If you’re hosting your WordPress site with SiteGround, you get multiple ways to optimize its performance. You get built-in caching via SiteGround’s SuperCacher, and they also offer a companion SG Optimizer plugin to make other performance tweaks.

So, if you’re already using those tools, do you need to do anything else to optimize your site? More specifically, does it still make sense to use a comprehensive WordPress performance plugin such as WP Rocket?

In this post, I’m going to try to answer that question with real data. First, I’ll explain exactly what’s happening with SiteGround’s optimization, as well as how WP Rocket fits in. Then, I’ll run a bunch of performance tests to try to figure out if WP Rocket makes a difference.

What’s the Difference Between WP Rocket and SiteGround’s SuperCacher?

On their GrowBig and GoGeek plans, SiteGround include their own SuperCacher caching solution, as well as a free SG Optimizer companion plugin, which is listed at WordPress.org.

Before I get to the testing, let’s compare what the SuperCacher functionality and SG Optimizer do, versus what WP Rocket does.

SiteGround SuperCacher and SG Optimizer Explained

SiteGround’s SuperCacher adds three levels of caching:

The SiteGround SuperCacher functionality

  • Static Cache — stores your static files, including images, CSS, JS and so on, in your server’s RAM, which means they’re served from RAM instead of your hard drive.
  • Dynamic Cache — this offers full-page caching powered by Nginx, and is equivalent to what most WordPress page caching plugins do (including WP Rocket, though the exact mechanism is different). It takes the end-product of WordPress’ PHP and stores it as a static HTML.
  • Memcached — this is object caching. It lets you store database queries in the cache, so you can deliver data from there, rather than querying your database each time.

In addition to the SuperCacher, SiteGround also have their own free SG Optimizer plugin, which comes installed by default with all new WordPress installs at SiteGround. This plugin integrates with the SuperCacher functionality to let you control your cache settings from your WordPress dashboard, and it also adds a bunch of other performance improvements, such as:

  • GZIP compression
  • Browser caching
  • Minification and concatenation
  • Image optimization
  • Lazy loading

You can learn more about SiteGround in our full SiteGround review.

WP Rocket Explained

WP Rocket

WP Rocket is a popular WordPress caching and performance plugin.

It adds page caching, as well as a huge number of other performance tweaks. Some of these tweaks are also offered in the SG Optimizer plugin, but you also get unique features.

It offers:

  • GZIP compression
  • browser caching
  • minification and concatenation
  • lazy loading
  • CDN integration
  • Heartbeat API control
  • database optimization
  • optimization for Google Analytics and Facebook Pixel scripts
  • a bunch of smaller tweaks, such as disabling emojis.

It also gives you more control over how your cache functions, with features such as:

  • cache preloading, which lets you automatically load your content into the cache, so every visitor gets served cached content
  • separate caches for mobile users and/or logged-in users

You can learn more in our full WP Rocket review.

Can You Use Both at the Same Time? How Does It Work?

Yes! That’s the beautiful thing, and kind of the point of this post. The two are fully compatible, so you can use all three levels of SiteGround’s caching and the SG Optimizer plugin, while also using all of WP Rocket’s functionality.

Unlike our WP Engine with WP Rocket post, WP Rocket does not disable its page caching when you use it with SiteGround’s SuperCacher.

Instead, your site will have both full-page caching via Nginx at the server level (SiteGround), as well as page caching at the file/application level (WP Rocket).

When someone visits your site, your server will first try to serve the page from the Nginx cache. However, if the page isn’t in Nginx’s cache yet, then WP Rocket can serve it from WP Rocket’s page cache instead (which is totally possible because of how WP Rocket includes cache pre-loading). So, instead of the Nginx cache miss resulting in a visitor seeing an uncached page, they still get served a performance-optimized cached page from WP Rocket.

Additionally, WP Rocket’s purge functionality integrates with SiteGround’s cache. That is, if you purge the cache via WP Rocket, WP Rocket will purge both SiteGround’s Nginx cache and WP Rocket’s cache.

While there are no compatibility issues with the caching functionality itself, there is some overlap with some of the other performance features in the SG Optimizer plugin.

If you opt to use both WP Rocket and SG Optimizer, you’ll want to disable GZIP compression and browser caching in the SG Optimizer plugin because WP Rocket applies those optimizations by default.

In fact, SiteGround will automatically disable any overlapping functionality for you, as I discovered when I uploaded WP Rocket to my SiteGround site:

SiteGround with WP Rocket

You’ll still be able to use a ton of other WP Rocket features, including:

  • separate cache for mobile devices or logged-in users
  • optimize CSS delivery
  • lazy loading
  • replace YouTube iframe with image
  • database optimization
  • Heartbeat control
  • Etc.

What I’m Testing

To figure out how much value WP Rocket adds vs SiteGround’s built-in caching and optimization solutions, I’m going to test two scenarios:

  1. SiteGround with just the SuperCacher (all three levels) and SG Optimizer plugin. I’ll activate all of the other optimization features, including minification, GZIP compression, and lazy loading.
  2. SiteGround with SuperCacher, SG Optimizer, and WP Rocket (I’ll disable any overlapping features to avoid compatibility issues).

