Very heavy HTML document
HTML documents larger than 1.5 MB. The HTML is downloaded before anything else, on every visit and every crawl. Very heavy documents usually carry inlined data or repeated markup that belongs elsewhere.
WarningPERF-004 · Performance · checked on every page
Where it usually comes from
Pages that embed a whole product catalogue as JSON for a script, inline SVG sprites repeated on every page, or long lists rendered in full.
How to fix it
- Look for large inline scripts, JSON state or SVGs in the HTML.
- Move them to separate files that can be cached, or load them when needed.
- For long lists, show the first part and paginate or load the rest on request.
- Measure the document again after the change: the check passes below 1.5 MB.
How to check it yourself
Look at the size of the document request in the browser's Network tab — the first request, not the images.
What it looks like in a report
Warning The HTML document weighs 3 to 6 MB. · /category/*
Category pages embed the whole product list as JSON for a script. (An example shop; the numbers are illustrative.)
How the audit counts it
PERF-004 is a warning in the performance category, and weighs moderately in that category’s score. When it appears on many pages built from the same template, the report shows it once, with the number of pages it covers — because one change in the template fixes all of them.
If the finding is deliberate on your site, it can be accepted as intentional in the report. It then leaves the list and the score, and comes back on its own if what it shows changes.
Other performance checks
- Images without declared dimensions · PERF-001
- Too many blocking resources in the head · PERF-002
- LCP above 2.5 s · PERF-003
- Layout shifts while loading (CLS) · PERF-005
- Slow response to clicks and taps (INP) · PERF-006
- Images heavier than 200 KB · PERF-007
Find it on your site
A Trakis audit runs this check and the other 65 on your site, and tells you on how many pages each one sits. Or go back to all the rules.