This report never publishes a headline performance score
What this check looks for
We measured ‹scope› in a browser, and we are showing you what we found — but we do not publish a single 0-100 speed score, on this run or any other. This is not about your site or about the machine we used; we simply do not calculate that number.
Why it matters
Publishing a number that looks like Google's but is not computed the way Google computes it would be worse than publishing none, because you would compare the two. Everything else in this section is unaffected: the resources, the sizes and the savings are facts about what your server sent, and no scoring model is involved in them.
What it costs your score
This check never deducts. It reports a fact — or reports that something could not be verified — and is shown on the report without moving the score.
- Severity
- info
- Default confidence
- confirmed
- Status when triggered
- info
- Deduction
- 0 points
- Family cap
- none
- Category
- Performance
- Module
- Perf lab
- Fix owned by
- third party
- In the ruleset since
- 2026.09
Technical detail
**Why there is no score, on every run.** ‹detail›
The 0-100 Performance score people recognise is not a measurement. It is the output of Lighthouse's Lantern simulation applied to a trace, run through a scoring curve calibrated against a corpus of real sites. Our lab runner drives Chromium directly over the DevTools protocol; it implements neither the simulation nor the curve. There is therefore no number for us to publish and no run on which one appears — this finding is not an occasional caveat, it is a permanent property of this report.
**This says nothing about the hardware your site was measured on.** For the record, the run reported a CPU benchmark index of ‹benchmark index› on ‹cores› available core(s), and if a future runner ever did compute a score we would not publish it below an index of ‹floor› on at least 2 cores. Those numbers are context for the timings, not the reason the score is absent.
**What we publish instead.** The measurements that need no model: the transfer size of every resource, which resources block rendering, which images are larger than the space they are displayed in, which text responses arrived uncompressed, and how much of the shipped JavaScript went unused. Those are properties of what your server sent. The metric timings from this run are shown too, labelled as indicative, and they are not scored.
**If you want the score.** Run PageSpeed Insights against the same URL. It executes on Google's own infrastructure and computes the number the way Google defines it — which is exactly why we would rather point you at it than imitate it.
Standards and references
Test this on your domain
Run the check that produces this finding, on its own, against any domain.
Other perf lab checks
- The page ships more JavaScript than it uses
- Images are served in older, heavier formats
- Images are much larger than the space they are shown in
- Lab measurement of one page load
- Stylesheets and scripts stop the page from rendering
- Static files are re-downloaded because they are barely cached
- Scripts and stylesheets are sent without compression
- The page was not measured in a browser