Fix Guide
How to Fix a Large HTML Document
The HTML response is large enough to slow parsing, increase crawl cost, and hide duplicated markup.
Recommended fix
Reduce inline JSON, duplicate page-builder markup, unused HTML, and oversized embedded data.
This guide is designed to pair with a scanner report. Run a URL scan first, then follow the implementation steps.
Developer task
Inspect the rendered HTML size, remove duplicate sections, lazy-load noncritical data, and move large payloads out of the document.
Implementation steps
How to apply this fix
- Inspect the rendered HTML size and find the largest contributors.
- Trim duplicate page-builder markup and remove unused or hidden sections.
- Move large inline JSON or embedded data into separate, cacheable resources.
- Lazy-load noncritical content instead of shipping it in the first response.
- Re-scan to confirm the HTML document size is reduced.
Verify
Re-run the URL scan after deploying the change to confirm the issue clears and the Themerella Score updates.
Related guides