What the page weighs, from the resources its HTML declares
Updated
What this check looks for
The subresources this page's HTML declares, how many of them we asked the server about and how many bytes they took: the inventory the other findings use.
In a report, this finding reads as follows, with each ‹…› filled in from what that scan observed:
‹scope› declares ‹subresources› in its HTML.
We asked the server about ‹fetched› of them and read ‹transferred› in total; the findings below are computed from that inventory.
Why it matters
Every optimisation below names specific files. This is the list those names come from, and the place where the limits of the measurement are stated rather than assumed.
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
- user
- In the ruleset since
- 2026.09
Technical detail
‹detail›
**How this was measured, and what it could not see.** We fetched the page and then the subresources its HTML declares, and read what the server sent back. No browser was involved, so nothing here depends on how fast our machine is — but equally, **a resource that a script loads after the page arrives is invisible to this check**. A page that assembles its own asset list at runtime will look lighter here than it is. The number of subresources the page declared, and how many of those we asked about, are both stated in the page-weight finding; where they differ, this section examined a prioritised sample rather than the whole page.
**No timing appears anywhere in this section, and that is deliberate.** First paint, Largest Contentful Paint, layout shift and main-thread work cannot be established without rendering the page. We do not estimate them from byte counts: a plausible-looking number we did not measure is worse than an honest gap. The Core Web Vitals this report *scores* come from the field-data section, measured on real visitors' devices, and a lab measurement of the timings — if one was performed for this scan — is reported separately and is labelled as indicative.
Standards and references
Test this on your domain
Run the check that produces this finding, on its own, against any domain.