Hosting compatibility

WP Rocket is compatible with 99% of hosts.  Due to the specifics of some hosting platforms, there may be some particular considerations. If you come across a hosting company that wants you to remove WP Rocket, please let us know so that we can contact them directly to become compatible.

Note: If your hosting company is not listed here, it doesn’t mean their hosting is not compatible with WP Rocket. Quite the opposite, in most cases it will mean WP Rocket works just fine on their hosting environments, so there isn’t anything to be pointed out about them in this document.

In this article

BigScoots

  • WP Rocket is automatically compatible with the BigScoots platform.
  • For users of the BigScoots Cloudflare Enterprise: WP Rocket page caching is automatically disabled and Cache Lifespan feature will not work, but all other optimizations will still be applied.

Cloudways

If you subscribe to Cloudflare Enterprise plan within your Cloudways hosting plan, WP Rocket won't be able to synchronize its cache with Cloudflare's in this case because Cloudways does not provide you with an API key and zone ID you can add to configure our Cloudflare add-on.

You'll need to purge the Cloudflare cache yourself each time you change the WP Rocket settings, or disable WP Rocket's page caching to keep only the optimizations. See: Disable page caching

We have, however, set up compatibility with Cloudflare APO if you're interested: Using Cloudflare APO with WP Rocket

DreamPress

  • WP Rocket is automatically compatible with DreamHost's DreamPress platform:
  • Page caching is automatically disabled and Cache Lifespan feature will not work, but all other optimizations will still be applied
  • Varnish add-on is auto-enabled and will keep the cache clearing synchronized
  • HTML expires rule is removed from htaccess to allow for proxy caching
  • WP_CACHE is not required and is set to 'false'

GoDaddy

Flywheel

  • Page caching is automatically disabled on Flywheel and Cache Lifespan feature will not work, but all other optimizations will still be applied.
  • To use WP Rocket, you must turn on Enable WP_CACHE  from the Advanced tab of your Flywheel site card dashboard:

  • If you want to use Flywheel's CDN and WP Rocket's file minification, retrieve your unique Flywheel CDN domain from your website’s source code, or ask Flywheel’s support about it. Then enter your CDN domain in the CNAME field on WP Rocket’s CDN settings panel, and activate the checkbox “Enable Content Delivery Network” on the same panel.
  • WP Rocket automatically detects if you use Flywheel and auto-purges their Varnish caching when your WP Rocket cache is purged. 

Hostgator Managed WordPress Hosting

  • WP Rocket is allowed on their system.

Hostinger

  • You can use both Hostinger's Automatic Cache along with WP Rocket: https://support.hostinger.com/en/articles/6215624-how-to-use-cache-manager. However, as Hostinger recommends, and because from WP Rocket's side there is no automatic compatibility yet, you'd need to clear Hostinger's cache when you've made changes in your site, unless you're fine with their current 30 minutes cache lifespan.
  • For the Hostinger's CDN, it's a server proxy (like Cloudflare) and not a CDN like RocketCDN. We don't have a compatibility with it and we recommend you to keep it off.

Nexcess

Nexcess has a custom plugin called Nexcess, which has its own page caching option, at Cache Status > Enable the site cache. This feature is not compatible with WP Rocket's page caching, and it's recommended to keep it deactivated.

RunCloud

  • RunCloud is technically a server management panel rather than a host. But they added compatibility to their RunCloud Hub plugin to ensure that cache purging is synchronized.
  • Our page cache is disabled and Cache Lifespan feature will not work. This includes Separate cache files for mobile devices.
  • WP Rocket rewrite rules and the max-age: 0 for HTML files will be removed from the htaccess file.
  • RunCloud Hub plugin will disable mandatory cookies and hide the Varnish add-on.

Savvii

  • WP Rocket is compatible with Savvii hosting.
  • Our page cache is disabled and Cache Lifespan feature will not work but all other features will work. 
  • Cache purging is synchronized between WP Rocket and Savvii's cache.

Siteground

SpinupWP

  • WP Rocket is compatible with SpinupWP hosting.
  • Our page cache is disabled and Cache Lifespan feature will not work, but all other features will work. 
  • Cache purging is synchronized between WP Rocket and SpinupWP's cache.

Synthesis

  • W3 Total Cache is pre-installed, but you can delete it and install WP Rocket instead, with no problems. 

