Can WPRocket be used on Cloudway Servers

I have a paid license for WPRocket Caching Plugin for Wordpress. I know Breeze plugin comes installed by default. Is Breeze recommended over WPRocket for Cloudways servers?

It seems the paid version of WPRocket offers benefits that Breeze doesn’t offer.


1 Like

If configured correctly, Breeze blows WPRocket out of the water. Not even close from our testing.

So you could use WP Rocket then, but your tests indicate faster caching, I wish it was as easy to fill out and use as WP Rocket Screens. Just saying “configured correctly” doesn’t really help unless you are a power user.

Yes it can and it performs great. In our testing it outperformed all the other caching plugins, including Breeze.

Do some testing and see what works best for you.

Deactivating Breeze and using WP Rocket a shouldn’t cause any problems. Benchmark results depend on your site design, so if you like WP Rocket, go for it. You can always revert back.

Thanks all! I appreciate it!

I agree with Luke1 - WP Rocket works better for our server, which is on DigitalOcean. We were seeing weird issues with Breeze, but cannot recall exactly what those issues were. WP Rocket definately performed better and as I recall, is more stable. As others suggested, test both and see which one works best for your set up as it will be different then ours.

WP-Rocket delivers great speed on my Digital Ocean server.

However, cache preloading kills my 1 core CPU (idle CPU drops down to 0)… I wish Cloudways started to offer the DO plans with 2 and 3 cores which I mentioned here:

When I had Varnish activated, WP-Rocket was not able to preload many URLs (I checked FTP cache folders).
I recently noticed that the issue persists even with Varnish deactivated, but it doesn’t affect as many URLs.
Perhaps 20% of all URLs that should be preloaded according to the sitemap, are not. And it’s not always the same URLs in each purge-preload cycle.

Has anybody noticed the same issue? php-app.access.log doesn’t show any errors… everything with status 200 for wp-rocket sitemap-preload.

Did you ever find a solution to this? Thanks!

If your site is particularly heavy or has a lot of pages on a 1 core server it’s best to change the preload interval. WP Rocket has a plugin if you check their documentation on preloading. Default is 0.5s, but on large or heavy sites I find it best to change this to 3s, experiment with your site and see what works for you.

Also it’s worth considering whether or not sitemap preloading is the best option. On most sites I find setting a longer cache expire works well and just using the standard preload option which includes all links it can find from your homepage. A lot of sitemaps include pages that often won’t be visited often, old content and certain category pages etc, no need to preload these every time. Simply have a longer cache expire of say 3 days, and cache the frequently accessed content.

1 Like

I have two wordpress sites, one with Rocket, the other with Breeze. On the first site I tried four other popular caching plugins before trying Rocket.

In my experience, Rocket just demolishes everything else, in terms of performance, features, interface, and support. It’s a very, very advanced product.

I’m keeping Breeze on site #2 because performance isn’t as important, and so I’m interested in a free and well-supported plugin.

My server (which runs both sites) is a single-cpu Vultr server. No problems with server load during page preloads. But I set thepreload interval a bit lower than the max, and also have the heartbeat set to reduce theload. I have other plugins that tax the server much more.

We have a WP ML site with a very slow theme on a DO vps. Breeze was OK but WP Rocket is almost instant loading.

It depends on your exact site. No one solution works across the board for every site.

You may use WPRocket or any other caching plugin of your choice. However, if you wish to use Varnish then you need to configure its settings manually inside the plugin. You may also contact our support for this.

Note: Take a full backup or create a staging site of your live site before implementing any major changes.

Ibad Rehman