Reports and sharing
Reports are built for decisions. nimo tells you what is slow, why it matters, and what to fix first.
Fix the hero image before touching JavaScript.
It is responsible for the slow first view and has the lowest risk path to a better mobile LCP.
LCP
3.2s
Needs work
CLS
0.05
Good
INP
180ms
Watch
Share report
Public linkWhat a report includes
Verdict
A short explanation of the current state of the page.
Metrics
Core Web Vitals and supporting metrics from field and lab data.
Deep dives
Images, scripts, fonts, third parties, page entities, search context, and traffic context when available.
Next steps
Recommendations ranked by expected impact and practicality.
Prioritized recommendations
nimo does not simply repeat every Lighthouse warning. It ranks work by likely user impact, stack relevance, metric trend, and safety.
A recommendation can be important even when the Lighthouse score looks fine. nimo checks the field data first when it exists.
Share a report
Use share links when you need to send a report or comparison to a client, teammate, or developer. Share links are public URLs with an expiry window.
Open the report
Choose an audit report or comparison.
Create the share link
Pick the expiry window that matches how long the recipient needs access.
Send the link
The recipient can view the report without signing in.
Use reports with clients
For client work, save a before audit, make the change, run another audit, and share the comparison. This makes the work concrete: what changed, by how much, and what remains.
Client summary prompt
Summarize this report for a client in five bullets. Focus on business impact and the next fix.
Share the next report
Use a public report link when someone needs the answer without learning the dashboard.