Caching is the single biggest speed improvement most WordPress sites can make. Without it, every visit makes PHP rebuild the page and run dozens of database queries. With page caching, most visitors get a ready-made HTML file in milliseconds. But “caching plugin” covers very different tools, and the best one depends more on your hosting than on feature lists.
Quick answer
- Your host already caches? (many managed hosts do) Use their cache or their recommended plugin, not a second one.
- LiteSpeed server (common on shared hosting): LiteSpeed Cache uses the server’s own cache and is usually the best fit.
- Apache or Nginx without host caching: a PHP page-cache plugin such as WP Super Cache, W3 Total Cache or WP Fastest Cache.
- Use one page-cache plugin only. Two caching plugins fight each other.
The most popular caching plugins right now
This table is generated from our directory and refreshes automatically from WordPress.org, so the numbers are current whenever you read this. Click any plugin for a setup guide and its full hooks reference.
| # | Plugin | Active installs | Rating | Last updated | Tested up to | Hooks |
|---|---|---|---|---|---|---|
| 1 | 7+ million | 4.8 | 2 weeks ago | 7.1.4 | 178 | |
| 2 | 1+ million | 4.3 | 2 weeks ago | 7.1.4 | 42 | |
| 3 | 1+ million | 4.9 | 2 weeks ago | 7.1.4 | 22 | |
| 4 | 1+ million | 4.8 | 17 hours ago | 7.2 | 201 | |
| 5 | 1+ million | 4.2 | 2 weeks ago | 7.1.4 | 40 | |
| 6 | 900,000+ | 4.4 | 4 weeks ago | 7.1.4 | 246 | |
| 7 | 500,000+ | 4.5 | 3 days ago | 7.1.4 | 20 | |
| 8 | 500,000+ | 4.4 | 1 month ago | 7.1.4 | 17 | |
| 9 | 300,000+ | 3.6 | 2 days ago | 7.1.4 | 104 | |
| 10 | 300,000+ | 4.7 | 2 weeks ago | 7.1.4 | 123 |
Live data from WordPress.org, last checked Nov 18, 2026. Sorted by active installs. Click a plugin for its setup guide and hooks.
What the different kinds of caching do
Page caching
Saves the finished HTML of each page and serves that copy to the next visitors instead of running WordPress again. This is what makes the big difference to server response time (TTFB). Logged-in users, carts and checkout pages are normally excluded, because they’re different for every visitor.
Server-level caching
The same idea, done by the web server (LiteSpeed, Nginx FastCGI cache, Varnish) before PHP is even involved. It’s faster than a PHP-based cache. The plugin’s job is then mainly to tell the server when to clear pages, for example after you update a post. LiteSpeed Cache’s page caching only works on servers running LiteSpeed or OpenLiteSpeed.
Object caching
Keeps the results of database queries in memory (Redis or Memcached) so repeated queries are skipped. It matters most for things page caching can’t help with: WooCommerce carts, membership sites, the admin area. It needs Redis or Memcached on the server; ask your host.
Browser caching and asset optimization
Tells browsers to keep CSS, JavaScript and images so returning visitors don’t download them again, and often bundles extras: minifying files, delaying JavaScript, lazy-loading images, generating “critical CSS”. These help, but they are also where most caching-related breakage comes from. Turn them on one at a time and check your site after each.
How to choose
- Find out what your host provides. Managed WordPress hosts usually run their own page cache and may block or discourage caching plugins. Check their docs before installing anything.
- Match the plugin to the web server. On LiteSpeed, use LiteSpeed Cache. On Apache or Nginx without host caching, use a PHP-based page cache.
- Prefer simple if you’re not technical. WP Super Cache (by Automattic) and WP Fastest Cache work well with default settings. W3 Total Cache has the most options, including object, database and CDN settings, and needs more care to configure.
- Consider premium if you want everything in one place. WP Rocket is a paid plugin that bundles page caching with most front-end optimizations and sensible defaults.
- Check maintenance. Use the “last updated” and “tested up to” columns above; a caching plugin touches every request, so it must keep up with WordPress.
Mistakes that make sites slower or broken
- Two page caches at once (a plugin plus host cache, or two plugins): stale pages, purge problems, sometimes blank pages.
- Combining every CSS and JS file into one: rarely worth it on modern HTTP/2 hosting and a common cause of broken layouts and scripts. Try minify without combine.
- Caching pages that must be dynamic: carts, checkout, account pages and anything showing per-user content must be excluded.
- Not clearing the cache after changes: if an edit doesn’t show up, purge the cache before debugging anything else.
- Expecting caching to fix a heavy site: a bloated theme or 40 plugins loading assets everywhere stays heavy for the first, uncached visit and for logged-in users. See our plugin checklist.
How to test the result
Test in a private browser window (logged-in users usually bypass the cache). Load the page twice, then run PageSpeed Insights and compare the server response time before and after. Many caching plugins add a response header or an HTML comment that shows whether the page came from the cache; check your page source or the browser’s Network tab.
FAQ
Do I need a caching plugin if I use a CDN like Cloudflare?
Usually yes. By default Cloudflare caches static files (images, CSS, JS) but not your HTML pages, so WordPress still builds each page. A page cache on the server, or a configured HTML edge cache, covers that part.
Will caching break my WooCommerce store?
Not if cart, checkout and account pages are excluded. The major caching plugins detect WooCommerce and exclude these automatically, but verify it in the plugin’s settings after setup and test a full order.
Can a caching plugin be customized?
Yes. Most expose hooks to exclude URLs, clear the cache from your own code or change optimization rules. Open any plugin in the table above and choose Hooks to see what’s available, or ask us to set it up for you.
Leave a Reply