Blog / friday roundup
Five caching plugins we actually see working
Five WordPress caching plugins that hold up on real shared hosting, when each one fits, and how to avoid caching the same page twice.
We're starting a Friday habit on this blog: short lists of tools we actually see working on customer accounts, with no trends and no fluff. First up, caching plugins, because nothing else moves a slow WordPress site as far for as little effort. We wrote last week about why speed matters for search; this is the practical follow-up.
A quick note on how we judge these. We don't read feature pages. We watch what happens on our servers: CPU seconds per request, how often the cache actually gets hit, and how many support tickets a plugin generates. These five earn their keep.
LiteSpeed Cache
Where the server runs LiteSpeed, this is the one we recommend without hesitation, and our shared hosting runs LiteSpeed for exactly this reason. It talks to the web server directly, so cached pages are served before PHP even wakes up. On busy sites we see CPU usage drop by half or more after it's set up properly. The catch: it only does its best work on a LiteSpeed server, so check what you're running before you install it.
WP Super Cache
The old reliable. It writes plain HTML files to disk and serves those, which is about as simple as caching gets. It has fewer options than the others on this list, and honestly that's a feature: there's very little to misconfigure. For a small brochure site or a blog that publishes weekly, it's hard to beat. We rarely see a support ticket caused by it.
W3 Total Cache
The powerful one, and the one we see misconfigured most often. It can cache pages, database queries, and objects, and it can hook into external services. In careful hands on a complex site it does great work. In a hurry, people turn everything on, and we then spend an afternoon working out why logged-in users see each other's content. Our advice: enable page caching only, confirm the site behaves, then add one feature at a time.
WP Fastest Cache
A sensible middle ground. Setup is a single settings page, the defaults are sane, and it handles the common cases (mobile, logged-in users, cache clearing on publish) without drama. We see it a lot on small-business sites where nobody wants to think about caching again, and mostly nobody has to.
Cache Enabler
The minimalist. Lightweight, quick to configure, and it generates static HTML with very little overhead of its own. We like it on lean sites with lean themes, where the goal is to keep the whole stack small. It doesn't try to minify, combine, or optimize everything else, and if you want that, pair it with a separate tool rather than reaching for a bigger plugin.
The double-caching trap
The most common caching problem we untangle isn't a slow cache. It's two caches. Someone installs a second caching plugin "to be safe," or runs a caching plugin on top of server-level caching that's already doing the same job. The symptoms are maddening: edits that don't show up, one visitor seeing yesterday's page, contact forms that fail for some people and not others.
One page cache. That's the rule. Pick one plugin from this list, confirm what your host already does at the server level, and disable whichever layer is redundant. If you're on our servers and not sure what's already handling caching for your account, ask us before you install anything.
Winter is a good time to sort this out, before the spring rush hits whatever your busy season is. If you'd like a second pair of eyes on your caching setup, open a ticket with support and tell us which plugin you're running; checking for a doubled-up cache takes us a few minutes.