PageSpeed Insights: how to actually read the score (and what to ignore)
PageSpeed Insights decoded: Core Web Vitals in plain words, which scores matter, what to ignore, and the fixes ordered by real impact.
Everyone pastes their site into PageSpeed Insights. Almost everyone misreads the result. Here is the decoder ring.
The two sections (know the difference)
- Lab data (the score at top): a simulated test — useful for comparing changes, not gospel
- Field data (Core Web Vitals): real visitor measurements from Chrome — this is what Google uses. A new site has no field data yet (normal)
The 3 Core Web Vitals, translated
1. LCP (Largest Contentful Paint): how long until the main content appears. Target: under 2.5s. Usually an image problem
2. INP (Interaction to Next Paint): how fast the page responds to taps. Target: under 200ms. Usually a JavaScript problem
3. CLS (Cumulative Layout Shift): how much the page jumps while loading. Target: under 0.1. Usually images without dimensions or late-loading ads/fonts
What to IGNORE
- The obsessive 100/100 chase: 90 vs 97 changes nothing in business
- 'Reduce unused CSS' style micro-audits before hosting/images are fixed
- Desktop score drama — your Pakistani audience is mobile; the mobile report is the report
The fixes in real order of impact
1. Hosting stack (NVMe + caching + current PHP) — moves everything
2. Images: WebP, resized, lazy-loaded — fixes most LCP
3. Plugin diet — fixes most INP
4. Image dimensions + font-display swap — fixes most CLS
The workflow
Test → fix in that order → retest. Compare YOUR before/after, not strangers' scores. And remember: the score serves the visitor, not vice versa — a 95 with no customers beats a 100 with none.