Caching is the highest-leverage performance fix in WordPress, and the plugin market is crowded with claims. So we tested six cache plugins the way we test everything in our benchmark methodology: identical staging servers, realistic content, uncached and cached passes — plus one test vendors never run: what happens to pages whose content varies by logged-in role, which is exactly the setup of our B2B client base.
The numbers
Baseline uncached LCP on our demo set: 1.61s. Cached results:
| Plugin | Cached LCP | TTFB (cached) | Role-content test | Breakage notes |
|---|---|---|---|---|
| LiteSpeed Cache | 0.58s | 88ms | Handled via ESI | Needs LiteSpeed server; ESI config fiddly |
| WP Rocket | 0.61s | 94ms | Handled (dynamic exclusions) | None in standard setups |
| Cache Enabler | 0.64s | 101ms | Handled (per-group cache) | Minimal options; CDN config manual |
| W3 Total Cache | 0.66s | 109ms | Partial — needed exclusions | Options overload; two settings conflicts found |
| WP Fastest Cache | 0.69s | 113ms | Partial | Minification broke one page’s slider |
| Breeze | 0.71s | 118ms | Failed — stale role content served | Simple; good for basic brochure sites |
The test that separates real plugins from toys
Role-varied content breaks naive caching: the first user’s version of a page gets served to everyone. On a retail site that means an admin bar leaking to customers; on our B2B stores it means wholesale prices leaking to guests — the scenario documented in our pricing-plugin comparison. Three plugins handled it correctly out of the box. Two needed manual exclusions. One served stale role content until we excluded the pages entirely.
Per-plugin notes
- LiteSpeed Cache — the fastest number in the table, but only if your server runs LiteSpeed. On nginx it degrades to page-cache-only duty. Its ESI (edge-side includes) is the correct architecture for role-varied fragments; configuration took us an afternoon.
- WP Rocket — premium, and the closest to “configure and forget.” Its exclusion UI saved us on two client sites with membership content. Paid, ~$59/yr, no free tier.
- Cache Enabler — our default on this very site: free, lean, per-group caching for roles, and honest about what it does not do (no minification fanciness). Pairs well with a separate optimizer if needed.
- W3 Total Cache — the most options in the group, which is also the problem. Two of its defaults conflicted with object caching in our tests. Powerful if you enjoy knobs; risky if you do not.
- WP Fastest Cache / Breeze — fine for simple sites. Breeze’s stale-role behavior rules it out for anything with member or wholesale content.
Server-level caching beats all of them
Worth saying: nginx FastCGI cache or hosting-level caching outperforms every PHP-layer plugin — our nginx tests hit 0.52s TTFB without any plugin. Plugins matter most on shared hosting where you cannot touch server config. The full hierarchy is explained in the WordPress caching guide.
What we don’t like
We test and recommend these plugins for a living, and three things still annoy us. LiteSpeed Cache is only fully functional on LiteSpeed servers — on the Nginx and Apache stacks most shared hosts run, its page-cache layer silently does nothing and you are configuring settings that never apply. WP Rocket has no free version at all, so it is the wrong first purchase for a hobby site that has not yet earned revenue. And the free options (Cache Enabler, W3 Total Cache) give you no object-cache UI: getting Redis working means editing wp-config.php by hand and debugging with wp cache type over SSH — exactly the work beginners hire us to do. None of these are dealbreakers; all of them are the reason our picks differ by hosting type instead of one universal winner.
Recommendations
- LiteSpeed hosting: LiteSpeed Cache, invest the afternoon in ESI.
- Shared hosting, mixed content: WP Rocket or Cache Enabler.
- Simple site, no roles: Cache Enabler free is genuinely enough.
If your current setup’s numbers are unknown, the free audit measures them — caching config errors are among the top findings we see. And remember caching is step two; a heavy theme is step one — see the theme diagnostic.
On our tests, LiteSpeed Cache (on a LiteSpeed server) posted the best cached numbers — 0.58s LCP, 88ms TTFB. On nginx, WP Rocket and Cache Enabler were within 0.06s of each other. Role-based prices create role-varied pages. A naive cache stores the first visitor's version for everyone. The cache must vary by role, use ESI fragments, or exclude those pages. WP Rocket's exclusion handling and defaults saved configuration time on client sites with member content. On simple sites, free Cache Enabler measures within 0.03s — pay only for complexity you have. Generally no — pick one page-cache layer. Double caching causes stale-content bugs that are miserable to diagnose. Server-level cache alone beats plugin+server combos. Cached visits improve dramatically, but uncached crawlers still see the heavy page. Fix theme weight first (the diagnostic guide), then cache — they compound.What is the fastest WordPress cache plugin?
Why do wholesale prices leak through cache plugins?
Is a paid cache plugin worth it?
Should I use a cache plugin and server caching together?
Does caching fix a slow WordPress site by itself?
