Guides
Website Speed Test: Diagnose Real User Performance Before Chasing a Score
A useful website speed test identifies the metric, the affected template, and the evidence needed to make one focused fix.
Run a fresh DomainLens audit and use the report as your priority list.
A speed test is a diagnosis, not a grade
A website speed test can show a fresh Lighthouse result, field data from Chrome users, or both. Those are different measurements. A good lab result proves that one controlled visit was fast; it does not replace the 28-day field data Google groups in Search Console.
Start with the metric that fails. LCP points to the main visible content arriving late, INP to slow interaction work, and CLS to unexpected movement. Fixing a metric that already passes only makes the report prettier.
Turn one result into a safe fix
Use the Core Web Vitals guide to choose the failing metric, compare field and lab evidence in Search Console versus PageSpeed Insights , and check server delivery with the HTTP headers checker .
| Finding | First check |
|---|---|
| Slow LCP | LCP element, HTML discovery, image priority |
| Poor INP | Long tasks and third-party scripts |
| High CLS | Reserved space for media and banners |
| No field data | Use lab output as a hypothesis, not proof |