Table of Contents

Is it a coincidence that new versions of WP Rocket always arrive during the change of season? Maybe not, as we like to keep our plugin tidy and always abreast of the times.

So, as fall starts to find its space on this side of the world, we can finally say it: it’s time to update and welcome a new major version of WP Rocket! ?

Version 3.4 comes after a dense summer of enhancements, new features construction and revamping of old ones. What change of season would it be without a rejuvenation of our historical features?

Let’s dive in and discover what exciting improvements WP Rocket is going to bring to your site. ?

WP Rocket 3.4 New Features and Enhancements

WP Rocket 3.4 includes two new features and five enhancements, and most of them are related to image support. We also added a new tab on the plugin’s backend, completely dedicated to our video tutorials. ?

Keep reading to know more!

Separate Cache File for WebP Images

Version 3.4 brings the possibility for WP Rocket to create a separate WebP cache file to serve WebP images.

Our plugin won’t create WebP images, since this is a job for an image optimization plugin like Imagify.

The news here is that we can provide a method to serve WebP files via a dedicated cache file!

Furthermore, WP Rocket is now also automatically compatible with several plugins that  handle WebP conversion.

WP Rocket now can serve cache files for WebP Images

You can find more info about WebP compatibility on our documentation.

Additional Capabilities for User Roles

Until today, only the Administrator(s) of your site(s) were able to manage all WP Rocket settings.

With WP Rocket 3.4, you can start granting to other user roles access to some or all of WP Rocket’s options.

For example, you can now allow other user roles to purge the cache, without giving them access to other settings. ?

Our new documentation explains how to play with this new feature.

Enhancement of Our CDN Rewriting Feature

In the past months, our developers and product team worked very hard for revamping an historic feature of WP Rocket: the CDN rewriting feature.


Previously, our CDN feature detected specific WordPress functions and rewrote the asset (CSS/JS/image) links they loaded.

The downside of this approach was that some files could be missed because they were loaded via custom functions we couldn’t detect. In those cases we often referred customers to use another CDN integrator plugin, i.e. CDN Enabler from KeyCDN.

CDN assets rewriting
CDN assets rewriting


3.4 introduces a different approach for CDN rewriting

Instead of detecting specific functions, we are now parsing the entire HTML of the page and replacing the asset URLs there.

So, starting from now, it won’t matter how an asset (an image, for example) ended up on the page: its URL will be rewritten to point to the CDN.

This way, WP Rocket CDN integration will be able to catch almost every asset, and it won’t be necessary to use a third-party CDN plugin.

A Twist In Our Cache Lifespan Option

Cache Lifespan is one of the very first features we introduced in WP Rocket, so we’re fond of this option! 

But over time, we realized it was time to revamp it a little.


Previously, we deleted the entire cache according to the Cache Lifespan interval, which was set to 10 hours by default.

If this system was pretty straightforward for small to medium sites, large sites could sometimes face issues because of this, since they could find themselves with lots of pages uncached for a while, even with preloading. 

Also, deleting large numbers of files can consume server resources: not an ideal situation.

how much disk space does a wordpress site need
Server resources can be affected by the elimination of large numbers of files

So with WP Rocket 3.4, instead of deleting the whole cache, we’ll only delete those files that are older than the specified interval.

For example: if you set your Cache Lifespan to 5 hours, when the deletion runs, a cache file created 4 hours ago won’t be deleted.

How does it work? We set up a cron job running every hour to check which files to delete. ⏱

This should help large sites to keep their cache longer and reduce CPU consumption related to preloading. 

Newcomers on the Plugin’s Backend: Tutorial Videos

Finally, we also have some news concerning your experience with WP Rocket’s backend.

Our new tutorial videos are now embedded in the dashboard, meaning that you can click on them right away if you need more info on how to get started with WP Rocket!

Tutorial videos embedded in WP Rocket 3.4
Tutorial videos to get started with WP Rocket

You’ll also find the complete list of the videos on the new dedicated Tutorials tab:

Tutorials tab in WP Rocket 3.4
Tutorials tab in WP Rocket’s backend

From the first installation to the best settings, from measuring your website speed to more advanced customization techniques, our video tutorials cover all the fundamentals of WP Rocket, and they are at your fingertips (but also on our YouTube channel and documentation ?).

Compatibility with Chrome Native Lazy-Loading

As you may already know, Chrome 76 introduced native lazy-loading.

This means that lazy-loading can be done by the browser itself instead of a plugin.

As soon as Google announced the news a few months ago, we started thinking about making WP Rocket automatically compatible with Chrome’s lazy-loading.

After several tests and brainstorming, we eventually realized this was not the best choice for our plugin.

At the moment, Chrome’s implementation of native lazy-load is very conservative and sets a very large threshold. WP Rocket’s LazyLoad, on the other hand, has a smaller threshold allowing more images to be lazy-loaded.

This means that our LazyLoad feature is currently more effective in reducing the amount of data transferred on the initial page load (which is the key value of lazy-loading!).

WP Rocket already includes an efficient lazy-loading system
WP Rocket already includes an efficient lazy-loading system

While do not include automatic compatibility with Chrome browsers using native lazy-loading, WP Rocket 3.4 still gives you the possibility to choose support for Chrome’s native lazy-loading through a helper plugin.

You can find more info about why we made this choice on our dedicated blog post on Native lazyloading for WordPress.

New Requirements 

It’s worth noting that we also changed the minimum requirements (PHP and WordPress version) to use this new major versions of WP Rocket.

They are the following:

  • PHP version: 5.6
  • WordPress version: 4.9

Don’t hesitate to update them or to contact your hosting provider, if you don’t feel confident doing that by yourself.

Final Notes

WP Rocket 3.4 includes two new features and several enhancements, along with a few bug fixes. We encourage you to read all the details on our changelog.

We’re sure that you’ll enjoy the possibility to serve a separate WebP cache file for WebP images and to customize access to WP Rocket settings for different user roles! ?

Among the enhancements, we’re particularly proud of the improvements to our CDN rewriting feature and of the twist we gave to our historic Cache Lifespan option. ?

Now it’s your turn! Update WP Rocket, play with it and let us know what you think in the comments below. 🙂

Comments (9)

How about Cloudflare CDN? Can we use this feature with Cloudflare as well? I have Shortpixel + WP Rocket + Cloudflare.

"For example: if you set your Cache Lifespan to 5 hours, when the deletion runs, a cache file created 4 hours ago won’t be deleted."

This would be an issue on the scenario when we do an update which will have a site-wide effect and we need to make it live immediately. There should be an option to delete the entire cache immediately - in addition to the new option.

I clear the cache in this way a lot, so I can tell you that you are going to get tickets a lot about this.

I am curious about CloudFlare as well :)

Any news on fragmented caching? Have you introduced support for multisites? Right now WP Rocket is still needed to be installed individually on each one of the blogs and the only way to clean the entire cache is via cli or ftp. Preloading a huge network site will take any server down for hours, will the new approach solve a situation like that one?

I already have WP Rocket at version, will my version automatically upgrade to the new 3.4?

What is the point of your plugin? It slows WordPress, 4 sec for load any page without cache, and when I disable your plugin every page loads in 1-2 seconds.

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