ARTICLE
How to Read a Page Speed Score (Without Being a Developer)
What every field in a Page Speed Grader report actually means, where the thresholds come from, and which numbers to fix first when you can only fix one.
Apr 27, 20267 min read
A page speed score is four numbers, not one
Most page speed reports show a single 0–100 score and call it a day. That score is a weighted average of four underlying metrics, and the weights matter. A site with a 65 might be one CSS change away from 90, or it might need a full rebuild — the overall score doesn't tell you which.
The Page Speed Grader returns the underlying metrics directly. This post walks through each one: what it measures, what the thresholds are, and what to do when your site fails it.
The four metrics that matter
Google's Core Web Vitals framework defines three metrics with explicit thresholds. The Page Speed Grader reports these plus one additional that's diagnostic-only:
| Metric | What it measures | Pass | Needs improvement | Fail |
|---|---|---|---|---|
| LCP (Largest Contentful Paint) | Time until the biggest visible element finishes rendering | ≤ 2.5s | 2.5–4.0s | > 4.0s |
Keep reading
How to Read the Meta Tag Analyzer Output
What every field in a Meta Tag Analyzer report means, what the thresholds are, and how to act on each finding without guessing.
How to Fix Render-Blocking Resources
Identify and eliminate render-blocking CSS and JavaScript that delay FCP and LCP — with concrete code fixes for defer, async, preload, and critical CSS.
Image Optimization Without Breaking Your Build
A pragmatic image-optimization plan that ships actual LCP wins on real client sites: formats, dimensions, lazy-loading rules, and CDN tradeoffs.
Try the tool
Run the page speed grader tool