Skip to content

Third Party Integrations for Super Page Cache

One of the best ways to have a super-fast website is to use the caching method. A cache is a reserved storage location that collects temporary data to help websites, browsers, and apps load faster. Whether it's a computer, laptop or phone, web browser or app, you'll find some variety of cache. In our case, the cache is used for the static elements of the website so when a user visits your website, it will load faster.

Although the cache is a wonderful thing, sometimes more of the same thing is not the way to go. In this case, having multiple caching plugins or methods of cache for your website can result in errors, malfunctions, and other types of bad behavior that you would not like to experience, thus we would recommend you to stick to one method and apply it correctly.

Here are the most common questions users might have related to our plugin's third-party integrations.

Does it work with Litespeed Server?

Yes, but if you are using a LiteSpeed Server version lower than 6.0RC1, disable the option Overwrite the cache-control header for Wordpress's pages using web server rules. You can keep this option enabled for Litespeed Server versions equal to or higher than 6.0RC1.

How does this plugin work with Kinsta Cache?

If you are using Kinsta hosting, you can integrate this plugin to work with Kinsta Server Level Caching and to ensure when you Purge Cache via this plugin, it not only purges the cache on Cloudflare but also on Kinsta Cache. You can enable this feature by going to the Compatibilities tab of the plugin settings and enabling Automatically purge the Kinsta cache when Cloudflare cache is purged. It is also recommended that if you are taking advantage of the Kinsta Server Caching (Recommended), please ensure that the Enable Disk Page Cache option is turned OFF.

After purging the cache from our plugin, it gets deleted from both Kinsta & Cloudflare Cache. Now when you visit the webpage for the first time after purging the cache, you will get cache response headers as MISS/EXPIRED, etc. for both Cloudflare and Kinsta cache.

At this point, after receiving the first request both Cloudflare & Kinsta caches the page on their own platforms respectively. But do note that when Cloudflare is caching the first request at this point the x-kinsta-cache header is of status MISS. For the second request when Cloudflare serves the page from its own CDN Edge servers without sending the request to the origin server, it keeps showing the x-kinsta-cache cache header as MISS. Because when Cloudflare cached the page the response header was MISS but Kinsta caching system has already cached it upon receiving the first request.

Now if you purge the Cloudflare cache only (on Cloudflare dashboard) or enable development mode in the Cloudflare dashboard so that the request doesn't get served from Cloudflare CDN, you will see the x-kinsta-cache showing as HIT, because this time the request is going to your origin server and you are seeing the updated response headers that are being served by the server.

If you run a WooCommerce store on Kinsta with Cloudflare, apply the following configuration to cache public pages while keeping cart and checkout behavior correct:

  1. Go to Super Page Cache → Compatibilities.
  2. Under Kinsta settings, enable Automatically purge the Kinsta cache when Cloudflare cache is purged.
  3. Enable Automatically purge cache for product page and related categories when stock quantity changes to keep product pages current after inventory updates.
  4. Enable Automatically purge cache for scheduled sales to clear product pages when a sale starts or ends.
  5. Verify that Cart, Checkout, Checkout's pay page, and My Account page are checked under Don't cache the following WooCommerce page types.
  6. On the General tab, disable Enable Disk Page Cache — Kinsta's server-level caching handles page storage.

📝 Note: Cookie-based bypass is handled automatically. Logged-in users and visitors with an active WooCommerce session cookie bypass the cache without any extra configuration.

⚠️ Important: On stores with more than 10,000 products, enabling the automatic stock purge setting can trigger hundreds of URL purges simultaneously and cause Cloudflare API rate-limit errors. See How to Optimize Cache for WooCommerce Stores for guidance on targeted purging.

Advanced: Cache Tags for high-traffic stores (Pro)

Cache Tags let the plugin invalidate only the pages affected by a content change — a single product, category, or author — instead of purging the full cache. This reduces uncached requests after updates and is especially useful for high-traffic WooCommerce stores where a full purge would cause a temporary load spike on the origin.

Cache Tags is a Super Page Cache Pro feature. To enable it, go to Super Page Cache → General, turn on Show Advanced Settings, then open the Advanced tab and enable Enable Cache Tags.

For full setup instructions, see Cache Tags in Super Page Cache Pro.

Can I use this plugin together with Litespeed Cache?

Yes, you can! You have only to disable its page caching functionality. To do this:

  1. Go to Litespeed Cache > Cache
  2. Click on OFF near Enable Cache
  3. Click on the Save Changes button

Then:

  1. Enter to the settings page of this plugin
  2. Click on the Third-Party tab
  3. Scroll to the Litespeed Cache Settings section
  4. Enable the option Automatically purge the cache when LiteSpeed Cache flushes all caches
  5. Purge the cache

Can I use this plugin together with Autoptimize?

Yes, you can! It is highly recommended to enable the option Enable 404 fallbacks of Autoptimize.

Can I use this plugin together with WP-Rocket?

Yes, you can! Please follow these steps:

  1. Disable WP-Rocket and make sure no advanced-cache.php files of other plugins are in the wp-content directory
  2. Enable this plugin
  3. Enable the Fallback Cache option
  4. Click on the Third-Party tab
  5. Scroll to the WP-Rocket Cache Settings section and enable all the options
  6. Purge the cache
  7. If you are not under LiteSpeed Server or are you using LiteSpeed Server version >= 6.0RC1, enable the option Overwrite the cache-control header for Wordpress's pages using web server rules
  8. Enable WP-Rocket again
  9. Purge WP-Rocket cache

Can I use this plugin together with other page caching plugins such as Cache Enabler, WP Super Cache, and WP Fastest Cache?

No. The support for these plugins was removed because you can use the fallback cache option of this plugin if you want to use a standard page cache behind Cloudflare. In order to avoid conflicts, it is strongly recommended to use only this plugin as a page caching system.

Can I use this plugin together with Varnish Cache?

Yes, but you don't need it. If you want to use a standard page cache behind Cloudflare, enable the fallback cache option of this plugin. In order to avoid conflicts, it is strongly recommended to use only this plugin as a page caching system.