Common Questions for WP Cloudflare Super Page Cache

1. Can I use this plugin to take advantage of Cloudflare's Cache Everything rule, bypassing the cache for logged-in users even if I'm using the free plan?

Yes! This is the main purpose of the plugin.

2. Does this plugin also perform CSS and Javascript optimizations?

No, this is a caching plugin. To perform other page optimizations you can use it together with other performance plugins such as Autoptimize, WP Rocket, or any other optimization plugin.

The purpose of this plugin is to get you the lowest possible response times (Time to First Byte aka TTFB) by using Cloudflare as a page caching system while maintaining full control of the cache.

3. What is the swcfpc=1 parameter I see attached at the end of every internal link when I'm logged in?

It is a cache buster. Allows you, while logged in, to bypass the Cloudflare cache for pages that could be cached.

It is added to all internal links for logged-in users only. It is disabled in Worker mode.

4. Can I restore all Cloudflare settings as before the plugin activation?

Yes! You can by clicking on the Reset all button at the top of the plugin settings.

5. Why do all the pages have "BYPASS" as the cf-cache-status?

Cloudflare does not add in cache pages with cookies because they can have dynamic contents. If you want to force this behavior, strip out cookies by enabling the option Strip response cookies on pages that should be cached.

6. What is Fallback Cache?

Fallback Cache is an option to generate a static HTML version of the web pages inside your site. This is a great option and can increase your site speed dramatically. The way Cloudflare works is that it will only cache a page to its global CDN network if it has received any request for those pages. So, if you don't have a fallback cache, for the first few requests, your server will be executing the pages and sending the HTML to the user, which increases slowness and latency.

Our fallback cache system follows the same standard that Cloudflare follows when it caches a page to its CDN edge. This way we generate the HTML version of the webpage before a user has requested that page. By doing this, when any user accesses the webpage for the first time, the page loads super fast as it is already loading a rendered HTML rather than waiting for the server to generate HTML and pass that to the users.

Our fallback cache system works way better than any other disk cache system and plugins out there in the market. In short, now you don't need to install any other caching plugin in conjunction with WP Cloudflare Super Page Cache, as the plugin can now handle Cloudflare caching and disk caching.

7. What is Preloader and how it works?

The preloader is a simple crawler that is started in the background and aims to preload pages so that they are cached immediately.

Once the preloader is enabled, you need to specify which preloading logic to use among those available You can choose a combination of options (sitemaps, WordPress menus, recently published posts, etc ..).

It is also possible to automatically start the preloader when the cache is cleared.

In order to avoid overloading the server, only one preloader will be started at once. It is therefore not possible to start more than one preloader at the same time. Furthermore, between one preload and the other, there will be a waiting time of 2 seconds.

If you want to run the preloader in the middle of the night when you have low users, you can run the preloader over the CRON job as well.

8. What is the difference between Purge Cache and Force purge everything actions?

If the "Purge HTML pages only" option is enabled, clicking on the "PURGE CACHE" button only HTML pages already in cache will be deleted from Cloudflare's cache.

If for some reason you need to delete static files (such as CSS, images, and scripts) from Cloudflare's cache, you can do so by clicking on "Force purge everything".