Skip to main content

FlyingPress + Cloudflare Integration: Full Page Caching Setup Guide

Updated over a month ago

By default, Cloudflare only caches static files like images, CSS, and JavaScript.
With the FlyingPress Cloudflare integration, you can:

  • Cache full HTML pages at Cloudflare’s edge locations for faster global load times.

  • Reduce load on your origin server.

  • Automatically purge Cloudflare’s cache whenever content is updated.

  • Improve TTFB (Time to First Byte) for visitors worldwide.

  • Works with all Cloudflare plans, including the free plan.

  • Automatic configuration sync — FlyingPress and Cloudflare stay perfectly aligned:

    • Pages not cached or excluded in FlyingPress are also excluded in Cloudflare.

    • Query strings ignored in FlyingPress are also ignored by Cloudflare.

    • Bypass cookies in FlyingPress also bypass cache in Cloudflare.

    • Enabling Separate Mobile Cache & Optimizations in FlyingPress automatically enables Cache by Device Type in Cloudflare.

Step-by-Step Integration

  1. Open FlyingPress
    Go to the CDN tab in FlyingPress.
    Enable CDN and select Cloudflare as the provider.

  2. Get Your Zone ID

    • Log in to your Cloudflare dashboard.

    • Select the site you’re integrating.

    • On the Overview page, find the Zone ID and paste it into FlyingPress.

  3. Get Your Email Address

    • In your Cloudflare profile, go to Preferences.

    • Copy your email address and paste it into FlyingPress.

  4. Get Your Global API Key

    • In your Cloudflare profile, go to API Tokens.

    • Click View next to Global API Key, copy it, and paste it into FlyingPress.

  5. Enable “Page Caching” Toggle

    • In FlyingPress, switch on the Page Caching toggle.

    • This tells Cloudflare to cache full HTML pages, not just static files.

How to Confirm It’s Working

  1. Use Flying TTFB

    • Test your site at Flying TTFB.

    • The first run may be slower (cache MISS).

    • The second run should be faster with a cache HIT.

  2. Check in Browser DevTools

    • Open Chrome DevTools → Network tab.

    • Look for the cf-cache-status header.

    • HIT confirms the page was served from Cloudflare’s cache.

    • Logged-in users will not get cached HTML pages due to WordPress cookies.

FAQ / Notes

  • Disable Cloudflare APO before enabling this integration to avoid conflicts.

  • Works with all Cloudflare plans, including the free plan.

  • Purging FlyingPress cache automatically purges Cloudflare’s cache:

    • Purge Pages → Purges only HTML pages from Cloudflare.

    • Purge Everything → Purges HTML pages and static files from Cloudflare CDN.

  • First request after a purge will always be uncached (MISS). Subsequent requests should be cached (HIT).

  • Logged-in WordPress users will always bypass Cloudflare HTML page caching.

FlyingCDN vs Cloudflare Integration

While the Cloudflare integration only adds page caching on Cloudflare, FlyingCDN goes much further — including page caching, image optimization, WebP conversion, DDoS protection and advanced security features, Argo Smart Routing, access to all Cloudflare PoPs, Cloudflare Enterprise routing, and more. To know more, visit flyingcdn.com

Did this answer your question?