Your caching plugin is hiding the problem, not solving it

Install a caching plugin, watch your PageSpeed score jump, job done — it's the most common speed "fix" in WordPress, and it's built on a misunderstanding of what caching does.

A cache stores the finished page so it can be served again without rebuilding it. That's genuinely useful. But notice what it doesn't do: it doesn't make the page build any faster. It makes the second delivery fast. The first visitor after every cache clear — and every visitor the cache misses — still gets the slow version.

Who the cache doesn't help

• First visitors after every update, post edit or cache expiry — often the person who just clicked your ad.
• Logged-in users and shoppers. Carts, checkouts and account pages are personal, so they usually bypass the page cache entirely. On a WooCommerce store, the pages that make money are the pages caching can't touch.
• Googlebot, which crawls deep, cold URLs — and measures what it finds.

What's usually actually slow

When we profile a slow WordPress site, the same four causes come up in various mixtures:

• Oversized images — a 4,000-pixel photo scaled down in the browser instead of resized on the server.
• Render-blocking CSS and JavaScript loading before the browser is allowed to paint anything.
• Slow database queries — a plugin doing far more work per page than the page needs.
• Plugin bloat — scripts for a booking form loading on all 400 pages that don't have one.

None of these are fixed by caching. They're papered over — for some visitors, some of the time.

Caching a slow page makes it fast for the second visitor. Fixing the page makes it fast for everyone.

The right order

• Measure first. A mobile PageSpeed baseline on a cold cache, so improvement is provable.
• Fix the causes. Images converted and sized properly, blocking assets deferred, unneeded scripts dequeued, the slow query found and rewritten.
• Then cache. Now it's caching a fast page — the cache becomes a bonus instead of a bandage.
• Re-measure under the same conditions, and keep re-measuring monthly, because new plugins and images quietly add the weight back.

That last point is why speed work belongs inside ongoing maintenance rather than being a one-time event: sites don't stay fast by themselves any more than they stay secure by themselves.