My test site uses a full demo from the Avada theme, which should do a good job of simulating a real WordPress site. You can see a full screenshot of the test page here.

Basically, I’m trying to answer the question: Is there any performance value to using WP Rocket on top of the optimizations you already get with SiteGround?

To gather the test data, I’ll use WebPageTest with the following configuration:

  • Test location: Chicago.
  • Connection Throttling: Fios 20/5 Mbps (which is about the average internet speed in the USA).

For each scenario, I’ll run ten separate tests on three different days — 30 tests total for each scenario. Then, I’ll put all of the data together at the end and try to draw some conclusions.

Day One Results:

Only SuperCacher and SG Optimizer:

Mean Load Time: 3.46 seconds.

Test 1Test 2Test 3Test 4Test 5
3.404 s4.118 s3.969 s4.394 s3.048 s
Test 6Test 7Test 8Test 9Test 10
3.391 s3.464 s2.821 s3.204 s3.669 s

After activating WP Rocket:

Mean Load Time: 4.15 seconds.

Test 1Test 2Test 3Test 4Test 5
5.510 s2.954 s4.422 s4.674 s3.058 s
Test 6Test 7Test 8Test 9Test 10
2.755 s3.312 s4.139 s4.993 s5.657 s

Day Two Results:

Only SuperCacher and SG Optimizer:

Mean Load Time: 3.95 seconds.

Test 1Test 2Test 3Test 4Test 5
3.809 s5.081 s4.291 s3.714 s3.415 s
Test 6Test 7Test 8Test 9Test 10
2.811 s3.259 s2.954 s3.425 s6.749 s

After activating WP Rocket:

Mean Load Time: 3.33 seconds.

Test 1Test 2Test 3Test 4Test 5
4.789 s3.153 s2.979 s3.985 s2.682 s
Test 6Test 7Test 8Test 9Test 10
3.845 s2.646 s3.700 s2.757 s2.764 s

Day Three Results:

Only SuperCacher and SG Optimizer:

Mean Load Time: 3.63 seconds.

Test 1Test 2Test 3Test 4Test 5
3.622 s3.859 s4.284 s3.361 s3.129 s
Test 6Test 7Test 8Test 9Test 10
3.525 s3.304 s4.372 s3.539 s4.214 s

After activating WP Rocket:

Mean Load Time: 3.43 seconds.

Test 1Test 2Test 3Test 4Test 5
3.811 s2.661 s3.640 s2.836 s3.643 s
Test 6Test 7Test 8Test 9Test 10
3.291 s5.766 s2.873 s3.318 s2.490 s

Putting it Together: Is it Worth Using WP Rocket with SiteGround?

Okay, so after running 30 separate tests on three separate days for each situation, here’s how things shook out:

Overall AverageDay One AverageDay Two AverageDay Three Average
Just SG Optimizer3.68 s3.46 s3.95 s3.63 s
SG Optimizer + WP Rocket3.64 s4.15 s3.33 s3.43 s

Those numbers are pretty dang even, which leads me to believe there’s not a big difference between just going with SiteGround’s SuperCacher and the SG Optimizer plugin, versus using WP Rocket.

WP Rocket certainly didn’t have a negative impact, but I’m not sure I can call that 0.04 second improvement significant.

So, from purely a page load time perspective, I’d say you don’t need to spring for WP Rocket if you’re already hosting with SiteGround.

However, I do think there are a few things that aren’t represented in the test data that may still make WP Rocket a good option to pair with SiteGround.

SiteGround Don’t Have Cache Preloading

Before running all of these tests, I opened the test page in my own Incognito browser to give SiteGround a chance to load the page into their cache. However, that won’t always happen in real life, and on a live site you’d have some people hit uncached pages because SiteGround don’t do cache preloading.

However, WP Rocket does, which eliminates that situation. Remember — if you combine WP Rocket with SiteGround’s caching, you basically have two levels:

  • SiteGround’s Nginx caching at the server level.
  • WP Rocket’s page caching at the file/application level.

So, because WP Rocket has already preloaded your content into its cache, it can still serve up a quick-loading cached page even in situations where SiteGround’s Nginx cache misses.

WP Rocket Still Does More Than SG Optimizer

Second, WP Rocket still just plain does more than SG Optimizer, even if those tweaks didn’t translate into big differences in the page load tests.

For example, WP Rocket adds extra features, such as Heartbeat API control and database optimization, which SG Optimizer doesn’t have. WP Rocket can also help you to optimize third-party tracking scripts, such as Google Analytics and Facebook Pixel.


If you’re already using SiteGround’s SuperCacher and SG Optimizer, WP Rocket definitely isn’t a must-have plugin for performance. However, it still does offer some small improvements, so, if it fits your budget, it still may be worthwhile pairing the two.

And, again, the two are built to integrate with each other, so you won’t hit any compatibility issues in doing so. SG Optimizer will automatically disable its duplicate features to avoid a conflict, and you’ll also be able to purge the SiteGround cache through the WP Rocket interface.

Used/using SiteGround or/with WP Rocket? Thoughts or opinions?


Leave a Reply