Audits
An audit is nimo checking how your site performs, explaining what matters, and saving the result so future changes can be compared.
Run an audit
You can run an audit from the dashboard, Telegram, or MCP. A full audit pulls available Chrome field data, runs a simulated test, analyzes the result, and creates a report. A quick audit is useful after a fix when you want a fast comparison.
Pick the site
Use the dashboard, /site in Telegram, or list_sites through MCP.
Start the audit
Trigger the audit from the UI, /audit, or the run_audit MCP tool.
Wait for the report
nimo streams progress while it checks real visitor data, runs diagnostics, and builds the report.
Read the results
nimo leads with the plain-language verdict, then shows metrics and recommendations.
LCP
How long visitors wait before the main content appears. nimo describes this as page load, not as a metric acronym.
CLS
How much the page shifts while visitors try to read or click.
INP
How responsive the page feels when visitors interact.
Diagnostics
Images, scripts, stylesheets, fonts, third parties, and page structure that explain why a metric is slow.
Lighthouse scores can move between runs. nimo focuses on metric values, history, and real visitor impact.
Compare changes
Run an audit before and after a fix. nimo can compare two audits and show what improved, what got worse, and what stayed the same.
Comparison prompt
Compare my last two audits. Which metrics changed enough to trust?
Use audit history
Audit history helps nimo tell the difference between a one-off slow run and a real trend. It also helps you explain client work with before-after evidence.
For important pages, run a manual audit before deploying a fix. Then run another audit after the change has shipped.
Run an audit
Get the first report, then use history to prove whether each fix worked.