The page's assets were not examined
What this check looks for
We could not read the HTML of ‹scope›, so there is no page-weight analysis in this report. Nothing about the site's assets is being claimed here, good or bad.
Why it matters
This is a gap in our report rather than a fault on your site. It is stated so that an empty assets 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 assets
- Fix owned by
- third party
- In the ruleset since
- 2026.09
Technical detail
The page-weight analysis did not run: ‹reason›.
This check needs the served HTML, because the HTML is what declares which stylesheets, scripts, images and fonts the page loads. Without it there is no list of subresources to ask about, and the honest output is this finding and nothing else — no inventory, no opportunity, and above all no pass.
The usual causes are the ones that stop any fetch: the host did not answer, the response was a 4xx or 5xx, or the URL was refused by the scanner's own target policy before a connection was made. The reason above says which. Other sections of this report are unaffected and may still carry findings about the same page.
Standards and references
Test this on your domain
Run the check that produces this finding, on its own, against any domain.