"Do I need a caching plugin or a CDN?" is a question with a slightly annoying answer: they do different jobs, and most sites want both.
The confusion is understandable, because both get sold as "makes your site faster" and the marketing rarely explains which problem each one solves. So let's separate them properly, then get to which plugin.
The short version
Three distinct mechanisms:
| What it does | Fixes | |
|---|---|---|
| Page cache | Stores finished HTML so WordPress doesn't rebuild pages | Slow server response (TTFB) |
| Object cache | Stores database query results in memory | Slow dynamic pages — stores, memberships |
| CDN | Serves static files from servers near the visitor | Distance latency for global audiences |
Most small sites need: page caching (plugin or host-level) plus a free CDN tier. That's it.
Object caching matters when you run WooCommerce, a membership site, or anything heavily dynamic.
Page caching: the big one
WordPress builds every page from scratch on every request — running PHP, querying the database, assembling HTML. For a page that hasn't changed in three months, that's an enormous amount of repeated work.
Page caching stores the finished HTML and serves that instead. The first visitor triggers the build; everyone after gets the stored copy.
What it fixes: slow server response time, which is the ceiling on everything else. If your TTFB is 1.5 seconds, page caching is the single highest-return change available.
Where it happens:
Server-level caching — built into your host's stack (Nginx FastCGI, LiteSpeed Cache, Varnish). Generally the fastest, because the request never reaches PHP at all. If your host offers it, use it.
Plugin-level caching — WP Rocket, W3 Total Cache, WP Super Cache. Works anywhere, marginally slower than server-level, more configurable.
One important note: don't run two page caching layers simultaneously. Server-level caching plus a caching plugin's page cache causes stale content and confusing bugs. If your host caches at server level, disable page caching in your plugin and use it for its other features.
Object caching: for dynamic sites
Page caching stores whole pages. Object caching stores the results of database queries in memory, so repeated queries don't hit the database.
Why that matters: page caching can't help pages that must be unique per visitor. A logged-in member's dashboard, a WooCommerce cart, a personalised account page — these can't be served from a shared cache. Object caching speeds them up by removing repeated database work.
What you need: Redis or Memcached available on your server, plus a plugin to connect WordPress to it (Redis Object Cache is the standard). Most managed WordPress hosts offer this; most cheap shared hosting doesn't.
Who needs it: WooCommerce stores, membership sites, forums, anything with logged-in users or heavy dynamic content.
Who doesn't: a brochure site or a blog where nearly every visitor sees the same pages. Page caching covers you.
CDNs: what they actually do
A Content Delivery Network stores copies of your static files — images, CSS, JavaScript, fonts — on servers around the world, and serves each visitor from the nearest one.
What it fixes: physical distance. If your server is in London and your visitor is in Sydney, every file makes a round trip of roughly 17,000km. A CDN cuts that to a local hop.
Who benefits most: sites with geographically spread audiences. If your visitors are all in one city and your server is in that country, the benefit is modest.
What else you get, which is often underrated: DDoS protection, a free SSL certificate, bot filtering, and reduced load on your origin server.
Cloudflare's free tier covers global CDN, SSL, and basic security for most small sites genuinely well. It's one of the more remarkable free offerings on the web, and for a typical blog or business site it's sufficient without upgrading.
One caution relevant to your AI visibility: Cloudflare and similar offer one-click AI bot blocking, which operates at a layer your robots.txt never sees. It's easy to block retrieval crawlers like OAI-SearchBot without realising, which removes you from AI answers entirely. Check what's enabled. Which bots matter.
Which caching plugin?
Comparing by what fits rather than by feature count.
WP Rocket — paid, and the reason it's popular is that its defaults are sensible. Turn it on and most of what you want is already configured. Includes page caching, lazy loading, minification, database cleanup, and a CDN integration. Best for people who want it to work without learning the subject.
LiteSpeed Cache — free, and outstanding if your host runs LiteSpeed or OpenLiteSpeed servers. That condition does all the work: on LiteSpeed hosting it caches at server level, which is faster than any PHP-based plugin. On non-LiteSpeed hosting it still functions but loses its main advantage. Check what your host runs before choosing it.
W3 Total Cache — free, extremely configurable, and correspondingly easy to misconfigure. Powerful in experienced hands; a source of confusing breakage otherwise.
WP Super Cache — free, from Automattic, simple and reliable. Fewer features, harder to break. A reasonable choice for a straightforward blog.
Your host's own solution — Kinsta, WP Engine, SiteGround and others include caching in their stack. Often the best option, and it means one less plugin. Check before installing anything.
On pricing: I've deliberately not quoted figures. Plugin pricing and CDN tier limits change regularly, and stale numbers on a review post are the fastest way to lose a reader's trust. Check current rates directly.
Is WP Rocket worth paying for?
Depends on which of two situations you're in.
Worth it when: you don't want to learn caching configuration, you're on hosting without a good built-in solution, or you value your time more than the subscription. Its genuine selling point is that the defaults are safe — you get most of the benefit without breaking anything.
Not worth it when: your host runs LiteSpeed (LiteSpeed Cache is free and faster there), your host already includes good caching, or you're comfortable configuring W3 Total Cache and enjoy the control.
The honest summary: WP Rocket sells convenience and safety, not exclusive capability. Free plugins can achieve comparable results with more configuration effort and more risk of misconfiguration. Whether that trade is worth the fee depends on how you value an afternoon.
Settings that break sites
The section most guides skip, and where most caching disasters happen.
Minify and combine CSS/JS. Combining files was standard advice under HTTP/1.1 and is largely obsolete under HTTP/2. It frequently breaks page builders, sliders, and forms. Minification alone is safer than combining.
Defer or delay JavaScript. Real gains, real risk. Sliders, tabs, accordions, popups, and mobile menus depend on their JS running. Enable, then click every interactive element on the site.
Lazy loading applied to everything. Excludes your hero image, or you're deferring exactly what LCP measures.
Caching logged-in users. Serves one user's personalised page to another. Almost never what you want.
Not excluding cart, checkout, and account pages. Caching a WooCommerce cart causes genuinely serious bugs — customers seeing other customers' carts. Most plugins exclude these automatically; verify yours does.
The method that avoids all of this: enable one setting, check the site properly (forms, cart, mobile menu, search), then enable the next. If something breaks you know exactly what caused it.
A sensible default setup
For a typical small business site or blog:
- Server-level caching if your host offers it. Otherwise a caching plugin with page caching on.
- Cloudflare free tier for CDN and SSL — check its AI bot settings.
- WebP conversion via your caching or optimisation plugin.
- Lazy loading below the fold, hero excluded.
- Minification on, combining off.
- Skip object caching unless you're running something dynamic.
That covers the large majority of achievable gain, and none of it is likely to break your site.
Frequently asked questions
Do I need a caching plugin and a CDN?
They solve different problems, and most sites benefit from both. Caching stops WordPress rebuilding pages from scratch on every request, which fixes slow server response time. A CDN serves static files from servers near each visitor, which fixes distance latency. If your audience is geographically concentrated near your server, the CDN benefit is modest — though Cloudflare's free tier also provides SSL and DDoS protection, which is worth having regardless.
Is WP Rocket worth paying for?
It's worth it if you want caching configured safely without learning the subject — its main selling point is sensible defaults rather than exclusive features. It's not worth it if your host runs LiteSpeed servers, where LiteSpeed Cache is free and caches at server level, or if your host already includes good caching. Free plugins achieve comparable results with more configuration effort and more risk of misconfiguration.
Is Cloudflare's free plan enough?
For most small sites, yes. It provides global CDN, a free SSL certificate, basic DDoS protection, and bot filtering, which covers what a typical blog or business site needs. Paid tiers add advanced firewall rules, image optimisation, and more granular caching control. One thing to check: Cloudflare's AI bot blocking operates at a layer your robots.txt doesn't control, and it can block the retrieval crawlers that make you visible in AI answers.
What to do next
Before installing anything, check whether your host already caches at server level. Kinsta, WP Engine, SiteGround, and most LiteSpeed hosts do — and running a second page cache on top causes stale content rather than speed.
Then run PageSpeed Insights and look at your TTFB. Over a second means caching is your highest-return fix. Under 600ms means it's already handled and your time is better spent on images.
Free: The WordPress maintenance checklist.
Related guides
- WordPress speed: the Core Web Vitals playbook — where caching fits in the order
- How to read a PageSpeed Insights report — checking your TTFB
- WordPress plugin audit — what caching can't fix
- llms.txt and AI crawlers — the CDN setting worth checking
Join the Newsletter
Get practical marketing tactics delivered straight to your inbox.
Written by
Muhammad Basim
Related Articles
Transactional Email Services Compared for WordPress
Every one of these services will deliver your password resets. That's not the differentiator. What differs is setup difficulty, what the free tier covers, how good the logs are when something goes wrong, and — the one people never consider until it bites them — whether the service also handles marketing mail, and whether you […]
Contact Form Notifications Not Arriving: Every Cause
Here's the version of this problem that costs the most: it's been happening for months and you don't know. The form says "thank you." The visitor believes they've reached you. You believe nobody's been in touch. There's no error, no bounce, no alert — just an absence, and absences are invisible. Most of the time […]
WooCommerce Order Emails Going to Spam: The Fix
"I never got a confirmation. Did my order go through?" Every store owner gets this message. And when it arrives often enough, you stop treating it as customer confusion and start realising your receipts genuinely aren't landing. This costs more than most email problems, because a missing order confirmation doesn't just annoy someone — it […]