WP Engine

  • WP Rocket is the only optimization plugin that is allowed on their system. We worked closely with their team to meet their requirements. 
  • The page caching feature of WP Rocket is automatically disabled to prevent conflict with WP Engine's caching. For this reason features related to caching will not work (Cache Lifespan, User Cache and Always Purge URLs). All other features such as LazyLoad, minification etc. are available.
  • WP Rocket automatically detects if you use WP Engine and auto-purge their Varnish caching when your WP Rocket cache is purged. 
  • WP Rocket will automatically be allowed on your staging site even if you have a Single license. Staging won't count as an additional site.
  • If you are using WP Engine's Global Edge Security or advanced network, you should keep the CDN option in WP Rocket disabled. Both services have the CDN feature at the DNS level.
  • WP Engine has deprecated the use of the htaccess file. They apply those related optimizations in their server configuration instead. WP Rocket does not require the use of the htaccess file on WP Engine - all features will still work as expected.
  • WP Rocket will not create an advanced-cache.php file on WP Engine sites.
  • WP_CACHE is not required and is set to 'false'.
  • If a URL contains `utm_` or `gclid`, WP Engine will handle it as if there were no query string on the request. This behavior can be problematic if the page has conditional content depending on any URL parameter values.

Kinsta

  • The page caching feature of WP Rocket is automatically disabled to prevent conflict with Kinsta’s caching and Cache Lifespan feature will not work. All other features such as LazyLoad, file optimization, etc. are available.
  • Kinsta’s CDN is powered by Cloudflare therefore it will work automatically with WP Rocket. Checking the “Enable Content Delivery Network” option is not required.
  • Kinsta’s full page caching and OPcache is disabled by default on staging sites, so you’ll get no cache at all. If you try to run website speed tests you will see higher than average load times due to the fact that the pages aren’t being served from cache.

Amazon Lightsail (Bitnami)

  • In Bitnami environments, the .htaccess file may not be available for WP Rocket to work automatically. To resolve, use the helper plugin below to disable the use of the .htaccess file for those environments:

    📥  Download (.zip): WP Rocket | No .htaccess
    Developers: You can find the code for this plugin on GitHub.

  • The Bitnami stack has PageSpeed Module (mod_pagespeed) enabled by default. It needs to be disabled to avoid conflicts with WP Rocket. To disable it, please follow the steps provided in this Bitnami documentation: Disable PageSpeed

WordPress.com

  • WP Rocket is the only caching plugin allowed on sites hosted at WordPress.com.
  • The page caching feature of WP Rocket is automatically disabled to prevent conflict with WordPress.com’s caching and Cache Lifespan feature will not work. All other features such as LazyLoad, file optimization, etc. are available.
  • WP Rocket can only be installed and used If you have a Business or eCommerce plan. If you have a Personal or Premium plan you’re not allowed to install WP Rocket nor any other plugin on your site(s).
  • We recommend disabling the Page Optimize plugin to prevent conflicts with WP Rocket.
  • WP_CACHE is not required and is set to 'false'

Pantheon

The permissions restrictions can be bypassed when one of the following alternatives is implemented:
  • Creating a symlink for the advanced-cache.php file and manually creating the file in the uploads folder. Please see this article for more info. 
  • Customizing the cache folder and config file as shown in this article.

Pressable

  • The page caching feature of WP Rocket is automatically disabled to prevent conflict with Pressable's caching and Cache Lifespan feature will not work. 
  • All other features such as LazyLoad, file optimization, etc. are available.
  • WP_CACHE is not required and is set to 'false'

Presslabs

WP Rocket disables the page caching feature in this hosting.

Additionally, Presslabs relocates the  cache and wp-rocket-config folders to the uploads folder, in these paths:

  • /uploads/wp_rocket/cache/
  • /uploads/wp_rocket/config/

Pressidium

  • WP Rocket's cache is be cleared when Pressidium cache is.
  • Pressidium cache is purged when WP Rocket's cache is.
  • The Varnish Add-on will be automatically activated and configured.

RAIDBOXES

  • WP Rocket is compatible with RAIDBOXES. However, you must first deactivate the server-side cache of RAIDBOXES in the settings of your box, if you want to use WP Rocket.
    RAIDBOXES-Cache deaktivieren
  • Alternatively, you can use RAIDBOXES' caching system and disable WP Rocket's Cache.
  • When you turn off WP Rocket, you'll see a warning that certain entries in the wp-config.php cannot be changed. That's the case with RAIDBOXES. Just click the Force Disabling link in the alert.

Webempresa

  • Webempresa has an optional custom plugin called WE Varnish Cache, which disables the cache generation of WP Rocket. This is because they are caching the pages using Varnish on their server instead, when their Magic Cache is enabled. 
  • All the other features of WP Rocket will still work as expected. 
  • You should aivate the Varnish add-on to synchronize cache purging.

WPX Cloud

  • Varnish add-on is auto-enabled and will keep the cache clearing synchronized.
  • HTML expires rule is removed from htaccess to allow for their CDN caching.
  • Preload may be disabled by default to avoid CPU issues, but it can be enabled by request if you contact their support.
  • In WPX suggested WP Rocket settings the Preload and Remove Unused CSS features are disabled, and most of the scripts are excluded from the Delay JavaScript execution feature.

    To get the most out of WP Rocket, it's recommended to enable the features and remove the exclusions, one by one, making sure there are no issues.
Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.