Is anyone else experiencing a slowdown on their website's initial page retrieval in Webflow? It seems that the slowness occurs before the assets are downloaded, with a minimum hang time of 5 seconds. The issue seems to happen even if the page has been previously visited, occurring every 4th to 6th page load. Could this be related to the speed of the Webflow CDN in fetching fresh copies of web pages?

TL;DR
  • Use Chrome DevTools to confirm the delay is due to high TTFB on the initial HTML document, not asset loading.  
  • The issue stems from intermittent CDN cache misses, where Webflow’s edge server fetches HTML from the origin, causing 5+ second delays.  
  • Minimize republishing, enable consistent domain redirects, and monitor with tools like GTMetrix to better understand cache behavior.

You're describing a noticeable delay (5+ seconds) before initial page content begins loading, happening intermittently every several page loads — even when assets are cached. This points to a Time to First Byte (TTFB) issue likely tied to how Webflow delivers pre-rendered HTML from its CDN.

1. Understand Webflow’s Hosting Architecture

  • Webflow uses AWS Cloudfront (a CDN) to serve static HTML content, CSS, and JS.
  • Pages are pre-rendered and cached at edge locations.
  • Whenever a cached page expires or isn’t present at the specific edge location, Webflow fetches a fresh copy from origin, causing a delay.

2. Confirm the Problem Is TTFB (Not Asset-Related)

  • Use Chrome DevTools > Network tab to observe TTFB on the main document request (yourpage.html).
  • If the delay appears before the DOM or any assets load, and the first document shows a TTFB > 3–5 seconds, it’s server-side latency.
  • CDNs should return assets in milliseconds if cached — longer delays suggest cache miss or slow origin response.

3. Intermittent Pattern Suggests Cache Misses at the CDN

  • Webflow may rotate or purge edge location caches, especially if:
  • You’ve recently published or republished your site.
  • The CDN’s cache TTL (time-to-live) has expired for your page.
  • Webflow doesn’t currently allow control over edge cache expiration, so every few loads may request fresh HTML from the origin server if CDN cache has evicted the page.

4. You’re Not Alone — This Has Been Noted by Others

  • Multiple Webflow forum users have reported slow initial page retrieval even for static pages.
  • These delays occur intermittently, aligning with your “every 4th to 6th load” observation.
  • It’s a likely side effect of CDN cache revalidation or eviction policies — especially for less-trafficked pages.

5. Steps You Can Take Right Now

  • Enable Webflow’s Redirect to www (or vice versa) to ensure consistent cache keys.
  • Use Cache-Control headers sparingly (Webflow doesn’t give much control, but custom headers via reverse proxy can help if using external hosting).
  • Monitor via tools like Pingdom or GTMetrix across multiple geolocations to confirm edge cache behavior.
  • Avoid unnecessary republishing, which can purge CDN caches globally.

Summary

The intermittent slow initial page load every few visits is most likely due to CDN cache misses, where Webflow’s edge server needs to fetch fresh HTML from origin. This is a known limitation of Webflow’s current CDN behavior and affects TTFB. There's no immediate fix within Webflow, but being aware of cache behavior can help reduce its frequency.

Rate this answer

Other Webflow Questions