Table of Contents

Delivering a great user experience is more crucial than ever – you’re probably aware of it. Do you also know how to make a great first impression when new users visit your website? The easiest way is to take advantage of the preload cache option.

And preload cache is exactly at the center of our new major release. Say hello to WP Rocket 3.12! Our latest version focuses on enhancing the Preload Cache feature, making it more reliable and effective in improving user experience.

Keep reading and learn what WP Rocket 3.12 entails for your site. You’ll discover why we decided to work on Preload Cache and how your site will benefit from enabling the new option right away.

Read until the end of the blog post – there’s also an announcement all Rocketeers were waiting for!

Introducing the New Preload Cache Feature

Let’s take a step back and understand why preload is important for enhancing user experience and what’s the difference between cache and preload cache.

When you enable WP Rocket without the Preload Cache option, users landing on your site for the first time will experience a pretty slow page. That’s normal because it’s just the first session, and the pages are not cached yet. In fact, the cache will be generated after the first visit. So, the same pages will load much faster during the second and subsequent sessions. 

What happens when you take advantage of the Preload Cache? In this case, users will get a faster page as soon as they visit the website for the first time. That’s possible because the preload cache option will simulate a visit to that page before any user session. So, when users land on the same page for the first time, they will immediately get the cached version. That’s helpful, especially because a bad first impression on your site could mean that users will leave and never return. A cached version also allows search engine bots to visit the pages quicker and improve page indexation and crawling budget.

Can you see why Preload Cache is a great asset to improve user experience and optimize SEO performance?

Of course, we do! That’s why we focused on revamping the Preload Cache feature for WP Rocket 3.12. The previous Preload Cache option didn’t provide the most effective results because the process could be a bit slow or incomplete – meaning that not all URLs would be preloaded. As a result, some pages could still be too slow when visited for the first time.

And there was something more. Looking at some usage data about WP Rocket 3.11, we noticed that not all our customers would take advantage of such a useful feature.

On the one hand, 89% of Rocketeers enabled the Activate Preloading option to preload only the homepage and the links included on the page. 

The old Activate Preloading option 
The old Activate Preloading option 

On the other hand, only 48% also activated the Sitemap-based cache preloading option – which would fetch the sitemap and preload almost all URLs.

The old Sitemap-based cache preloading option
The old Sitemap-based cache preloading option

We realized there was room for improvement for the feature itself and the adoption from our users. Preload greatly affects user experience and can impact websites, starting from their conversion rate.

We aimed to make the Preload Cache option easier, more reliable, and more powerful when providing a better UX to anyone browsing our users’ websites.

You can watch our video or jump to the next section to find out what we achieved.

What Are the 3.12 Preload Improvements and Changes?

The biggest 3.12 enhancement entails the way the feature works. When enabled, the Preload Cache option will always preload all URLs. This is possible because WP Rocket automatically looks for one of the most popular sitemaps so that it can preload all pages by default. If the plugin can’t find any sitemap, it will use the WordPress built-in sitemap as a fallback.

In short, WP Rocket will always find a way to grab all the URLs and preload them. 

Moreover, the URLs and data are now stored in a database. In other words, there isn’t anything that could block the preload process or slow it down –  it’s an asynchronous process running in the background.

The other change involves what you’ll find in the Preload tab. The Preload Cache feature now includes only one option to preload all the website’s URLs. So, you don’t need to tick two boxes for the homepage and the sitemap anymore. Instead, just flag the Preload Cache feature, and the plugin will take care of everything.

The new Preload Cache option – WP Rocket 3.12

You’ll now get a different message. In the current notice, there is no counter. This is because preload is supposed to be ongoing, so no counter will be accurate. Every time a page’s cache is deleted, it should be preloaded automatically.

The Preload message 

You’ll also see new messages in the menu and the dashboard tab. 

You won’t find “Preload cache” in the menu anymore.

Old Preload Cache button - Menu
Old Preload Cache button – Menu

In the dashboard, the option about Preload Cache is also gone.

Old Quick Actions - Dashboard
Old Quick Actions – Dashboard

Here’s what you’ll find instead.

  • If Preload is enabled, you’ll see a “Clear and preload cache” button in the menu. 
