TL;DR: Your web server picks your caching plugin, then budget and setup effort narrow it. LiteSpeed and OpenLiteSpeed hosts get LiteSpeed Cache free. Apache and Nginx sites pay for WP Rocket or FlyingPress, which cache on your own server. If you’d rather hand it all off, NitroPack is the pick on any host: it caches the optimized page off the origin. Whichever you choose, run one page cache, never two.
You need one caching plugin for your WordPress site, and the right one depends on something you may never have checked: which web server your host runs. LiteSpeed, Nginx, and Apache each cache differently, so a plugin that flies on one can do very little on another—and on a managed host it can duplicate caching that’s already switched on.
Start there. Your hosting dashboard or a quick support chat will tell you in under a minute, and once you know, the shortlist drops to two or three names.
After that, the pick comes down to price and how much configuring you’ll actually do. The Core Web Vitals numbers that settle it are field data from real Chrome visits, not lab screenshots.
Test NitroPack yourself
By submitting, you agree to the WP Engine Terms of Service and acknowledge the Privacy Policy.
Which caching plugins are best for WordPress?
The best caching plugin for a WordPress site is decided by its web server first, and by budget and setup effort second. Every option you’ll shortlist is one of three kinds of cache:
- A server-level cache (run by LiteSpeed Cache), which needs a host running LiteSpeed or OpenLiteSpeed. The web server stores the finished page and serves it before PHP runs.
- An origin plugin for Apache and Nginx hosts. The plugin builds cached pages on your own server and, by default, serves them from there too, so its speed depends on that server.
- A cloud service that builds optimized pages off your server and serves them from a CDN, with nothing left to configure on your server.
Whichever kind you pick, run one page cache. Two full page caches on one site fight over which copy to serve, and what you get is stale pages and broken cart or login states.
The table compares the five names you’ll actually be choosing between, looking at what each handles, where it runs, and what it costs. Prices are per site.
| Option | What it handles | Server fit | Price | Effort | Best for |
|---|---|---|---|---|---|
| NitroPack ⭐ | Cloud page cache, CDN, image and code optimization | Any WordPress or WooCommerce host | Free (1,000 pageviews/mo); Starter from $7/mo billed annually | Low—connect and go | Hands-off speed on any host |
| LiteSpeed Cache | Server-level page cache, plus optimization tools | LiteSpeed or OpenLiteSpeed only | Free | Low on LiteSpeed presets; high if you tune it | LiteSpeed and OpenLiteSpeed hosts |
| WP Rocket | Origin page cache with minify, lazy load, delay JS | Apache, Nginx, most managed hosts | $59.95/yr | Low | Apache/Nginx sites that want cache on at activation |
| FlyingPress | Origin page cache with unused-CSS removal and LCP preload | Apache, Nginx | $59/yr | Medium | Apache/Nginx sites tuning Core Web Vitals by hand |
| W3 Total Cache | Page, object, database, and browser cache | Any, including VPS | Free; Pro $99/yr | High | Developers setting every layer manually |
Server-level cache if your host runs LiteSpeed
If your host runs LiteSpeed or OpenLiteSpeed, LiteSpeed Cache is free and hands page caching to the web server itself; on any other server its cache features switch off and only the optimization tools remain.
Origin plugins for Apache and Nginx
On Apache or Nginx, the choice is between three origin plugins, and all three build the cache on your own server. WP Rocket ($59.95/year) switches page caching on at activation and FlyingPress ($59/year) is built around Core Web Vitals work such as unused-CSS removal and LCP preload, but both store the cache on your own server. W3 Total Cache (free, Pro $99/year) exposes page, object, and database caching for developers who want to set each layer by hand.
Cloud service off the origin
NitroPack is a speed-optimization service and the best option for hands-off speed on any WordPress host. It caches the optimized page on its own infrastructure and serves it from a CDN, so there is no plugin cache to tune, and it takes over page caching from LiteSpeed Cache or WP Rocket.
Is LiteSpeed Cache free on every host?
LiteSpeed Cache is free and caches at the server level only when your host already runs LiteSpeed or OpenLiteSpeed, because the server itself does the page caching and the plugin only tells it what to store and when to purge. That one condition decides everything, so check it before you install anything.
- Your host runs LiteSpeed or OpenLiteSpeed. Install the plugin, keep the default preset, and page caching is on at zero cost. Hostinger runs LiteSpeed across its shared and WordPress plans, and plenty of cPanel hosts do too.
- Your host runs Nginx or Apache. The plugin still installs, but LiteSpeed’s own docs are clear that the caching features switch off. You keep minification, lazy loading, image optimization, and database cleanup, and lose the page cache. The only way to get the page cache back is to route your traffic through LiteSpeed’s QUIC.cloud CDN, a separate service that’s free only up to a usage cap. This means that on Nginx-based managed hosting such as Kinsta or WP Engine, LiteSpeed Cache is no longer the free option, and front-end work goes to NitroPack, or the NitroPack Add-On on WP Engine, instead.
This leaves Apache and Nginx sites choosing an origin plugin.
What should Apache and Nginx sites use instead?
Apache and Nginx sites get their page cache from an origin plugin, and two common paid picks are WP Rocket and FlyingPress—both of which build and store the cache on your own server.
- If your Apache or Nginx site needs page caching from activation, WP Rocket ($59.95/year) does that without a trip through the settings, and bundles database cleanup, lazy loading, and delayed JavaScript. Image optimization is a separate purchase, and the bundled RocketCDN covers only three pages before it becomes one too.
- If you’d rather tune Core Web Vitals by hand, FlyingPress ($59/year, 14-day trial) gives you the controls: unused-CSS removal, priority loading for above-the-fold images, real-user LCP and INP tracking, and now its own image optimization, with the page cache served from your own server by default.
Is either worth the money compared to a free plugin? On Apache or Nginx, yes, if the alternative is configuring a free plugin by hand—you’re paying for defaults that are already right, plus support. On a LiteSpeed host, LiteSpeed Cache gets you the same outcome for free. If you’d rather not add image optimization and a CDN on top, NitroPack includes both on every plan, starting with a Free plan that needs no credit card.
⚠️ Important: By default, both plugins serve cached pages from your own server, so each page arrives only as fast as that server responds.
Which caching plugins pass Core Web Vitals?
The caching plugins that pass Core Web Vitals are the ones whose sites pass in real Chrome visits, and HTTP Archive counts exactly that for every tool it can detect. A site passes when three-quarters of its visits over 28 days hit LCP within 2.5 seconds, INP under 200 milliseconds, and CLS under 0.1—Google’s thresholds. A PageSpeed score on a staging site measures one simulated load and tells you none of that.
The table is the HTTP Archive Tech Report for August 2026 (mobile) comparing caching tools. “Sites measured” is how many sites each figure is based on, which matters as much as the percentage: a 0.1-point gap between a 4,585-site sample and an 11,320-site sample is a tie.
| Caching tool | Sites passing Core Web Vitals | Sites measured |
|---|---|---|
| FlyingPress | 56.6% | 4,585 |
| NitroPack ⭐ | 56.5% | 11,320 |
| WP Fastest Cache | 55.8% | 41,670 |
| WP Rocket | 51.3% | 272,660 |
| LiteSpeed Cache | 50.7% | 391,972 |
| W3 Total Cache | 44.5% | 81,968 |
Among the caching tools compared here, NitroPack and FlyingPress are level at the top of HTTP Archive’s August 2026 field data, at 56.5% and 56.6%, with NitroPack’s figure drawn from two and a half times as many sites. WP Fastest Cache is under a point behind, sites on WP Rocket and LiteSpeed Cache pass at roughly half, and W3 Total Cache trails at 44.5%.
These percentages describe whole sites, not the tool on its own. Every site in the table also has a host, a theme, and a plugin stack, and all of those count toward whether it passes, so treat the caching tool as one factor in the result rather than the cause. There’s also one thing the table can’t tell you: whether your host already caches your pages.
Forecast your own Core Web Vitals with NitroPack’s free speed test—no account needed →
Does host caching already replace a plugin?
Managed hosts usually cache your pages for logged-out visitors, so a second page-cache plugin repeats that work and can conflict. What they often leave to you is the front-end work: image compression, critical CSS, JavaScript deferral, and minification.
WP Engine is the clearest example. It runs six caching layers—page, CDN, edge full-page, object, the NitroPack Add-On, and the browser—and removes some caching plugins automatically because they clash with the first four. Of those six, only the NitroPack Add-On compresses images or defers scripts.
Two checks before you install anything on a managed host:
- Ask support, or read the plan page, to determine whether page caching is on by default.
- Load a page twice in a private window and look at the response headers for a cache hit (
x-cache,cf-cache-status, or your host’s own header).
If the answer is yes, skip the caching plugin. What’s still worth paying for is the front-end work—images, critical CSS, scripts—and a CDN if your host doesn’t include one. On WP Engine, that’s the NitroPack Add-On, which you add from the Products page in your User Portal. On any other host, it’s NitroPack itself.
How does a cloud service compare to caching plugins?
A cloud service builds the optimized page on its own servers and delivers it from a CDN, meaning your server no longer has to do the caching work. The plugins above build their cache on your own server and serve it from there by default. Edge delivery is something you add and configure: FlyingPress offers it through its Cloudflare integration or its paid FlyingCDN add-on, and W3 Total Cache’s Full Site Delivery needs the Pro licence plus a separate CDN subscription. A service includes it from the start.
NitroPack is a speed-optimization service that caches WordPress pages off the origin and replaces the page cache in an origin plugin such as LiteSpeed Cache or WP Rocket. It connects through a small WordPress plugin, takes about three minutes to set up, and behaves the same on a $5 shared plan as on a managed cluster, because your server only has to generate each page once before the CDN takes over.
- What it costs. The Free plan covers 1,000 pageviews a month with no credit card; Starter is $8 a month, or $7 billed annually, for 8,000 pageviews.
- What it doesn’t do. NitroPack is front-end only, so it won’t clean up your database—pair it with a tool like WP-Optimize if post revisions and transients have piled up. And it is a page cache, so switch caching off in any origin plugin you keep, or the two will serve each other’s stale copies.
Test your site on NitroPack’s Free plan—no credit card needed →
The final verdict on caching plugins
There is no single best caching plugin for every WordPress site; your web server picks it for you.
- On LiteSpeed or OpenLiteSpeed, install LiteSpeed Cache and keep your money.
- On Apache or Nginx, pay for WP Rocket or FlyingPress, knowing their page cache runs on your own server unless you add a full-page CDN.
- On any host, NitroPack is the pick when you’d rather hand caching, the CDN, and front-end optimization to one automated service.
Whichever you choose, run one page cache, and check what your host already does before you add anything. For the tools outside caching—image compression, script managers, database cleanup—we’ve compared those separately in the best plugins to speed up WordPress.
The quickest way to see what any of this means for your site is to run your homepage through NitroPack’s Website Speed Test. It shows how it would perform with NitroPack’s optimizations applied, and you decide whether to pay for that gap.
Try NitroPack on the Free plan—no credit card needed →
FAQs about caching plugins for WordPress
What are the differences between page caching, object caching, and browser caching in WordPress?
Page caching stores the finished HTML of a page so anonymous visitors get it without PHP or database work. Object caching (Redis or Memcached) stores the results of repeated database queries, which is what speeds things up for logged-in users. Browser caching sets how long images, CSS, and scripts stay on the visitor’s own device. How WordPress caching affects Core Web Vitals walks through all five layers.
What’s the best caching setup for a WooCommerce store?
Cache the catalog and product pages, and keep cart, checkout, and My Account out of the cache entirely, along with the WooCommerce session cookies. Most tools handle those exclusions for you, but a few need them set by hand. NitroPack’s Cart Cache, on the Plus plan and up, keeps serving cached pages to shoppers with items in their cart while the cart contents stay up to date. Store-specific rules, including cart fragments and object caching for logged-in customers, are in our WooCommerce cache plugin comparison.
Which caching plugin do developers prefer for advanced control?
Developers who want to hand-tune every layer usually reach for W3 Total Cache, or LiteSpeed Cache on a LiteSpeed server, because both expose page, object, and browser caching as separate settings. Teams that want the result without the tuning use NitroPack and leave the settings to the service. WP Rocket vs W3 Total Cache goes deeper on the control-versus-convenience trade-off.
Can I run two caching plugins at once?
No. Two full page caches on one site fight over which copy to serve, and you get stale pages, broken AJAX, or wrong cart contents. That includes NitroPack: it is a page cache in its own right, so disable caching in any origin plugin before you connect it, or remove the plugin altogether.
