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
- Managed WordPress Hosting: WP Rocket is allowed and not blacklisted.
- Web & Classic, cPanel, and Plesk Hosting: Their APC cache system can conflict with WP Rocket's cache, so you can turn it off: Disabling APC on Your Hosting Account.
Bluehost Managed WordPress
- Their Varnish configuration breaks WP Rocket's minification, so you must either turn off their Varnish, or turn off our minification.
- Page caching is automatically disabled on Flywheel, 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 now allowed on their system :)
- WP Rocket is compatible with all their caching layers. See this doc for further info:
Can I Use WP Rocket With Siteground's SG Optimizer?
- W3 Total Cache is pre-installed, but you can delete it and install WP Rocket instead, with no problems.
- WP Rocket is the only caching 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. 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.
- The page caching feature of WP Rocket is automatically disabled to prevent conflict with Kinsta’s caching. All other features such as LazyLoad, file optimization, etc. are available.
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:
- They have their own caching system in place that's why other caching plugins, including WP Rocket, are blocked (as per their documentation).
- The page caching feature of WP Rocket is automatically disabled to prevent conflict with Pressable's caching. All other features such as LazyLoad, file optimization, etc. are available.
- 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.
- 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.