The challenge is that caching isn’t one thing. There’s page caching, object caching, edge caching, server-level caching, and CDN caching — and most well-optimized sites are using several of these layers at once. Add in the fact that your hosting environment largely dictates what’s even available to you, and the “best caching plugin” question becomes almost impossible to answer in isolation.
We asked the members of The Admin Bar what caching solutions they rely on and what makes them effective. The answers reflected exactly that complexity — a lot of layered setups, a strong preference for server-level solutions, and a few plugin picks that keep coming back.
Here’s what the community had to say.
The Most Mentioned Caching Solutions
- LiteSpeed Cache
- Cloudflare
- FlyingPress
- WP Fastest Cache
- WP Rocket
- Object Caching (Redis)
- Other Solutions Worth Knowing
Why Agencies Choose These Caching Solutions
LiteSpeed Cache
LiteSpeed Cache came up more than any other single solution in this thread — but with an important caveat that members were consistent about flagging: it only makes sense on a LiteSpeed server.
Ben Wade put it plainly: “LiteSpeed cache but only on an actual LiteSpeed server.” Ishfaq Farooq Mir echoed it: “LiteSpeed Cache if using a LiteSpeed server, otherwise WP Fastest Cache.” Melanie Barkdull Adcock, Jay Taylor, Anil Agrawal, Ergys Llojaj, and Lucian Pascu are all running LiteSpeed Cache on LiteSpeed servers — usually paired with Cloudflare for an additional edge caching layer.
The reason it comes up so often is simple: when your server and your caching plugin are built to work together, you’re not fighting your infrastructure. LiteSpeed Cache can tap directly into server-level features that no third-party plugin on a non-LiteSpeed server can replicate.
Best fit: any site running on a LiteSpeed server — which includes a number of popular hosting options like Cloudways (OpenLiteSpeed), GridPane (LiteSpeed Enterprise), and dedicated LiteSpeed setups.
Cloudflare
Cloudflare isn’t a caching plugin — it’s an edge network that sits in front of your entire site — and for agencies managing multiple client sites, it came up repeatedly as a foundational layer rather than an optional extra.
Rob Marlbrough runs Cloudflare on 99.9% of the sites he manages and uses it for full HTML edge caching:
“I run Cloudflare on 99.9% of the sites I manage, and so it’s silly not to take advantage of full HTML edge caching closest to the visitor (along with nginx and Redis caching to speed up origin hits to refresh the edge cache). I use the Super Page Cache plugin since it’s free and simple to implement. It automatically rebuilds the pages when changes are made, and automatically bypasses the edge cache for dynamic requests and pages.”
Rob Marlbrough
Massimo Villa uses Cloudflare for edge caching, Super Page Cache for page caching, and Redis for object caching — a clean three-layer stack. Alex Celeste runs Cloudflare across all sites but notes it’s easy to forget about until a media item isn’t showing up correctly after an update. Amy Jo Higgins relies on Cloudflare alone for most of her smaller client sites and gets 90–100 PageSpeed scores without much else. Darius Zak caches everything through Cloudflare using advanced filters to exclude dynamic elements.
The common theme: Cloudflare adds a layer of performance that’s independent of whatever caching plugin or server setup you’re running underneath it.
Best fit: agencies managing multiple client sites who want a consistent, reliable edge caching layer across their entire portfolio.
FlyingPress
FlyingPress has been gaining real traction in this community as a premium caching and optimization plugin — and the members using it tend to be enthusiastic.
Marion Paolo Abagar called it out simply: “FlyingPress FTW.” Dustin Dauncey was more specific:
“FlyingPress is my fave caching solution, and their recently added image optimization has completely replaced ShortPixel for me too — reducing the costs of buying ShortPixel credits.”
Dustin Dauncey
Chris Key uses it but notes occasional JavaScript conflicts on mobile menus when it’s active — a tradeoff worth testing on any JS-heavy build. Vojkan Cvijanovic runs the free version of WP Fastest Cache alongside the paid version of FlyingPress, though he flagged that the API connection uses a global account key rather than a domain-level key, which is a pain point for agency workflows managing many sites.
Best fit: agencies who want an all-in-one caching and optimization plugin and don’t mind a premium price; especially useful if you’re also looking to consolidate image optimization into one tool.
WP Fastest Cache
WP Fastest Cache is the low-fuss option — and for agencies managing simpler sites, that’s exactly what you want.
Rose Newell makes the case for it clearly:
“WP Fastest Cache is honestly plenty — I get quad 100s. Plus the right settings in Nginx of course.”
Rose Newell
She also notes she doesn’t even use the paid version: “I honestly don’t even use or need more than the free version.” Marcel Botezat agreed. Debbie Albin and Vojkan Cvijanovic are both using it as part of their stack as well.
The pattern here is that WP Fastest Cache works well when the rest of your setup is solid — good hosting, Nginx configured correctly, and a site that isn’t doing anything exotic. It’s not going to carry a poorly configured environment, but it doesn’t need to if the foundation is right.
Best fit: agencies running well-optimized hosting environments who want a simple, free caching solution that stays out of the way.
WP Rocket
WP Rocket is the premium caching plugin most WordPress professionals know by name — and it still has plenty of advocates, even as server-level alternatives have improved.
Jermain Mayland pairs it with server caching and object caching. Matt Schwartz takes a practical approach worth noting: stick with whatever the host recommends, including WP Rocket on Rocket.net, Breeze on Cloudways, and Pressable Cache on Pressable. The logic is sound — hosts build around their recommended solutions and are more likely to support you when something goes wrong.
Chris Key came to the thread from the opposite direction: he’s moved away from managing caching himself entirely, leaving Rocket.net to handle it at the server level, and only occasionally tests FlyingPress alongside it.
Best fit: agencies on managed hosts that recommend WP Rocket, or those who want a well-documented premium plugin with broad compatibility.
Object Caching (Redis)
Object caching came up repeatedly not as a standalone solution but as an essential second layer alongside page caching — and Redis is the implementation most members mentioned.
Alex Celeste runs server-level page caching and Redis object caching through SpinupWP, with Cloudflare on top. Massimo Villa’s stack explicitly includes Redis as the object cache layer. Jermain Mayland pairs server caching with object cache. Saurabh Guttedar couples his own caching plugin (Warp Performance) with Redis object cache and OPCache, calling both “very important.”
Object caching stores the results of database queries so WordPress doesn’t have to repeat expensive lookups on every page load. For sites with dynamic content, logged-in users, or complex queries, it can make a significant difference that page caching alone can’t address.
Best fit: any site with meaningful database activity — WooCommerce, membership sites, heavily queried content — where page caching alone doesn’t fully solve the performance picture.
Other Solutions Worth Knowing
These also came up in the thread:
- NitroPack — George Manty’s favorite; an all-in-one performance and caching service that handles optimization as a managed service rather than a plugin you configure yourself
- Swift Performance AI — Steve uses it on LiteSpeed servers and gets above-90 PageSpeed scores consistently; notes it’s too much for Apache environments
- Hummingbird Pro — Keith Eldridge uses it on WPMU DEV hosting with FastCGI page caching and Cloudflare integration, including cache flushing from WP Admin
- Super Page Cache — Rob Marlbrough and Massimo Villa both use this free plugin to bridge WordPress with Cloudflare’s edge cache; worth knowing if you’re on Cloudflare and want automatic cache rebuilding on page edits
- WPCompress — Steve uses it on Apache/cheaper hosts where Swift Performance would be overkill; generates critical CSS on demand, though he notes it would benefit from cache warming
- Warp Performance — Saurabh Guttedar’s own plugin, paired with Redis and OPCache
Patterns We Noticed
Hosting and caching are inseparable. Cathy Larkin said it in the thread and it’s worth repeating: you can’t really talk about caching without talking about your hosting environment. LiteSpeed Cache on a LiteSpeed server is a fundamentally different setup than the same plugin on an Apache server. Scott Macon put it bluntly: “Nothing beats server-level caching.” The members getting the best results are consistently the ones whose caching strategy matches their hosting stack.
Most agencies are running multiple cache layers. The thread was full of stacked approaches: server-level page cache + Redis object cache + Cloudflare edge cache. These layers serve different purposes and compound each other’s benefits. If you’re only running one, there’s likely performance left on the table.
Use what your host recommends. Matt Schwartz’s approach — sticking with the host’s recommended caching solution — is practical advice that came up in different forms throughout the thread. Hosts design their infrastructure around specific plugins and are better positioned to troubleshoot when things go wrong.
Ecommerce and membership sites need a different approach. Keith Eldridge and others noted that caching settings can’t be one-size-fits-all. WooCommerce cart pages, checkout, and logged-in user sessions all need to be excluded from page caching, which requires careful configuration that a simpler setup might not handle correctly.
Some agencies skip plugins entirely. Chris Key trusts Rocket.net’s server-level caching and doesn’t manage a caching plugin at all. Amy Jo Higgins gets 90–100 scores using just Cloudflare on smaller static sites. For the right hosting environment and site type, less really can be more.
How to Choose a Caching Solution
A few questions worth working through before you commit to a setup:
What server type is your host running? LiteSpeed, Nginx, and Apache each have different caching options available. LiteSpeed Cache is only worth installing if you’re on a LiteSpeed server. Nginx has its own fastcgi cache. Know your stack first.
Does your host already handle caching? Managed hosts like Rocket.net, Pressable, and WP Engine all include server-level caching. Adding a caching plugin on top may conflict rather than compound. Check before you install.
Is your site static or dynamic? A simple brochure site and a WooCommerce store need fundamentally different caching strategies. Dynamic content, cart sessions, and logged-in users all require cache exclusions that simpler setups don’t handle well.
Are you already using Cloudflare? If so, adding a plugin that bridges WordPress with Cloudflare’s edge cache (like Super Page Cache) can give you a significant boost without much additional complexity.
Do you need image optimization too? If you’re paying for both a caching plugin and an image optimization service, FlyingPress or NitroPack may let you consolidate into one tool and reduce overall costs.
Frequently Asked Questions About WordPress Caching
What’s the best WordPress caching plugin for agencies? There’s no single answer — it depends on your hosting environment. LiteSpeed Cache is the top pick for LiteSpeed servers. FlyingPress and WP Rocket are strong all-around premium options. WP Fastest Cache is a solid free choice for simpler setups. Most high-performing sites also add Cloudflare and Redis object caching on top.
Do I need a caching plugin if my host already provides caching? Not always. Many managed hosts (Rocket.net, Pressable, WP Engine, SiteGround) include server-level page caching built in. Adding a caching plugin on top can sometimes cause conflicts. Check what your host provides before installing one.
What is Redis object caching and do I need it? Redis stores the results of database queries in memory so WordPress doesn’t have to repeat them on every page load. It’s most beneficial on sites with significant database activity — WooCommerce, membership sites, or content-heavy sites with lots of queries. For simple brochure sites, it’s less critical.
Is Cloudflare a replacement for a caching plugin? Not exactly — Cloudflare provides edge caching (serving cached pages from servers close to your visitors), while a caching plugin typically handles page and object caching at the server level. They serve complementary purposes. Many agencies run both.
Does caching break WooCommerce or membership sites? It can if not configured correctly. Cart pages, checkout, account pages, and any content personalized to logged-in users need to be excluded from page caching. Most caching plugins have WooCommerce-specific settings, but they need to be enabled and tested carefully.