The new button when Preload Cache is enabled – Menu

If you go to the dashboard tab and look for the Quick Actions button, you’ll find the same option to Clear and Preload Cache.

The new button when Preload Cache is enabled – Dashboard
  • If the Preload is disabled, the button will only say “Clear Cache”.
The new button when Preload Cache is not enabled – Menu

You’ll find the same “Clear Cache” button in the dashboard tab.

The new button when Preload Cache is not enabled – Dashboard

What Will Happen to Your Old Preload Cache Option?

You may wonder what happens to your existing option once you update your WP Rocket version to 3.12.

That’s easy. If you had at least one of the old preload features activated in 3.11, you’d get the feature enabled when updating to 3.12. Of course, we highly encourage you to activate the Preload Cache feature if you previously didn’t do it.

The more websites using WP Rocket 3.12 with Preload Cache enabled, the better. As explained, the option will provide a better user experience to all users landing on your websites for the first time – and that’s what we would like to see more and more!

Why Your Site Performance Will Benefit From the New Preload Cache

We’re glad we achieved all the goals we had in mind when we decided to work on enhancing the Preload feature. And here’s why you should enable the revamped option right away.

  1. You’ll benefit from complete and reliable cache preloading. As mentioned above, the feature will always preload all the URLs. It doesn’t matter what happens to the cache – for instance, if it’s deleted. WP Rocket will always have all the information stored in the database. As a result, no matter what, the cache will be available and provide users with pages loading fast from the first session. 

    The plugin will keep the same compatibilities with the following sitemaps: All-in-one SEO, Yoast, Rank Math, SEOPress, and the SEO Framework. In addition, there will always be a fallback to WordPress built-in in case there would not be any sitemap to crawl.
  1. You’ll get the easiest Preload Cache ever. Now you only have one option to flag to preload all your website’s pages — no need to worry about anything else.
  1. You’ll provide your new users with a better first impression. A great user experience is essential for conversion rate – just to mention one of the reasons why visitors should enjoy the best possible experience on your website. Hopefully, the revamped feature will allow more and more users to enjoy our Rocketeers’ sites.

Remove Unused CSS: Goodbye, Beta Version!

That’s right: WP Rocket 3.12 comes with the finalized Remove Unused CSS. This powerful feature now works completely well, and it was time to remove the Beta mention for good. 

Remove Unused CSS is one of the most powerful WP Rocket features. It makes it easy to tackle CSS optimization, improve Core Web Vitals and boost the PageSpeed Insights score. Don’t take our words for granted – enable the option and see it yourself!

Remove Unused CSS - File Optimization
Remove Unused CSS – File Optimization

Wrapping up

Are you ready to try the new Preload Cache feature that comes with WP Rocket 3.12?

You’ll get your website’s pages cached and fast for all new users. A great first impression is essential to let visitors browse your site, enjoy their experience and return.

Preload Cache is a no-brainer option. Thanks to WP Rocket 3.12, you need just one click to activate it. The icing on the cake is that the new major release also comes with removing the Beta version for the Remove Unused CSS feature – one of the most effective options to improve your site performance easily.

Give it a try, and let us know your experience in the comments!

Comments (32)

Interesting changes but in the case of Woocommerce site where there are many product links in sitemap is not optimal server-wise to preload all products. There should be an option to manually add a sitemap to preload or exclude links from existing popular sitemaps, like in my case from the YOAST sitemap.

Don’t take our words for granted = the best

I LOVE rocket and I am paid till 2024!

I have just upgraded to the latest version 12 and followed the new
Setup steps.

And now my website speed is - Desktop 100
Mobile 89

And I am wondering why the Mobile is still low?
any help would be greatly appreciated - thank you

Does the Preload Cache also work with Varnish or server-side caching?

Hi Valentina,
I love your plugin. It really makes a change.
Keep on further.

Wow! is all I can say. I thought I would never break out of the 80s on Page Speed Insights. I now have 98!! Wow! Another website I manage was in the 50s with little hope of improving is very picture heavy. I now have 89 on that one! WOW!!! Thanks!!

is the double click hamburger problem on mobile gone?

