Crystal Ball checks covered

PAGE_WEIGHT_LARGE, large HTML, template bloat

What the flag means

Crystal Ball flags large HTML responses when the page source itself is unusually heavy. This is different from large images or slow scripts. It means the first HTML document carries too much cargo.

This can slow rendering, make pages harder to maintain, and hide simple content inside a mountain of markup.

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.

How to fix it

  • 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.