Crystal Ball checks covered

PAGE_WEIGHT_LARGE, large HTML, template bloat

Guide detail

Choose Your Technical Level

This setting applies to the meaning, causes, and fix sections. Your choice carries to other Fix Library guides on this device.

Practical explanations and page-specific steps. Recommended for most readers.

What the flag means

Crystal Ball flags an unusually large HTML response for review. This is different from image or script weight: it measures the initial document before those resources load. The threshold is a diagnostic heuristic rather than a universal page-size limit.

Large HTML can increase transfer, parsing, memory, and maintenance cost, especially when it contains repeated markup, inline data, or code that the visible page does not need. Compression helps transfer size but does not remove parsing work.

Common causes

Common causes include page builders, huge menus, inline CSS, app-injected data, product variant data, duplicated sections, embedded widgets, and templates that output far more code than the page needs.

What to check next

Check whether the issue appears on one page or every page using the same template. Review recent content, theme, plugin, deployment, and server changes, then compare the live output with a known-good page.

How to fix it

Confirm the warning first and make a backup before editing the live site. If the change involves templates, code, DNS, redirects, or server settings, switch to Intermediate or ask for help before proceeding.

  • Custom HTML/static: Inspect the HTML source and remove bloated inline CSS, large embedded JSON, unused markup, huge menus, and copied builder code. Keep the initial document lean.
  • WordPress: Page builders, mega menus, plugins, and injected schema can bloat HTML. Disable nonessential plugins on a staging copy and compare source size.
  • Shopify: Large theme sections, app blocks, product JSON, variant data, and recommendation widgets can enlarge HTML. Review the template and app embeds.
  • Wix: Large pages often come from many sections, galleries, apps, or embeds. Split very long pages and simplify repeated elements where possible.
  • Webflow: Audit Symbols/Components, CMS-rich sections, embeds, and custom code. Move large data out of the page source when it does not need to load immediately.

Need help?

If the fix gets murky, visit Support and send the details. Bug reports and Crystal Ball questions are free support. Implementation and development work may be paid support, but we will tell you clearly before anything becomes paid. No surprise invoices from the tower.