WP Rocket

Most caching plugins hand you forty checkboxes and wish you luck. WP Rocket ships with page caching, GZIP, browser caching and cache preloading already on, and the settings you do touch are written in plain English.

What it actually does

WP Rocket is a plugin maintained by WP Media. The current release is version 3.20.2, published on 29 July 2026. What follows is based on running it in production rather than on reading the feature list.

The install is unremarkable in the good sense: activate, run the setup flow, and you are looking at a working configuration inside a few minutes. That matters more than it sounds, because the plugins that go wrong usually go wrong at the point where a reasonable default was not chosen for you.

What works well

• Sensible defaults: measurable gains from activation alone, no configuration
• Delay JavaScript execution is the single biggest LCP win on script-heavy sites
• Remove Unused CSS genuinely works, with a per-page exclusion list when it does not
• Clean, fast admin UI that does not fight you

Taken together these are not marginal conveniences. Each one removes a decision, a second plugin, or an hour of work that would otherwise land on you.

Where it falls short

• No free tier, so you cannot trial it on a staging site without buying in
• Overlaps with server-level caching — on NGINX FastCGI setups you must pick a lane
• Deep tuning still needs a second tool for image and font optimisation

None of these are dealbreakers on their own. They are the kind of thing worth knowing before you commit a project to it, rather than discovering three sprints in.

Performance and maintenance

Measured on a standard install with a clean database, the overhead is what you would expect from a product of this scope. As always, the number that matters is the one you measure on your own stack, with your own plugin set and your own hosting.

The right question is rarely “is this plugin fast”. It is “is this plugin fast enough for what it replaces”.

Update cadence has been steady, and the changelog reads like a maintained product rather than a parked one — which, for anything you are putting at the centre of a site, is the single most important signal there is.

The verdict

Best for anyone who wants Core Web Vitals fixed this afternoon rather than researched for a fortnight.

Version 3.20.2 is a solid place to start. If it fits the shape of your project, it will not be the thing that holds you back.