The WordPress caching plugin debate never ends. “LiteSpeed is the best”, “Everyone uses WP Rocket”, “W3 Total Cache is the classic”. I’ve run all three on different sites. Here’s where each one earns its place.
LiteSpeed Cache
What this site runs. A first-class citizen on sites served by LiteSpeed Web Server or OpenLiteSpeed. Free, and it caches at the web server layer, meaning PHP never has to run.
Upsides:
– Server-layer cache, PHP stays cold. TTFB drops to 30 to 50ms.
– QUIC.cloud CDN integration with a free tier.
– Built-in image optimisation (WebP conversion, lazy loading).
– Automatic critical CSS generation.
– Database tidy-up (revisions, transients).
– Object cache support.
Downsides:
– Only pays off in full on a LiteSpeed/OpenLiteSpeed server. On Apache or Nginx you get plugin-level caching only, without the server advantage.
– The settings screen is intimidating, it can overwhelm newcomers.
– On QUIC.cloud CDN, service is throttled when you blow through your quota.
– Documentation is uneven, some features take trial and error.
On Hostinger, LiteSpeed is pre-installed, which makes this plugin the sensible default. On non-Hostinger hosting, check whether the server is actually LiteSpeed first.
WP Rocket
Paid ($50/year and up). The most polished UI. Sensible defaults, install-and-go.
Upsides:
– Setup is trivial, zero-config by design.
– Safe defaults, “it won’t break your site”.
– Lazy load, bundle splitting, preload, all automatic.
– Database cleanup, heartbeat control.
– Plays well with e-commerce and membership plugins.
– Support is responsive.
– Frequent updates.
Downsides:
– The license cost.
– No server-level cache. PHP always runs, even on a cache hit there’s warmup time.
– CDN isn’t integrated, you set it up separately (it does integrate with CloudFlare and BunnyCDN).
– Limited knob count. Not enough for advanced tuning.
On client sites, WP Rocket is popular. Agencies without strong technical chops can use it safely. With just the defaults, we’ve gotten 90% of the benefit.
W3 Total Cache
The old guard, around for 10+ years. Free, with a paid Pro. The configuration is labyrinthine.
Upsides:
– Very granular control. A separate set of settings for each cache type.
– Supports Memcached, Redis, APC, Disk, Opcode.
– Detailed fragment and object caching.
– Wide CDN integration list.
– Enterprise features in Pro.
Downsides:
– The UI is a disaster. It looks like it shipped in 2008.
– Misconfiguring is easy, and it can break the site.
– Default settings aren’t great.
– Support is limited.
– I’ve hit hosting compatibility issues with it.
I don’t install W3 Total Cache on a new site unless there’s a specific reason. If an old site already has it and there’s vendor lock-in, you can keep going with it.
Performance comparison
I tested all three on a comparable WooCommerce site (on LiteSpeed Web Server):
| Metric | No cache | W3 Total Cache | WP Rocket | LiteSpeed |
| — | — | — | — | — |
| TTFB | 800ms | 180ms | 150ms | 45ms |
| LCP | 3.2s | 2.1s | 1.9s | 1.4s |
| PHP execution | 700ms | 80ms | 60ms | 0ms |
LiteSpeed’s server-layer cache advantage is obvious.
Same test on an Apache server:
| Metric | No cache | W3 Total Cache | WP Rocket | LiteSpeed |
| — | — | — | — | — |
| TTFB | 850ms | 200ms | 170ms | 210ms |
| LCP | 3.3s | 2.2s | 2.0s | 2.4s |
On Apache, LiteSpeed loses its plugin advantage and WP Rocket edges ahead.
E-commerce specifics
WooCommerce cart, checkout, and account pages shouldn’t be cached. All three plugins know how to exclude these, but verify for yourself. /cart, /checkout, /my-account have to stay out of the cache.
Also, logged-in user caching. By default, logged-in users aren’t cached. On membership sites this is a real performance hit. Use role-based cache variation (LiteSpeed Cookie Vary, WP Rocket fine-tuning).
CDN pairing
Whichever plugin you pick, a CDN is non-negotiable. CloudFlare free tier is enough for simple sites. BunnyCDN is fast and cheap for image delivery. QUIC.cloud is native to LiteSpeed users.
Decision matrix
- LiteSpeed/OpenLiteSpeed server: LiteSpeed Cache, no contest.
- Apache/Nginx + budget: WP Rocket.
- Apache/Nginx + tight budget: LiteSpeed Cache (plugin mode) or W3 Total Cache.
- Very granular control needed: W3 Total Cache.
- Membership site, heavy logged-in traffic: LiteSpeed or WP Rocket.
- Mixed e-commerce: WP Rocket for the safest defaults.
What this site does
This theme runs with LiteSpeed Cache. ac_enqueue_assets() does simple cache busting on asset versions via AC_THEME_VERSION. After a theme change, both wp litespeed-purge all and wp cache flush get run. That’s my standard dev loop.