Cloudflare sits between your visitors and your server, which makes it one of the most effective places to improve website performance. Used well, it serves content from a location near each visitor, caches what it can, optimises images, and compresses responses. Used carelessly, it does little or even gets in the way. This guide covers the settings and techniques that genuinely improve Cloudflare website speed in 2026.

TL;DR

  • The biggest gains come from caching static assets aggressively and, where possible, caching HTML at the edge
  • Optimise images (modern formats, correct sizing, on-the-fly transformation) because images are usually the heaviest part of a page
  • Enable modern compression, HTTP/2 or HTTP/3, and keep TLS efficient
  • Measure before and after with real-world data; not every toggle helps every site

1. Cache Static Assets Aggressively

Static files (CSS, JavaScript, images, fonts) rarely change and should be served from Cloudflare’s edge, not your origin.

  • Set long cache lifetimes for versioned static assets so returning visitors and nearby users get them instantly.
  • Use cache-control headers correctly, and use fingerprinted filenames so you can cache “forever” and bust the cache on change.
  • Confirm assets are actually being served from cache (check the cf-cache-status response header for HIT).

2. Cache HTML at the Edge Where You Can

Serving the HTML document itself from the edge removes the round trip to your origin, which improves Time to First Byte and LCP.

  • For largely static sites, cache full pages at the edge.
  • For dynamic sites, cache what is safe (for anonymous visitors, for example) and bypass the cache for logged-in or personalised requests.
  • Be deliberate: never cache pages containing personal or session-specific data for all users.

3. Optimise Images

Images are typically the largest contributor to page weight, so this is where the biggest LCP wins usually are.

4. Compress and Modernise the Transport

  • Enable compression (Brotli) for text-based responses.
  • Serve over HTTP/2 or HTTP/3 for more efficient multiplexed connections.
  • Keep TLS efficient and enable modern protocol features Cloudflare provides.

5. Reduce and Prioritise What Loads

  • Minify CSS and JavaScript and remove unused code.
  • Defer non-critical JavaScript and load third-party scripts efficiently; they are common performance and INP culprits.
  • Preload critical resources such as the LCP image and key fonts.

6. Measure, Do Not Guess

  • Test load time and Core Web Vitals before and after each change, using real-world (field) data, not just a single lab run.
  • Turn on one meaningful change at a time so you know what actually helped.
  • Watch for features that can hurt if misapplied; verify rather than assume.

Key Takeaways

  • Cache static assets aggressively and cache HTML at the edge wherever it is safe to do so.
  • Image optimisation usually delivers the biggest single speed win.
  • Enable Brotli compression and HTTP/2 or HTTP/3, and trim and prioritise what loads.
  • Always measure before and after with field data; not every setting helps every site.

Cloudflare Website Speed and SEO

Improving your Cloudflare website speed lifts both conversions and rankings, because performance feeds directly into Core Web Vitals. For the metric-level fixes, see passing Core Web Vitals in 2026 . To find every technical issue holding your site back, including performance, a technical SEO audit gives you a prioritised action plan.

Frequently Asked Questions (FAQ)

Does Cloudflare actually make a website faster? Yes, when configured well. It serves content from a location near each visitor, caches static assets (and often HTML) at the edge, optimises images, and compresses responses. The gains depend on configuration; the defaults alone leave performance on the table.

What is the single most effective Cloudflare speed setting? Aggressive caching of static assets, and edge-caching HTML where it is safe, usually gives the biggest win by cutting round trips to your origin. Image optimisation is a close second because images dominate page weight.

Can I cache HTML on a dynamic site? Partly. Cache pages for anonymous visitors and bypass the cache for logged-in or personalised requests. Never serve one user’s personalised or session-specific page to everyone from cache.

Does site speed affect SEO? Yes. Speed feeds into Core Web Vitals, which are part of Google’s page experience signals. Faster sites also convert better, so the benefit is both ranking and revenue.

How do I know if Cloudflare is serving from cache? Check the cf-cache-status response header. HIT means it was served from Cloudflare’s edge; MISS or DYNAMIC means it came from your origin. Use this to confirm your caching rules are working.