The page was not measured in a browser
What this check looks for
We did not load ‹scope› in a real browser, so there is no lab measurement in this report. Nothing about the site's speed is being claimed here, good or bad.
Why it matters
This is a gap in our report, not a problem with your site. It is stated so that an empty lab section is never mistaken for a clean one.
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
The lab audit did not run: ‹reason›.
A lab measurement drives a real Chromium instance, which cannot run inside a Cloudflare Worker — there is no process to spawn and no browser to drive. It runs on a separate host, and when that host is not configured or not reachable, the honest output is this finding and **nothing else**. No metric, no opportunity and above all no pass is emitted from a run that did not happen.
The field-data section of this report is independent of this and may still be present: it comes from the Chrome UX Report API, which needs no browser of ours.
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
- This report never publishes a headline performance score
- Static files are re-downloaded because they are barely cached
- Scripts and stylesheets are sent without compression