Search the plugin directory for “cache” and you get pages of results, each claiming to be the fastest. Comparison articles disagree. A friend swears by one, a forum thread says it broke their site. And your host’s welcome email may have mentioned caching, which raises the question of whether you need a plugin at all.
How to choose a WordPress caching plugin is less about rankings than about your own setup. The single biggest factor is not the plugin. It is the server your site runs on and what your host already does. Get those two answers first and the choice usually narrows to one or two sensible options.
Step one: find out what server you are on
WordPress runs on top of web server software, and the common ones are Apache, Nginx and LiteSpeed (or its open-source sibling, OpenLiteSpeed). Caching plugins work differently on each, and one of the best-known plugins only provides its page cache on one of them.
Ways to find out:
- Your host’s plan page or documentation. Hosts that use LiteSpeed usually say so prominently, because it is a selling point.
- The response headers. Open your site in Chrome, open DevTools, go to the Network tab, reload, click the first request and look for a header named server. It may say Apache, nginx or LiteSpeed.
- Site Health. In WordPress, Tools, Site Health, Info, the Server section often shows the web server software.
- Ask the host. “Which web server runs my site, and do you provide server-level page caching?” gets both answers at once.
One catch: if your site is behind Cloudflare, the server header will usually say cloudflare. That tells you about the CDN, not the hosting. Use one of the other methods.
Step two: check what your host already caches
Many hosts now run a page cache at server level, in front of WordPress. Managed WordPress hosts almost always do. Some give you their own plugin, which mainly adds a purge button and connects the host’s cache to WordPress so it clears when you publish.
This changes the question. If the host already caches pages:
- You may not need a separate page caching plugin at all.
- Some managed hosts do not allow certain caching plugins, because two page caches interfere with each other. Check the host’s list of disallowed or discouraged plugins before installing one.
- If you want a plugin for its other features, such as delaying scripts, you may need to switch its page caching off and keep the rest.
A host cache, a plugin cache and a CDN are different layers doing different jobs, and our plain guide to website caching shows where each one sits.
The relationship between hosting and speed goes well beyond caching, and our post on how much hosting affects website speed covers what the server controls and what it does not.
Matching the plugin to the server
With those two answers, the starting point usually looks like this:
| Your setup | Sensible starting point |
|---|---|
| LiteSpeed or OpenLiteSpeed server | LiteSpeed Cache. Its page cache is provided by the LiteSpeed server itself, which is why it does not cache pages on Apache or Nginx. |
| Managed host with its own server cache | The host’s plugin or none, plus an optimisation plugin only if you need features the host lacks. |
| Apache or Nginx shared hosting with no server cache | A file-based page caching plugin such as WP Rocket, WP Super Cache, W3 Total Cache or Cache Enabler. |
| VPS or cloud server you or a developer manage | Often a server-level cache (Nginx FastCGI cache, Varnish, or LiteSpeed if installed) with a small plugin to handle purging. |
This is a starting point, not a verdict. All of the plugins named are widely used. The differences between them matter less than whether the one you choose suits your server and is set up carefully. If you land on LiteSpeed Cache, our post on safe LiteSpeed Cache settings to start with walks through the setup in stages.
How to choose a WordPress caching plugin: features that matter
Ask around for the best caching plugin for your site and you mostly get feature lists. Most lists are padded. These are the features that decide whether caching works well day to day:
Page caching that knows what to skip
It must automatically bypass logged-in users, WooCommerce cart, checkout and account pages, and visitors carrying cart cookies. It should let you add your own exclusions by address and by cookie. For what has to be skipped and why, see our guide to how a WordPress page cache works.
Sensible purging
When you update a post, it should clear that page plus related pages such as the home page, archives and feeds. It should have a clear “purge all” option and, if you use a CDN or host cache, a way to clear those too.
Handling of tracking parameters
Visitors from ads and email campaigns arrive with addresses carrying utm or click-ID parameters. A plugin that treats each as a separate page gives those visitors a cache miss. Look for a setting that ignores known tracking parameters.
Preloading, if your site is quiet
On a site with modest traffic, cached pages can expire before anyone visits. A preload feature rebuilds them in the background. It is useful on small and medium sites and needs care on very large ones.
Browser caching rules
On Apache and LiteSpeed, many plugins can write browser caching rules into .htaccess. Useful, but only if your host has not already set them.
Optimisation features you can leave off
Most caching plugins now include minify, combine, unused CSS removal, delayed JavaScript and lazy loading. These are separate from caching and are what most often breaks layouts and menus. A good plugin lets you switch each one on individually. You want caching working first, with optimisation added later, one feature at a time.
A clean way out
Check that deactivating the plugin removes its rules from .htaccess and its files from wp-content. Good plugins tidy up after themselves. If you ever need to switch, leftovers from the old plugin are a common source of trouble.
Maintenance and support
Look at when the plugin was last updated, whether it lists your WordPress version as tested, and whether its documentation explains the settings clearly. Paid plugins usually include direct support. Free ones rely on forums and documentation.
Why you should only run one
“Only one caching plugin” is advice everyone repeats. To be precise, it means only one page cache and only one tool doing each optimisation job.
Two page caches each store their own copy of every page and purge at different times, so you get pages appearing and disappearing, and edits that show for some visitors and not others. Two plugins both minifying CSS can process the same file twice. Two plugins both delaying JavaScript can break each other’s rules.
Separate jobs are fine together. An image optimisation plugin alongside a caching plugin is normal, as long as only one of them is converting images to WebP and only one is lazy loading. An object cache plugin for Redis alongside a page caching plugin is normal too.
When switching from one caching plugin to another, deactivate and delete the old one first, check that wp-content no longer contains its advanced-cache.php file, and check .htaccess for leftover rules. Then install the new one.
Testing your choice
- Before installing, run three speed tests on the home page and on a typical inner page, logged out. Note server response time and the overall load time, not just the score. Our website speed test tool is one way to get a baseline.
- Install the plugin and turn on page caching only. Leave every optimisation feature off.
- Open every page you measured a couple of times while logged out, giving the cache a chance to store it, and then measure again.
- Test the things that must not be cached: log in and out, add to cart, view the cart in another browser, submit a form.
- Only then try optimisation features, one at a time, testing the layout, menus and forms after each.
If the numbers barely change after step 3, check whether the pages are actually being served from cache before blaming the plugin.
Common mistakes when choosing
- Installing LiteSpeed Cache on a non-LiteSpeed server and expecting page caching from it.
- Adding a caching plugin on a managed host that already caches, without checking whether the host allows it.
- Turning on every option in the first session, then not knowing which one broke the menu.
- Choosing by PageSpeed score screenshots in reviews, which were run on someone else’s site.
- Keeping an old caching plugin “deactivated but installed”, with its rules still in .htaccess.
Caching is usually the first big step for a WordPress site, but it is one step. Our guide to making a website faster sets it beside images, scripts and hosting so you can see what comes next.
Frequently asked questions
Is a paid caching plugin faster than a free one?
Not automatically. Free plugins such as LiteSpeed Cache on a LiteSpeed server, or WP Super Cache on Apache, can serve cached pages just as quickly. Paid plugins tend to offer easier setup, more optimisation features and direct support. Whether that is worth paying for depends on how much time you want to spend configuring.
Do I need a caching plugin if my host already caches pages?
Often not for page caching. A host cache in front of WordPress already stores pages, and adding a plugin cache on top can cause conflicts. You may still want the host’s own plugin for purging, or an optimisation plugin with its page cache switched off, if you need features the host does not provide.
Does Cloudflare change which caching plugin I should use?
Usually not. With default settings Cloudflare stores static files such as images and scripts, while your pages still come from the server, so you still need a page cache there. What changes is purging: choose a plugin that can clear Cloudflare, or add the official Cloudflare plugin, so that updating a post also clears anything stored there.
Will a caching plugin work with WooCommerce?
The well-known caching plugins exclude the standard WooCommerce cart, checkout and account pages by default. Problems usually come from extra plugins such as currency switchers, location-based pricing or custom account pages. Test a full order logged out and logged in after setting it up, and add exclusions where needed.
Trying caching options on a live shop or a busy enquiry site is stressful. Caching plugin setup and configuration is one of the items in our speed optimisation service, and you see the before-and-after comparison for your own pages.
Next in this series: LiteSpeed Cache Settings: A Safe, Staged Setup
