Crystal Ball checks covered

MANY_FRONTEND_ASSETS, render-blocking CSS, render-blocking JavaScript

What the flag means

Crystal Ball flags this when a page appears to load many scripts or styles before users can see the useful content. Some CSS and JavaScript are necessary. The issue is when too many resources demand attention first.

This matters because the page can feel slow even if the server responds quickly. The browser is waiting for the spell ingredients before showing the room.

Common causes

Common causes include plugin scripts, Shopify apps, chat widgets, tracking tags, font kits, animation libraries, old code left after redesigns, and embeds that load on every page instead of only where needed.

How to fix it

  • Custom HTML/static: Load critical CSS first, defer nonessential JavaScript, and avoid stacking font kits, trackers, and libraries. Google’s critical rendering path guide explains the underlying issue.
  • WordPress: Use performance plugins carefully to defer scripts and remove unused CSS. Test after each change because aggressive optimization can break menus, forms, and sliders.
  • Shopify: Remove unused apps, check theme app embeds, and defer noncritical scripts where the theme supports it. Avoid adding multiple trackers and chat widgets without a purpose.
  • Wix: Reduce third-party apps, embeds, and heavy animations. Wix handles much of the platform code, so focus on what was added to the page.
  • Webflow: Move noncritical custom scripts before the closing body tag, reduce external libraries, and avoid loading unused animations or embeds on every page.

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.