WordPress.org

Weston Ruter

WordPress Performance Team

This plugin was formerly called as “No-cache BFCache”, which admittedly was a poor jargony name and was too narrowly scoped.
This plugin enables instant back/forward navigation via the browser’s <a href="https://developer.mozilla.org/en-US/docs/Glossary/bfcache" rel="nofollow ugc">bfcache</a>. It does this by removing the <code>no-store</code> directive from the <code>Cache-Control</code> response header, which WordPress sends by default when <code>nocache_headers()</code> is called. This happens primarily when a user is logged in, but some plugins may send these “no-cache” headers such as on the Cart or Checkout pages for an e-commerce site. Upon activation, to see the effect, you must log out of WordPress and log back in again, ensuring “Remember Me” is checked. Even so, another plugin, theme or server configuration may be active which makes pages <a href="https://web.dev/articles/bfcache#optimize" rel="nofollow ugc">ineligible for bfcache</a> due to other <a href="https://developer.mozilla.org/en-US/docs/Web/API/Performance_API/Monitoring_bfcache_blocking_reasons#blocking_reasons" rel="nofollow ugc">blocking reasons</a>. Nevertheless, the removal of <code>no-store</code> will still speed up back/forward navigations since pages may then be served from the browser’s HTTP cache, eliminating the need to re-download the HTML from the server. This is a feature plugin to implement <a href="https://core.trac.wordpress.org/ticket/63636" rel="nofollow ugc">#63636</a> in WordPress core.
Blog post: <a href="https://weston.ruter.net/2025/07/23/instant-back-forward-navigations-in-wordpress/" rel="nofollow ugc">Instant Back/Forward Navigations in WordPress</a>
The speed of page navigations in WordPress saw a big boost in 6.8 with the introduction of <a href="https://make.wordpress.org/core/2025/03/06/speculative-loading-in-6-8/" rel="nofollow ugc">Speculative Loading</a>. However, by default Speculative Loading in WordPress is not configured to enable instant page loads, which requires a non-conservative eagerness with the prerender mode; not all sites can even opt in to prerendering due to compatibility issues, such as with analytics, and due to concerns about sustainability with unused prerenders (e.g. increasing server load and taxing a user’s bandwidth/CPU). While Speculative Loading (i.e. the Speculation Rules API) is relatively new and currently only supported in Chromium browsers (e.g. Chrome and Edge), there is a much older web platform technology that enables prerendering and which is supported in all browsers: the back/forward cache (bfcache). This instant loading involves no network traffic and no CPU load, since previously visited pages are stored in memory. According to the web.dev article on <a href="https://web.dev/articles/bfcache" rel="nofollow ugc">back/forward cache</a>:
Chrome usage data shows that 1 in 10 navigations on desktop and 1 in 5 on mobile are either back or forward. With bfcache enabled, browsers could eliminate the data transfer and time spent loading for billions of web pages every single day!
Also learn more via the following video:
<iframe loading="lazy" class="youtube-player" width="750" height="422" src="https://www.youtube.com/embed/Y2IVv5KnrmI?version=3&rel=1&showsearch=0&showinfo=1&iv_load_policy=1&fs=1&hl=en-US&autohide=2&wmode=transparent" allowfullscreen="true" style="border:0;" sandbox="allow-scripts allow-same-origin allow-popups allow-presentation allow-popups-to-escape-sandbox"></iframe>
Normally, WordPress sends a <code>Cache-Control</code> header with the <code>no-store</code> directive when a user is logged in. This has the effect of <a href="https://web.dev/articles/bfcache#minimize-no-store" rel="nofollow ugc">breaking the browser’s bfcache</a>, which means that navigating back or forward in the browser requires the pages to be re-fetched from the server and for any JavaScript on the page to re-execute. The result can be a sluggish navigation experience not only when navigating around the WP Admin (see <a href="https://github.com/Automattic/jetpack/pull/44322#:~:text=page%20load%20is%3A-,Without%20bfcache,-With%20bfcache" rel="nofollow ugc">Jetpack demo video</a> and demo video below) but also when navigating around the frontend of a site. Furthermore, the lack of bfcache can cause data loss when data has been entered via a JavaScript-built UI since this state is lost when a page is not restored via bfcache (see <a href="https://github.com/woocommerce/woocommerce/pull/58445#issuecomment-3014404754" rel="nofollow ugc">WooCommerce demo video</a> and demo video below).
The reason why the <code>no-store</code> directive was added in the first place was due to a privacy concern where an authenticated user may log out of WordPress, only for another person to access the computer and click the back button to view the contents of the authenticated page loaded from bfcache or the HTTP cache. (See <a href="https://core.trac.wordpress.org/ticket/21938" rel="nofollow ugc">#21938</a>.) In practice this issue depends on the user being on a shared computer who didn’t exit the browser, and it requires the malicious user to act soon before the page is evicted from bfcache (e.g. Chrome as a <a href="https://developer.chrome.com/docs/web-platform/bfcache-ccns#:~:text=The%20bfcache%20timeout%20for%20Cache%2DControl%3A%20no%2Dstore%20pages%20is%20also%20reduced%20to%203%20minutes%20(from%2010%20minutes%20used%20for%20pages%20which%20don%27t%20use%20Cache%2DControl%3A%20no%2Dstore)%20to%20further%20reduce%20risk." rel="nofollow ugc">10-minute timeout</a>).
To address this privacy concern, a safeguard is in place to protect against restoring pages from bfcache and the HTTP cache after the user has logged out:
When authenticating to WordPress, a “bfcache session token” cookie is set along with the other authentication cookies. This cookie is not HTTP-only so that it can be read in JavaScript; it is a random string not used for any other purpose. When an authenticated page is served, this bfcache session token is included in the HTML as well as a script which reads the value of this cookie. When a user navigates away from the page and then navigates back to it, a script on the page checks if the current session token in the cookie matches the initial session token sent with the page. If they do not match (e.g. because the user has logged out or another user has logged in), then the contents of the page are cleared and the page is reloaded so that the contents are not available.
Since JavaScript is required to invalidate cached pages, the login form is extended to pass along whether scripting is enabled. Only when JS is enabled will the <code>no-store</code> directive be omitted from the <code>Cache-Control</code> response header. This ensures that users with JavaScript turned off will retain the privacy protection after logging out. Lastly, <code>no-store</code> is also only omitted if the user checked the “Remember Me” checkbox on the login form. Since it is highly unlikely a user on a shared computer would have checked this checkbox, this provides yet an additional safeguard (which may in the end prove excessive). A ✨ emoji is displayed next to the checkbox in a button that opens a popover that promotes the capability. If you want to opt out of this opt-in (and the sparkle) so that all logged-in users get bfcache, you can use the <code>nocache_bfcache_use_remember_me_as_opt_in</code> filter which you can use in a custom plugin or your theme:
<pre>add_filter( 'nocache_bfcache_use_remember_me_as_opt_in', '__return_false' );</pre>
When this plugin strips out the <code>no-store</code> directive, it also ensures that the <a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Cache-Control#private" rel="nofollow ugc"><code>private</code> directive</a> is sent in its place: “The <code>private</code> response directive indicates that the response can be stored only in a private cache (e.g., local caches in browsers).” WordPress is already sending <code>private</code> as of <a href="https://core.trac.wordpress.org/ticket/57627" rel="nofollow ugc">#57627</a>. This directive ensures that proxies do not cache authenticated pages. In addition to ensuring <code>private</code> is present, this plugin also adds <code>no-cache</code>, <code>max-age=0</code>, and <code>must-revalidate</code> while ensuring <code>public</code> is removed, all to further guard against any misconfigured proxy from caching the private response.
<h4>Demo: Navigating the WordPress Admin</h4>
Without bfcache:
<iframe loading="lazy" class="youtube-player" width="750" height="422" src="https://www.youtube.com/embed/Cz-_L6q9ZRc?version=3&rel=1&showsearch=0&showinfo=1&iv_load_policy=1&fs=1&hl=en-US&autohide=2&start=22&wmode=transparent" allowfullscreen="true" style="border:0;" sandbox="allow-scripts allow-same-origin allow-popups allow-presentation allow-popups-to-escape-sandbox"></iframe>
With bfcache:
<iframe loading="lazy" class="youtube-player" width="750" height="422" src="https://www.youtube.com/embed/z4dILiwe0Rk?version=3&rel=1&showsearch=0&showinfo=1&iv_load_policy=1&fs=1&hl=en-US&autohide=2&start=27&wmode=transparent" allowfullscreen="true" style="border:0;" sandbox="allow-scripts allow-same-origin allow-popups allow-presentation allow-popups-to-escape-sandbox"></iframe>
<h4>Demo: Navigating the WordPress Frontend</h4>
Without bfcache: The drafted BuddyPress activity update is lost when navigating away from the page before submitting. The activity feed and Tweet have to be reconstructed with each back/forward navigation.
<iframe loading="lazy" class="youtube-player" width="750" height="422" src="https://www.youtube.com/embed/Ko1w_SRlCig?version=3&rel=1&showsearch=0&showinfo=1&iv_load_policy=1&fs=1&hl=en-US&autohide=2&wmode=transparent" allowfullscreen="true" style="border:0;" sandbox="allow-scripts allow-same-origin allow-popups allow-presentation allow-popups-to-escape-sandbox"></iframe>
With bfcache: The drafted BuddyPress activity update is preserved when navigating away from the page without submitting. The activity feed and Tweet do not have to be reconstructed when navigating to previously visited pages via the back/forward buttons.
<iframe loading="lazy" class="youtube-player" width="750" height="422" src="https://www.youtube.com/embed/bzGm6LcHHAs?version=3&rel=1&showsearch=0&showinfo=1&iv_load_policy=1&fs=1&hl=en-US&autohide=2&wmode=transparent" allowfullscreen="true" style="border:0;" sandbox="allow-scripts allow-same-origin allow-popups allow-presentation allow-popups-to-escape-sandbox"></iframe>

Instant Back/Forward


This is now a "must install" plugin for me on every site I work on. It's absolutely magical.


Magical

Enables back/forward cache (bfcache) for instant history navigations even when “nocache” headers are sent, such as when a user is logged in.

Themeisle

Optimole

iSaumya

Salvatore Fresta

Super Page Cache is a powerful full page cache plugin for WordPress that caches static files (CSS, JS, images) and HTML webpages at both server disk-level and the global Cloudflare CDN. Get enterprise-level performance with zero configuration required.
Super Page Cache improves site speed by enabling server-side caching, cache preloading, local Google Fonts, and removing unused CSS and JavaScript, boosting Core Web Vitals and load times.
Works right out of the box with or without Cloudflare. Powerful disk caching saves files locally on your server. To use Cloudflare CDN, just enter your API Key or Token. The intuitive dashboard includes detailed settings and built-in documentation, though most users won’t need to change the defaults.
<iframe loading="lazy" class="youtube-player" width="750" height="422" src="https://www.youtube.com/embed/SYhoaL_fUY0?version=3&rel=1&showsearch=0&showinfo=1&iv_load_policy=1&fs=1&hl=en-US&autohide=2&wmode=transparent" allowfullscreen="true" style="border:0;" sandbox="allow-scripts allow-same-origin allow-popups allow-presentation allow-popups-to-escape-sandbox"></iframe>
<h3>⚡ Quick Links</h3>
<ul>
<li><a href="https://docs.themeisle.com/collection/2199-super-page-cache" rel="nofollow ugc">Documentation</a> → Complete setup and configuration guide</li>
<li><a href="https://wordpress.org/support/plugin/wp-cloudflare-page-cache/" rel="ugc">Support Forum</a> → Community help and expert support</li>
<li><a href="https://youtube.com/playlist?list=PLmRasCVwuvpSJuwaV7kDiuXhxl08zbZr5&si=Gem626AyPpNenDF3" rel="nofollow ugc">YouTube Videos</a> → Step-by-step visual guides for every feature</li>
<li><a href="https://themeisle.com/plugins/super-page-cache-pro/?utm_source=wordpressorg&utm_medium=readme&utm_campaign=quicklinks" rel="nofollow ugc">Go Pro</a> → Advanced features and priority support</li>
</ul>
<h3>🚀 How Does The Plugin Work?</h3>
Disk Caching (Works Without Cloudflare): Server-level caching saves HTML pages and static files directly to your server, loading pages instantly without any CDN.
Cloudflare CDN (Optional): Connect your Cloudflare account to leverage <a href="https://www.cloudflare.com/network/" rel="nofollow ugc">200+ edge locations</a> using modern Cache Rules. Works with FREE Cloudflare Plan – no paid account required. Achieve higher Pingdom and GTmetrix scores with edge delivery.
Supports Free, Pro, and Enterprise Cloudflare plans with auto-purging, cron jobs, and integrated metrics.
<h3>🔥 Core Features (Free Version)</h3>
<h4>🚀 Complete Caching Solution</h4>
<ul>
<li>Disk Caching: Lightning-fast server caching with Cloudflare fallback</li>
<li>CDN Integration: Optional Cloudflare CDN with 200+ edge locations</li>
<li>Cache Controls: Exclude cookies, query params, URIs, AMP, feeds, REST API</li>
<li>Cache Lifespan: Custom expiration or never-expire settings</li>
<li>Header Management: Preserve critical response headers</li>
<li>Cache Buster: Logged-in users never see cached content</li>
<li>Performance Metrics: Track cache effectiveness</li>
</ul>
<h4>⚡ Performance Optimization</h4>
<ul>
<li>Google Fonts: Combine and serve locally for better Web Vitals</li>
<li>Lazy Loading: Images, videos, iframes, background images</li>
<li>Lazy Load Exclusions: By keywords, URL patterns, or CSS classes</li>
<li>Assets Manager: Enable/disable CSS/JS per page</li>
<li>Browser Caching: Auto-configure <code>.htaccess</code> rules</li>
</ul>
<h4>🛠️ Advanced Cache Management</h4>
<ul>
<li>Auto-Purging: Clear cache on content updates including related pages</li>
<li>Granular Purge: HTML only or entire cache with assets</li>
<li>Preloader: From sitemaps, menus, or recent posts (manual/CRON)</li>
<li>Background Processing: Uses <code>Action Scheduler</code></li>
<li>Queue-Based Purging: Prevent server overload</li>
<li>Backend Bypass: Prevent admin dashboard caching</li>
<li>Per-Page Control: Exclude via editor metabox</li>
<li>Toolbar Purging: Instant purge from WP toolbar</li>
</ul>
<h4>🔧 Developer & Power User Features</h4>
<ul>
<li>Redesigned Dashboard: Intuitive navigation with grouped settings</li>
<li>Built-in Documentation: Tips within the dashboard</li>
<li>Cache Backends: <code>advanced-cache.php</code> or cURL-based</li>
<li>Defer JS Filter: <code>spc_defer_script</code> to exclude scripts</li>
<li>Role Permissions: Control who can purge cache</li>
<li>Cloudflare API: All plans via API Key or Token</li>
<li>Export/Import: Settings as JSON</li>
<li>Preserve on Deactivation: Retain settings for staging</li>
</ul>
<h4>🗄️ Database Optimization</h4>
<ul>
<li>Database Cleanup: Remove revisions, auto-drafts, trash, spam, transients</li>
<li>Scheduled Maintenance: Daily, weekly, or monthly</li>
<li>Table Optimization: <code>SQL OPTIMIZE TABLE</code> for defragmentation</li>
<li>Selective Cleanup: Choose which data types to clean</li>
</ul>
<h4>🌐 Universal Compatibility</h4>
<ul>
<li>Premium Hosts: Kinsta, WP Engine, SpinupWP, and more</li>
<li>eCommerce: WooCommerce, Easy Digital Downloads</li>
<li>Server Caches: Varnish, OPcache auto-purge</li>
<li>Prefetch: Internal links via <a href="https://instant.page" rel="nofollow ugc">Instant.page</a></li>
</ul>
<h3>💎 Super Page Cache PRO with Advanced Performance Features</h3>
<ul>
<li>Ignore Marketing Parameters: Better cache hit rate (UTM, affiliate, tracking codes)</li>
<li>Defer JavaScript: Eliminate render-blocking JS. <a href="https://docs.themeisle.com/article/2058-defer-js" rel="nofollow ugc">Learn more</a></li>
<li>Delay JavaScript: Load JS on interaction only. <a href="https://docs.themeisle.com/article/2057-delay-js" rel="nofollow ugc">Learn more</a></li>
<li>Advanced Lazy Loading: Viewport detection, above-the-fold optimization</li>
<li>Advanced Exclusions: Exclude specific JS/pages from caching</li>
<li>Priority Support: Faster email response times</li>
</ul>
<a href="https://themeisle.com/plugins/super-page-cache-pro/?utm_source=wordpressorg&utm_medium=readme&utm_campaign=spc-pro-featrues" rel="nofollow ugc">Upgrade to Pro</a>
<h3>🎯 Usage Note</h3>
Disable page caching in other plugins (WP Rocket, LiteSpeed Cache, W3 Total Cache). Safe to use alongside <a href="https://wordpress.org/plugins/optimole-wp/" rel="ugc">Optimole</a>, Autoptimize, Perfmatters, ShortPixel for asset optimization.
<h3>⭐ What Users Say</h3>
<blockquote>
★★★★★ “Response times dropped from 400ms+ to below 200ms. Almost the same as my static S3 site—using the free version!” – @jurijs0
★★★★★ “A game-changer for our website’s performance! Noticeable improvement in loading times, boosted engagement and SEO.” – @brandnexusstudios
</blockquote>
<a href="https://wordpress.org/support/plugin/wp-cloudflare-page-cache/reviews/#new-post" rel="ugc">Leave a review</a> | <a href="https://twitter.com/themeisle" rel="nofollow ugc">Follow us on Twitter</a> | <a href="https://www.youtube.com/@Themeisle" rel="nofollow ugc">YouTube</a>
Super Page Cache is backed by <a href="https://themeisle.com/" rel="nofollow ugc">Themeisle</a>, powering 1M+ WordPress sites with 450+ five-star <a href="https://www.trustpilot.com/review/themeisle.com" rel="nofollow ugc">Trustpilot</a> ratings.

Super Page Cache


Every site i have uses this Plugin, also the Support is fast and very nice!Big recommendation!!!


Best free Plugin you can get

Nice Plugin


Super Page Cache for Cloudflare is an exceptional plugin that has greatly improved my experience with WordPress caching. Having used various other caching plugins for several years, I can confidently say that this plugin stands out in terms of its effectiveness and simplicity.


effectiveness and simplicity


This is a really fantastic plugin. My websites are lightning fast, the plugin is pretty easy to use, and I've pretty much always been able to get answers to my questions by looking at documentation or the support forums. There was one time where I posted in the support forum and I got a response the same day. Solid plugin with great support. Highly recommend!


Really great plugin! Super fast, easy to use, and well documented


Configuration is easy and the total effect on load times is truly amazing. This is a staple for any site that I build. My clients and their clients benefit greatly from the improved load time on all pages. One of the best plugins ever created.


so simple and extremely effective


Great plugin to use Cloudflare Edge Network without the need to subscribe to APO. Support is also great and responsive. Well done!


A straight forward solution to use Cloudflare Edge Network for free


This is a great plugin for managing my CloudFlare cache. It has all of the features I need and isn't overloaded with spammy stuff like the majority of WordPress plugins are now.


Great plugin!


Great plugin that provides both fantastic out-of-the-box functionality for casual users and highly detailed and customizable settings for power users.



Fills an essential role in the community for WP + CloudFlare users.



Incredible fast and high quality support directly from the developer.



Highly recommended over the official CloudFlare plugin, which forces users to adopt their "APO" system, lacks detailed settings and just generals falls short of what it should do.


Amazing Plugin


... it's tricky to set up!You might have noticed that 80% of the reviews give 5 stars to this plugin. Aye, it well deserves them! And then there are a few who simply say "doesn't work" or "does nothing" or "same error as reported 5 years ago" and just give one star. There is not much in-between! How come?The explanation is easy.WordPress users come in all forms and shapes, and that also means quite different levels of know-how. Many entry-level cache plugins are very easy to set up: install it, click a checkbox to "enable cache", and in 90% of the cases, that's all you need to do. Some give you a few options to further tweak your setup, but these are mostly optional and/or "advanced usage" for the very few that really need them.This is the case of the free, built-in cache plugins already being offered by many hosting providers. They are installed automatically when WordPress is installed. They are also automatically configured. The end-user doesn't need to do much, and, in many cases, they're not even aware that a cache plugin is being used — everything works transparently and effortlessly.Obviously, that level of simplicity comes with a catch: you can't really optimise much in terms of caching. It's a one-size-fits-all-but-probably-none situation. In many cases, turning off the hosting provider's plugin and adding your own will give you the possibility of tweaking things further, beyond what an automatic configuration can do.And then there is the other extreme of the spectrum: W3 Total Cache. The cache plugin that has everything and does everything. You can precisely configure the most minute details of your whole caching framework (because, well, it doesn't limit itself to caching pages — it does pretty much everything). W3 Total Cache goes even further, actively looking for "improvement" tools that it can use and which might be running on your server — and allows you to activate them. Selectively. So you can use a Redis cache for some things (such as, say, object cache) but let the page cache stay on disk; or write some rules to get some elements automatically sent to a CDN, while keeping others local. It does support Cloudflare, too (as well as many, many other providers). In fact, it would be hard to think of anything that W3TC does not support or doesn't allow to be configured.So why isn't everybody using it, if it's that good?Well, W3TC is impossibly hard to configure. Or, rather, you can do it, but it will be a nightmare to "get it right". You might be "overtweaking" your configuration (it happened to me all the time!) and, as a consequence, W3TC would even slow down your system. You can miss a crucial parameter and throw your site offline in a second. And sure, you can make a copy of all the configuration settings that you have carefully preserved over the years, hoping to avoid all the trouble the next time you configure another WP installation. Well, good luck with that. It's highly likely that a different WP site will, well, require different configurations. Some WP sites have zero JavaScript, but complex CSS; others have minimalistic CSS, but very clever JavaScript tricks, such as partially loading bits of content instead of a full page. Tweaking W3TC for each of those scenarios can be completely different and may require you to dump your "favourite" configuration and just start from scratch again. Oh, and that's until your end-user decides to switch themes and/or add new plugins. Then you have to do everything from scratch — again.Not everybody has that amount of free time, nor the enthusiasm and dedication required to keep W3TC operating smoothly. It's simply too complex to configure and maintain. As a result, most sites using W3TC ae not as optimised as they could be.Enter Super Page Cache for Cloudflare.This plugin, in terms of complexity and the ability to fine-tune several performance parameters, is closer to W3TC and further away from the "generic" page cache plugin pre-installed by hosting providers. In other words: there is a lot to configure until you "get it right". The "reasonable defaults" that it starts with are... well, reasonable, sure, in the sense that they will not blow up your website, but the performance enhancements will not be dramatic.That's as it should be, because the heavy-duty work is not being done by WordPress, nor even by Super Page Cache for Cloudflare; indeed, most is being done on Cloudflare's side. And this is the right way to do it! Super Page Cache for Cloudflare essentially prepares WordPress to correctly interface with Cloudflare and leverages on what Cloudflare already provides (for free) in order to seriously accelerate your website.In other words...There is a limit to how much you can tweak your website locally. The "best of the best" caching plugin cannot magically wave some metrics away. If you're hosting in the US, but your clients connect from Europe, there is no way to tweak and fine-tune your caching plugin so that European users get faster access to your website. There is a limit to how fast data can be transferred between the two sides of the Atlantic — ultimately, the speed of light. You cannot get faster than that! So, at best, you can hope for a local optimal configuration: giving users near to your data centre the best experience possible, and, well, there is not much more you can do beyond that, right? There is no way to go faster than the speed of light (not on this universe, anyway).Well, the answer is that you can cheat.And that's what Cloudflare essentially does: it doesn't merely "cache your content". Rather, it does so by making copies of your website's cache to their 250+ data centres across the world. This means that European visitors will not connect to your website in the US. They will just connect to Cloudflare's nearest data centre in Europe, and retrieve the cached pages from there instead. Since Cloudflare operates in so many different cities, there is a huge percentage of the world's Internet population that gets local speeds to retrieve your website — as opposed to have to wait for data to patiently cross the Atlantic (twice... once for the request, once for the reply).It's the equivalent of making copies of your website all over the world. But instead of paying hundreds of web hosting companies across the world to hold a local copy of your website — not to mention the management of this automatic replication every time a cache is flushed — you just use Cloudflare to do everything on your behalf. Automatically, in the background, effortlessly. And for free.Super Page Cache for Cloudflare is just the key to unlock that potential.Now, to be fair, when you sign up to Cloudflare, by default, it caches very little — some JavaScript, some CSS, and, with luck, a few static images. This is the "bare minimum", or the least common denominator — it will certainly improve things a bit, but not that much. Cloudflare even has their own "official" WordPress plugin, which facilitates the two-way communication between WP and Cloudflare's servers. Nevertheless, Cloudflare's own plugin is not really fine-tuned to perfection. It also implements, by default, a "least common denominator" policy — and making sure that, when a WP author/editor publish an article and requires the cache to be cleared ("flushed"), this request is also forwarded to Cloudflare's network. But "flushing caches" is just one of the hundreds of options given by WP caching plugins. Some plugins, such as W3TC or the WP Fastest Cache plugin, are already "Cloudflare-aware" and can effectively communicate with Cloudflare's API. Most, however, cannot be bothered to be properly configured: they work, sure, but always using the "bare minimum" performance boost you get from a generic default configuration.As such, considering that there are way too many possible ways to configure WordPress itself — not to mention Cloudflare! — it's rather obvious that none of that leads to a simple way to pre-generate a "one-size-fits-all" cache configuration.That said, Super Page Cache for Cloudflare is not one of those "one-size-fits-all" solutions, but a plugin with a very reasonable amount of case-by-case configuration, even for the most basic of scenarios. And that is, unfortunately, the reason why so many reviews say "nothing works" or "impossible to configure". You need to be patient. This is not an entry-level plugin at all: it is a rather sophisticated way of tapping into Cloudflare's caching potential.But configuring Super Page Cache for Cloudflare is just half the story. You need to configure Cloudflare as well. One doesn't work without the other. And I have to say that learning to configure Cloudflare's rule engine so that it works correctly for Super Page Cache for Cloudflare was truly an education: I didn't realise how little I was actually using from Cloudflare's free account.It's not obvious, but once you register with Cloudflare for a free account (or a paid one!), by default, it does not cache most things. You get just CSS and JS caching by default — good if you have insanely huge CSS/JS files — but that's pretty much it.Why? Well, Cloudflare originally would cache most things — including all static HTML retrieved from one's own webserver, images and other media, and so forth. Unfortunately, this only worked so long as, on the Web server side, everything is properly prepared for Cloudflare to work well. What happened was that the vast majority of Cloudflare users (again, especially the free ones!) have no clue about how Cloudflare is configured, or why, or what it does. They have only heard that Cloudflare is great for protecting one's site from remote attacks (true) and that it does some caching (also true). They assume (incorrectly) that there is nothing they need to change on their side. And that inevitably leads to problems — such as dynamic content, generated taking cookies into account, or assuming that certain headers were present, not displaying correctly. A common issue I had with a really basic WP cache plugin was that Cloudflare would sometimes show the mobile page for a desktop user and vice-versa — even though on the WordPress side of things these two cases ought to be handled separately. They were, but... they weren't always detected based on their headers only. And sometimes Cloudflare would just blindingly serve the last version of the page they had cached, no matter who it was for (it was even possible to "leak" in this way pages requiring authentication...).Over the years, therefore, Cloudflare learned their lesson: stop assuming that people have flawlessly configured servers on their side. Instead, go for the bare minimum that will work even with the worst possible configuration, but which, at least, won't "break things". And let so-called "advanced power users" to tweak both configurations (on their local web server and on Cloudflare) to cache whatever can be cached — but with a knowledgeable human being making rational decisions and tinkering with the configuration, not with an "automated" procedure.Super Page Cache for Cloudflare does a neat job on the Web server's side of things. It can be configured to prepare a ready-to-be-served page cache on disk which will be nicely used by Cloudflare, exactly in the way Cloudflare prefers such content to be received. Super Page Cache for Cloudflare, therefore, is all you need to properly "prepare" everything to be served by Cloudflare — but it means that each site will require its own distinct configuration. There will be common things, of course, but they will not be exactly the same under all circumstances. In my experience, there are certain plugin + theme configurations that will not work with Cloudflare (so all you can do is to water your plants while waiting for something to happen). Most will, but they will also need some human help  to properly configure Cloudflare's page rules.And ultimately there's where the magic happens. By enabling the Cloudflare rule engine, and making sure that it understands the format that Super Page Cache for Cloudflare uses to write things to disk — and serves them from disk — you can virtually put your whole website on Cloudflare's cache and serve it from there. With a bit of tinkering, you can do it. But, again, it's not easy to do so, no matter how "automated" your system is, even though Super Page Cache for Cloudflare includes some of the more obvious configurations that you need to deploy.And woe to any major upgrade, which might just scratch your existing configuration — and you have to start over again!


Boosts your WP site beyond belief, but...


Once in a while I come across a plugin that blows my mind, and this is one of those.



It just works.


Worth all the stars


My host sent me a warning that I had used 2.5m dynamic requests in a month, way beyond appropriate limits. As I checked my sites, even though I was on Cloudflare, none of them were getting cache hits. After doing some research on Facebook, someone in Dynamic WordPress recommended this plugin if you're on Cloudflare.



Giving it a try, I found it very easy to configure. I integrated it with my Cloudflare API keys, and the rest was pretty much configuring a few defaults. After clearing server cache and Cloudflare cache, my site began to register cache hits. I've since replicated this across all my sites.



We can't post images here (nor links), but my usage is about 1/100th when using this plugin.



So thank you to the plugin author. I did buy a subscription just to support your work. The extra features I mostly use Perfmatters for.



Thanks for all you do.



Ronald Huereca


This Plugin Should Be Renamed to "Saves My ***"

Boost PageSpeed, SEO, and Core Web Vitals with full page caching, JS/CSS optimization, media optimization, and Cloudflare CDN.

Instant Back/Forward vs Super Page Cache