Performance fix guide
Oversized HTML Document
Very large HTML size increases time-to-first-byte and parse time, especially on mobile networks.
Issue ID: PERF-PAGEWEIGHT-001
Severity: high
Impact: High
Effort: M
Use this article when
- You need deeper remediation guidance than the issue card can show.
- You want CMS-specific steps before handing the fix to a developer.
- You want a repeatable re-check path after shipping the change.
What this issue is
Very large HTML size increases time-to-first-byte and parse time, especially on mobile networks.
Why it matters
Very large HTML size increases time-to-first-byte and parse time, especially on mobile networks. This affects load speed, Core Web Vitals, and how many visitors stay long enough to convert.
How we detect it
- FreeSiteAudit flags this issue when the rule for PERF-PAGEWEIGHT-001 fails and the page evidence points to Http headers.
- You can usually confirm this by checking the page source or the relevant page settings inside your CMS.
Evidence examples
Check the affected page source, rendered output, or relevant CMS setting to confirm the missing or incorrect element.
How to fix it
- 1Remove inline styles and scripts. Move to external files
- 2Remove unused HTML/comments/whitespace
- 3Paginate or lazy-load large content blocks
- 4Use server-side compression (gzip/Brotli)
How to re-check it
- Check HTML size in DevTools Network tab (aim for under 100KB uncompressed)
Related tools
This issue is best verified with the full FreeSiteAudit crawl rather than a single-point mini tool.