I was already using the preload feature. I turned on remove unused CSS and hit the clear and reload button. Holy cow! I didn't need to go to Page Insights to see that page load is a LOT faster. Thanks!

Unfortunately, regardless of all the improvements and all the happy emojis in your email, the price of 49 USD is just to high. Even the 20% off is not enough for us to keep using WP Rocket. That said, we are sure the plugin benefits some, but just not enough for us at that price.

Nice update. Now it'd be really good to have an option to choose if I want to automatically purge additional pages whenever a post is published or updated.

Thanks for the further improvements in speeds and caching. Good work on the pre load. On our largest Woo Commerce site we are seeing an improvement with the Pre Loader that has helped moved the site speed forward.


Why does version 3.12 use more CPU than the previous version?

That sounds good! Preloading seems to cache the pages faster now, great!

Is there any way to include pages translated with Weglot in the preload?

We're using your plugin for the last two years and are very satisfied.

Just got the mail for the WP Rocket v3.12 release but we're unable to see any update notification on our WordPress platform.
Is this released will be rolling on a user/region basis?


Is there any failsafe for this preloading of cache? I only ask as my sites rather large and when I run a cron job to purge the cache 2 levels down it uses about 7gb of storage on the server extra to store the preloaded files.

If the server gets to a critical level will the cache stop?

ps why do you keep deleting this comment?

I’m a longtime user of WP Rocket. It’s the best caching plugin out there.

Being said the new preload feature is NOT an improvement (not yet at least). It’s great for small sites, but if it’s a larger site or an eComm site it’s not ideal anymore. Many sites have to preload hundreds of products, posts, and pages. Since 3.12 preloads everything now and only preloads batchs of 45 urls it’s takes FOREVER to finish. By the time it’s done the cache seems to clear if set to 10-12 hours and the process starts again. And it absolutely sends CPU sky high. Like wildly high.

Pair this with having to run a real cron to effectively run preload. If the cron runs every minute just to preload larger sites faster then the server has massively high CPU. If it’s a cron job every 15-30 minutes then preload will never finish in a timely manner and CPU will still run high for hours on end.

If the data suggests that users clicked the Preload Homepage Links Only option 89% of the time then there may have been a reason for that. I personally had to use that option on most sites to keep server resources under control. That was the only way I could realistically use preload before on many sites. CPU was also considerably lower pre-3.12.

Being said WP Rocket is a great product and the new preload works great on small 5-10 pages sites. It’s just no longer a good service for mid-size to larger websites. I really hope you can bring back the homepage links only option or find a solution for larger websites.

Hope the feedback helps.

Nice update!

The new preload feature sounds good. Unfortunately, it does not explain in more detail how, beyond SEO sitemaps, it ensures that the preload takes all URLs into account.

We default to showing 12 products per page in WooCommerce categories. Lastly, before the update, we had noticed that paginated pages ("/page/2/" etc.) did not end up in the cache completely, but probably only when called manually instead of by the preload. Maybe because they are not included in the Yoast sitemaps.

After the update, at least my stubs via FTP look complete. Are paginated pages now really reliably considered completely in the preload?

And does the Remove Unused CSS feature work for logged in WooCommerce customers (User Cache is not enabled)?

Hi, with an e-commerce website with 40,000 products I can't imagine using as is - would kill the server. At the moment, I preload pages and product-category only. If I add say Posts or Products using the 3.11 Preload instantly takes the server to 100%. Your crawl preload interval plugin has never worked for me, so Exclusion fields in the main plugin sounds ideal!

We use WP Rocket on all of our sites - great product. On some of our sites, this latest WP Rocket version seems to be a backwards step e.g. for a single site (not multisite) using WooCommerce, Imagify, RankMath & WPML i.e. different domains for different languages, i am not sure the preload is working for all the domains (as the GTMetrix scores went down). Should all pages/posts/products etc. be pre-loading? If so, how can I test/confirm this?

In the previous WP Rocket version, we added in all versions of the sitemaps to pre-load.

Related Articles of Inside WP Rocket
Subscribe to Our Newsletter

Stay in the loop with the latest WordPress and web performance updates.
Straight to your inbox every two weeks.

Get a Faster Website
in a Few Clicks

Setup Takes 3 Minutes Flat
Get WP Rocket Now