Website Speed Reports: How to Read One Without Getting Fooled
Run the same speed test twice and you’ll get two different scores. Here is what Google says those scores mean, which three numbers matter, and what to fix first.
The short answer
A single speed score is a rough guide, not a verdict. Google’s own documentation says scores change from run to run, mostly because of conditions around the test, not the tool (Chrome for Developers). Look past the score to three numbers: how fast the main content shows, how fast the page responds to a tap, and whether the layout jumps around.
Why the score changes
Google lists common reasons scores fluctuate, including changes in the ads being served, internet traffic routing, testing on different devices, and browser extensions (Chrome for Developers). Run any test three times and look at the middle result.
What the score bands mean
Google colors performance scores this way: 0 to 49 is poor, 50 to 89 needs improvement, and 90 to 100 is good (Chrome for Developers).
The three numbers that matter
From Google’s Core Web Vitals (web.dev):
- Largest Contentful Paint (LCP): how fast the main content shows. Good is within 2.5 seconds.
- Interaction to Next Paint (INP): how fast the page responds to a tap or click. Good is 200 milliseconds or less.
- Cumulative Layout Shift (CLS): whether things jump around while loading. Good is 0.1 or less.
Google recommends measuring these at the 75th percentile of real page loads, separately for phones and computers (web.dev).
Real visitors beat lab tests
A lab test is one simulated visit. Real-visitor data shows what customers actually get. If your speed report shows real-visitor data, trust it over the lab score. Small sites often don’t have enough visits for Google to show it.
What to fix first
- Big images and videos. Compress them, and don’t load a large video on phones if a photo will do.
- Scripts that freeze the page. Tracking tags, chat widgets and form tools often load first and block taps. Load them later where you can.
- Unused code. Themes and plugins often load code a page never uses.
- Icon fonts. Whole icon libraries are often loaded for a handful of icons.
FAQ
My score dropped overnight. Did something break?
Maybe not. Run the test three more times. Google says scores fluctuate with test conditions (Chrome for Developers).
Do I need a perfect 100?
No. Google calls 90 to 100 good. Focus on the three Core Web Vitals on phones.
Sources: Chrome for Developers: Lighthouse performance scoring · web.dev: Web Vitals