Crystal Ball checks covered

RESPONSE_TIME_SLOW, server timing, hosting, caching

What the flag means

Crystal Ball flags slow initial response time when the server is slow to begin sending the page. This is often called TTFB, or time to first byte.

This is a problem because every later part of the page waits behind that first response. Images, scripts, and design polish cannot move quickly if the castle gate opens slowly.

Common causes

Common causes include slow hosting, no caching, too many CMS plugins, redirect chains, overloaded databases, security filters, cold serverless functions, or third-party systems that delay the page response.

How to fix it

  • Custom HTML/static: Check hosting response time, HTTPS redirects, cache headers, and server logs. Use lightweight pages, static caching, and a CDN where appropriate. Google’s TTFB guidance explains the response-time signal.
  • WordPress: Enable page caching, remove heavy plugins, check slow hosting, and test with the theme temporarily simplified. Start with your host’s cache tools and plugin audit before blaming the grimoire.
  • Shopify: Shopify handles server hosting, so focus on apps, theme complexity, and storefront scripts. If one page is slow, check page-specific apps, product media, and theme sections.
  • Wix: Wix handles hosting, so review heavy apps, embeds, animations, and oversized page sections. Test a simpler page to separate platform response from page weight.
  • Webflow: Publish to Webflow hosting or a fast static/CDN host, reduce third-party scripts, and check redirects. Static Webflow pages should usually respond quickly unless scripts or routing create detours.

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.