WordPress Caching, Explained Layer by Layer: Every Popular Plugin, Every Host Cache, and Which to Use
Which WordPress cache layer does what, how plugin and host caches conflict, how to read cache headers, and the order to purge. Plugin data checked 15 Nov 2026.

WordPress caching is not one switch. A request can be answered from your visitor’s browser, from a CDN edge, from your host’s page cache, from a static file a plugin wrote to disk, from PHP’s compiled-code cache, or from a memory-backed object cache, and each of those is a separate layer with its own settings and its own purge button. When a caching plugin “does nothing” or a page shows old content after an update, the cause is almost always that two layers are doing the same job, or that you are looking at a different layer than the one that answered.
Quick answer: run one page cache, not two. If your host already runs a page cache (LiteSpeed, Nginx, Varnish or an edge cache), keep the host’s cache and use a plugin only for the jobs the host skips, such as CSS and JavaScript tuning. On a plain shared host or VPS, use one page-cache plugin and add Redis for the object cache if the host offers it. To see which layer answered, request the page twice with curl -I and read cache-control, age, set-cookie and the host’s hit/miss header. When you purge, work from the origin outwards: object cache, plugin cache, host cache, CDN, and last the browser.
Plugin numbers in this guide come from the WordPress.org plugin API on 15 Nov 2026. Header names and host behaviour come from each vendor’s own documentation, linked where we use them, and were checked on the same day. We name a host only where its documentation says what we claim. For how caching shortens the wait for the first byte, we do not repeat the numbers here: see our TTFB optimisation guide.
In this guide
- What each cache layer does
- Whether you need a plugin when your host already caches
- What goes wrong when a page-cache plugin sits on top of host caching
- How to see which layer served a request
- The order to purge caches in
- Plugin numbers from WordPress.org, 15 Nov 2026
- Common mistakes people report
- Stores, communities and logged-in users
- The right setup for each host type
- For developers: headers, drop-ins and purge hooks
- FAQ
What does each WordPress cache layer do?
Each layer stores a different thing, closer to or further from the visitor, and each can only help with requests it is allowed to store. The table lists them in the order a request meets them. The first four skip PHP and the database entirely when they hit; the last two make an uncached request cheaper.

Layer | Where it lives | What it stores | Who controls it | How you purge it |
|---|---|---|---|---|
Browser cache | The visitor’s device | Images, CSS, JavaScript, sometimes HTML | Your | Only the visitor can; you change file URLs or headers |
CDN or edge cache | Provider’s data centres | Static files, and full pages if configured | CDN rules, origin headers | CDN dashboard, API or plugin integration |
Page cache | Host server (Nginx, Varnish, LiteSpeed) or plugin files on disk | The finished HTML of a page | Host or caching plugin | Host panel, plugin button, WP-CLI or code |
OPcache | PHP process memory | Compiled PHP code, not data | PHP settings on the server | PHP-FPM reload or host tool |
Object cache | Redis or Memcached memory | Query results and computed values | An |
|
Transients | Options table, or the object cache if one exists | Temporary values with an expiry | Plugins and themes through the Transients API | Expiry, or a cleanup |
Browser cache
The browser keeps files so the next page view does not download them again. You control it with response headers on static files. For logged-in screens WordPress deliberately forbids it: wp_get_nocache_headers() returns Cache-Control: no-cache, must-revalidate, max-age=0, no-store, private plus an Expires date in 1984, and core sends them for the admin, the REST API and logged-in requests. That is why a logged-in page never benefits from layers one to three.
CDN and edge cache
A CDN stores copies near the visitor. By default most CDNs cache static files and pass HTML through to your origin, so “I use a CDN” does not mean your pages are cached at the edge. Cloudflare, for example, documents exactly why a response was or was not cached through the cf-cache-status header, covered in the header section below. Full-page edge caching is an opt-in feature, and it usually refuses any response that sets a cookie.
Page cache
A page cache saves the finished HTML so PHP and MySQL do not run at all for a repeat visitor. It lives either on the server (Nginx FastCGI cache, Varnish, LiteSpeed) or as static files written by a plugin through the advanced-cache.php drop-in and the WP_CACHE constant. It is the layer with the biggest effect on public pages and the one most often duplicated. If you run Nginx yourself, our Nginx FastCGI cache setup and purge guide covers the server side.
OPcache
OPcache keeps compiled PHP in memory so the server does not re-read and re-compile every file on every request. It is a PHP extension setting, not a WordPress feature, and it helps every uncached request, logged-in ones included. Tuning it is covered in our PHP OPcache settings guide. After a code deploy, a stale OPcache can keep serving old PHP, which is a different symptom from stale HTML.
Object cache
By default WordPress remembers objects (options, users, post data, query results) only for the length of one request. A persistent object cache stores them in Redis or Memcached between requests through the object-cache.php drop-in in wp-content. It matters most for logged-in traffic, admin screens, stores and communities, because those requests cannot use the page cache.
Transients
Transients are temporary values stored through set_transient(). Without a persistent object cache they are written to the wp_options table with an expiry time; with one, they live in the cache and the database never sees them. That difference is why a site that adds Redis often sees its options table stop growing. Expired rows left behind in the database are a housekeeping job, covered in how to delete expired transients, which we will not repeat here.
Tip: logged-in visitors skip the browser, edge and page layers, so on a store or a community the object cache and OPcache matter more than the page cache. The database buffer pool sits behind all of this; we cover its settings in the MySQL tuning guide.
Do I need a caching plugin if my host already caches?
Usually not for page caching, and sometimes for nothing at all. Most managed hosts run a page cache at the server, and it never appears in your plugin list, which is why people forget it exists and add a second one. Ask support which layers are active, then read the headers to confirm. The table shows what the hosts’ own documentation says, as checked on 15 Nov 2026.
Host | What its docs confirm | Header to read | What the docs say about plugins |
|---|---|---|---|
Kinsta | Site cache, optional edge cache on Cloudflare’s network; logged-in users bypass |
| Clear plugin or theme caches first, then Kinsta’s |
WP Engine | Page cache with a 600-second default expiry; network caches including CDN |
| Plugins and themes often cache too; purge them when changes do not show |
SiteGround | Dynamic cache on its servers; Speed Optimizer plugin purges it |
| Use the plugin or Site Tools to purge; |
Cloudways | Varnish in front of the app, Breeze as the matching plugin | Often | A per-app purge in the platform clears all layers for that app; a server-level Varnish purge is separate |
LiteSpeed-based hosts | Server-level LiteSpeed cache, driven by the LiteSpeed Cache plugin |
| The plugin is the control panel for the server cache |
Sources: Kinsta edge caching, WP Engine cache documentation, SiteGround dynamic cache, LiteSpeed Cache troubleshooting. Cloudways documents its purge options in its help article on purging application cache; we could not find an official statement of its Varnish header name, so check it with curl -I rather than trusting a third party.
Two things follow. “Managed host” does not always mean “no plugin”: a host cache does the page caching, but you may still want a plugin for JavaScript delay, critical CSS or database cleanup. And a host cache is invisible inside WordPress, so a plugin that offers page caching will happily switch it on without knowing the server already does the same thing.
What goes wrong when a page-cache plugin sits on top of host caching?
You get two copies of every page, purged at different times, with rules that can cancel each other out. The symptoms are predictable, and each one is visible in the headers.
- Old content after an update. The plugin purged its copy, but the host or CDN still holds an older one. The visitor sees whichever layer answers first.
- A host cache that never hits. WP Rocket documents a case where its
.htaccessrule sets HTML expiry to zero, which can stop an upstream cache such as Varnish from working and shows asx-cache: MISSorx-proxy-cache: MISS. Its fix is a helper plugin that removes that rule. The details are in WP Rocket’s own article. - Both layers skipping the same pages. A cookie or a
no-storeheader that one layer treats as “do not cache” is usually treated the same way by the other, so adding a second layer does not rescue pages the first one rejects. - Double work on a hit. The server cache answers first, so the plugin’s cache folder stays empty and its page-cache setting does nothing. WP Rocket’s documentation notes that some hosts run their own page cache, which leaves its cache folder empty.
The fix is to keep one page cache. If your host runs one, turn off page caching in the plugin and keep only its optimisation features. If you want the plugin’s page cache instead, ask the host whether its own can be disabled for your site. Two page caches that both want the same advanced-cache.php file also fight outright, and only one can own it.
How can I see which cache layer served a request?
Read the response headers of a logged-out request, twice. The first request may be a miss; the second should be a hit if the page is cacheable. Checked on 15 Nov 2026:
curl -sI https://example.com/ | grep -iE '^(cache-control|age|set-cookie|x-cache|x-proxy-cache|x-kinsta-cache|x-litespeed-cache|cf-cache-status|x-varnish|server)'
# run it again, then compare the two answersHeader | Who sets it | What it tells you |
|---|---|---|
| Cloudflare | HIT: found in cache. MISS: eligible but not cached yet, so the origin answered. EXPIRED: cached but stale, origin answered. DYNAMIC: not eligible for caching. BYPASS: origin response was not cacheable (for example |
| Any cache | Seconds a stored copy has been held. Cloudflare sets it on HIT, STALE and UPDATING, not on MISS, DYNAMIC or BYPASS. |
| Kinsta | Whether Kinsta’s site cache served the page. It must be HIT before the edge cache can apply. |
| Kinsta edge | Edge caching is working when the type is Edge and the status is HIT or SAVING. |
| WP Engine, and Varnish setups | HIT served from cache, MISS not. On WP Engine, |
| SiteGround | HIT cached. MISS served dynamically (first request, or cache off). BYPASS the cache was told to skip it, for example for a logged-in user or a cart cookie. |
| LiteSpeed |
|
| Your origin | Whether shared caches may keep the page. |
| Your origin | A cookie on a public page often explains a BYPASS or a miss. |
Not every layer exposes a header. WP Rocket’s page cache, for example, does not add a hit/miss header; its documentation tells you to look at the bottom of the page source for the comment Performance optimized by WP Rocket followed by a Debug: cached@ timestamp, or to check the wp-content/cache/wp-rocket/ folder. If no layer announces itself, time the request: a cached page returns in tens of milliseconds, an uncached one usually takes several hundred or more.
Several headers can appear together, and the combination is the answer. A cf-cache-status: DYNAMIC next to x-proxy-cache: HIT means the host cached it and Cloudflare did not; a cf-cache-status: HIT next to a host MISS means the edge answered before the request reached the host. We saw a live example while writing this guide: this very page was served with cf-cache-status: UPDATING and a non-zero age, so Cloudflare was answering from its stored copy while refreshing it in the background, even though the origin’s own cache-control says no-cache. That is why you read the hit/miss header and age, and do not infer the answer from cache-control alone.
Test logged-in and logged-out separately
Open the browser’s Network tab, load the page in a private window, and read the document request’s headers. Then repeat while logged in. A logged-in response should not come from a shared page cache. Hosts say the same: Kinsta’s docs state that anywhere a user is logged in bypasses caching, and SiteGround lists wordpress_logged_in_ among the cookies that cause a BYPASS.
Warning: if you copy a logged-in cookie into a curl command to test, delete it afterwards and never paste it into a ticket or chat. It is a working login.
Confirm what is installed
wp plugin list --status=active --field=name | grep -iE 'cache|rocket|litespeed|w3-total|autoptimize|breeze|fastest|flying'
ls wp-content/advanced-cache.php wp-content/object-cache.php
wp cache typeAn advanced-cache.php file means a page-cache plugin has installed its drop-in. An object-cache.php file means a persistent object cache is wired in. wp cache type reports which object cache WordPress is using. Checked on 15 Nov 2026.
In what order should I purge caches?
Purge from the origin outwards: the layer closest to WordPress first, the layer closest to the visitor last. Each outer layer refills from the one behind it, so if you purge the CDN before the host cache, the CDN simply fetches the stale copy again and stores it fresh. Kinsta’s documentation gives the same advice for its own stack: clear plugin or theme caches first, then Kinsta’s caches.
- OPcache, only after a code deploy. If PHP files changed and behaviour did not, reload PHP-FPM or use the host’s tool. A page purge does nothing for stale compiled code.
- Object cache, only if stored data is wrong.
wp cache flushempties it. On a busy store this causes a short burst of database load while it refills, so do it deliberately and not after every edit. - Plugin page cache and its minified files. Use the plugin’s own “clear all” so combined CSS and JavaScript are rebuilt too.
- Host page cache. Kinsta, WP Engine, SiteGround and Cloudways each have their own button or CLI command. Know which scope it covers: WP Engine’s “Clear All Caches” in the admin clears page cache and network caches but not the object cache, and Cloudways separates the per-app purge from a server-level Varnish purge.
- CDN or edge. Purge by URL when you changed one page, everything when you changed the theme or core. Kinsta notes that clearing edge cache across Cloudflare’s data centres can take 2 to 5 minutes, so wait before judging the result.
- Browser. You cannot purge your visitors’ browsers; WP Engine’s documentation says browser cache can only be purged for your own device. Hard-reload to test, and change file names or versions (cache busting) when a static asset must refresh for everyone.
Many hosts purge their own layers automatically when you publish or update content, so a full manual sequence is for theme, plugin and core updates, not for fixing a typo. After the purge, load the home page logged out and run the header check again, then load a logged-in page and confirm it was not served from a shared cache. For a store or community, purge everything after each update, because a cached page or combined script file built for the old version can outlive it.
How do the popular caching plugins compare on WordPress.org, 15 Nov 2026?
All figures below come from the WordPress.org plugin API on 15 Nov 2026. Ratings are converted from the API’s 0 to 100 score to five stars. “Support threads” is the number of support threads resolved out of those opened in the last two months, as the API reports them. These numbers say how a plugin is maintained and supported; they are not speed results, and we have not benchmarked these plugins against each other.
Plugin | Rating (reviews) | Active installs | Version | Last updated | Tested up to | Support threads resolved |
|---|---|---|---|---|---|---|
4.8 (2,782) | 7 million+ | 7.9.3 | 3 Nov 2026 | 7.1.4 | 43 of 83 | |
4.4 (5,420) | 900,000+ | 2.11.0 | 20 Oct 2026 | 7.1.4 | 7 of 14 | |
4.3 (1,346) | 1 million+ | 3.1.5 | 2 Nov 2026 | 7.1.4 | 5 of 6 | |
4.9 (4,233) | 1 million+ | 1.5.5 | 5 Nov 2026 | 7.1.4 | 9 of 15 | |
3.6 (134) | 300,000+ | 2.6.4 | 2 Nov 2026 | 7.1.4 | 7 of 15 | |
4.3 (139) | 100,000+ | 1.8.17 | 27 Sep 2026 | 7.1.4 | 0 of 1 | |
4.7 (1,488) | 70,000+ | 4.0.2 | 9 Nov 2026 | 7.1.4 | 2 of 2 | |
4.7 (1,429) | 800,000+ | 3.1.17 | 25 Oct 2026 | 7.1.4 | 4 of 5 | |
4.5 (179) | 500,000+ | 3.0.0 | 18 Sep 2026 | 7.1.4 | 6 of 7 | |
4.2 (641) | 1 million+ | 7.8.6 | 2 Nov 2026 | 7.1.4 | 5 of 7 |
WP Rocket and FlyingPress are paid products and are not listed on WordPress.org, so they have no API figures. Their own pricing pages list the plans: WP Rocket shows Single (1 site), Plus (3 sites) and Multi (50 sites) plans quoted per month on one-year and three-year terms, with a 14-day trial; FlyingPress lists Starter, Pro, Business and Unlimited plans from $59 a year on renewal, with a 14-day trial. Prices change, so read the page before you decide.
Which layer each plugin touches matters more than the star count, because it tells you whether it will collide with your host:
Plugin | Page cache | CSS and JS tuning | Object cache | Collides with a host page cache? |
|---|---|---|---|---|
LiteSpeed Cache | Yes, on LiteSpeed servers or through QUIC.cloud | Yes, on any server | Connects to Redis or Memcached | No on LiteSpeed hosts, where it controls the host cache; yes elsewhere if page cache is switched on |
WP Rocket (paid) | Yes | Yes, including delay JavaScript | No | Yes; may need the host’s page cache or its own switched off |
W3 Total Cache | Yes | Minify in free; delay scripts in Pro | Yes, in free | Yes |
WP Super Cache | Yes | No | No | Yes |
WP Fastest Cache | Yes | Most in Premium | No | Yes |
Breeze | Yes, Varnish-aware | Yes | No | Designed to work with Cloudways Varnish |
Cache Enabler | Yes | HTML minify only | No | Yes |
Autoptimize | No in the free version | Yes | No | No; it pairs with a page cache |
Redis Object Cache | No | No | Yes, needs a Redis server | No; it is a different layer |
Plugin capabilities in the second table were checked against each plugin’s WordPress.org page or official site in October 2026 and spot-checked on 15 Nov 2026; confirm a specific feature on the vendor page before you pay for it. For a head-to-head between two paid and free contenders, our sister site compares WP Rocket vs LiteSpeed Cache.
What are the common mistakes people report?
The same handful of problems appear in support forums and vendor documentation again and again. This box lists six, paraphrased, with the source of each. Checked on 15 Nov 2026.
Common mistakes people report
- Stacking a plugin page cache on a host cache that already works. WP Rocket’s own documentation explains that its zero-expiry rule for HTML can keep a Varnish or proxy layer from ever hitting. Source: WP Rocket, “X-Cache MISS when WP Rocket is activated”.
- A cookie on public pages that stops the edge cache. Kinsta’s documentation says edge caching does not work for requests that return a
Set-Cookieheader. A WordPress.org thread about a Cloudways, Cloudflare and Varnish stack showsx-cache: MISSwithcf-cache-status: BYPASSon dynamic pages, traced by a plugin author to a PHP-set cookie; cookies set in JavaScript did not cause it. The thread is older (last modified October 2023) but the cause is still current. Source: WordPress.org support thread. Our own method for finding these is in the cookies quietly bypassing your page cache. - Expecting a HIT on the first request, or while logged in. SiteGround’s documentation says the first request for a page in a 12-hour window is a MISS, and that logged-in requests and cart cookies produce BYPASS. Test twice, logged out. Source: SiteGround dynamic cache documentation.
- The whole cache disappears and nobody knows why. A recent thread reports a site with about 2,200 pages losing both its cache counters now and then. Support’s first answer was that WP Super Cache does not clear itself when plugins are activated, and that another plugin calling
wp_cache_clear_cache()is the likely cause; the user’s search found two plugins that call it, and the thread was still unresolved when we checked. Source: WordPress.org support thread, October 2026. - Preload that seems to delete the cache. On a WooCommerce site, cached files fell after each preload run. Support explained that the homepage cache is cleared after each batch, that a refresh interval of 0 removes files older than 24 hours that the run did not refresh, and that product categories and tags are not preloaded by default. The
DONOTCACHEPAGElines the user saw came from cart, checkout and account pages. Source: WordPress.org support thread, October 2026. - Purging one layer and calling it done. WP Engine’s documentation notes that plugins and themes often cache content as well and should be purged separately, and that its admin “Clear All Caches” does not clear the object cache. Source: WP Engine cache documentation.
What should you cache on stores, communities and logged-in sites?
Cache public pages and exclude anything personal. On a store, never serve a cached cart, checkout or account page to anyone but the person it was built for, and keep the cookies that mark a cart out of the page-cache key. Every serious page-cache plugin ships WooCommerce defaults that exclude those pages; check the exclusions after any plugin change, and again if you rename the pages. Cached product and shop pages are fine; the mini-cart count must stay dynamic.
Communities are the riskiest case, because a member’s feed, inbox and notifications are built for them alone. Most plugins offer an option to cache logged-in users too, and for a community we would leave it off and rely on the object cache. The BuddyNext team tested the logged-in settings of four page-cache plugins with a Redis object cache running throughout and checked what members and guests received:
Plugin | Setting tested | Result |
|---|---|---|
WP Super Cache | Cache known users | Members fresh, guests cached |
W3 Total Cache | Page cache on, logged-in exclusion off | Members fresh, guests cached |
WP Rocket | User Cache add-on on | Members fresh, guests cached |
LiteSpeed Cache (OpenLiteSpeed) | Cache Logged-in Users on | Members fresh, guests cached |
The result held because BuddyNext marks its member pages as uncacheable itself, with the standard DONOTCACHEPAGE signal and Cache-Control: no-store, not because those plugins are safe for logged-in pages by default. A plugin that ignores the signal can still serve the wrong page. BuddyNext also purges the affected guest pages when a community post changes. Cloudflare APO and hand-written Varnish rules were not tested. The full results are in the BuddyNext page cache documentation, and our sister site covers the hosting side in Community Site Hosting Guide: What BuddyNext Really Needs. We make BuddyNext, so weigh that test as a vendor’s own result for its own plugin.
Which caching setup is right for your host?
Match the setup to the cache your host already runs. The goal is one page cache, one object cache where the host offers it, and optimisation tuning only where it is not already handled.

Your host | Page cache | Plugin | Object cache |
|---|---|---|---|
LiteSpeed server (for example Hostinger) | LiteSpeed server cache | LiteSpeed Cache | LiteSpeed’s object cache connection, if offered |
Own page cache (Nginx, Varnish, edge) | The host’s | None, or Autoptimize or similar for CSS and JS only | Host’s Redis if offered |
Cloudways with Varnish | Varnish | Breeze, set to work with Varnish | Redis if enabled |
Plain shared host or VPS | One page-cache plugin | WP Rocket, WP Super Cache or Cache Enabler | Redis Object Cache if Redis exists |
Cloudflare in front | Edge rules or APO, plus an origin cache | As for your origin | As for your origin |
If you run a small blog on a plain host, WP Super Cache or Cache Enabler is enough. If you want one plugin to do the page cache, the CSS and JavaScript tuning and the preload, WP Rocket or FlyingPress is the paid route. If you want the most control for free and are willing to learn the settings, W3 Total Cache is the option, and a large share of its misconfigurations come from switching on every feature at once. On a LiteSpeed host there is rarely a reason to look past LiteSpeed Cache.
For developers: headers, drop-ins and purge hooks
Treat the cache stack as a set of drop-ins and headers. A page-cache plugin owns advanced-cache.php and the WP_CACHE constant; the object cache owns object-cache.php. Only one of each can exist, which is why two plugins that both want the same drop-in fight.
Reading Vary and Cache-Control
A Vary: Cookie or Vary: User-Agent header multiplies cache entries, so check what you vary on. Cache-Control: private tells shared caches to keep out, which is right for logged-in pages and a bug on public ones.
Marking a response uncacheable
Plugins that honour the standard signal skip caching when the DONOTCACHEPAGE constant is set early in the request. nocache_headers() sends the no-cache headers that browsers and proxies respect.
add_action( 'template_redirect', function () {
if ( is_user_logged_in() || ( function_exists( 'is_checkout' ) && is_checkout() ) ) {
if ( ! defined( 'DONOTCACHEPAGE' ) ) {
define( 'DONOTCACHEPAGE', true );
}
nocache_headers();
}
} );
// checked on 15 Nov 2026 against developer.wordpress.orgUse it only for pages that really are personal. Setting it site-wide turns the page cache off.
Purging from code
There is no single purge function across cache plugins, so call each plugin’s documented one and guard it. LiteSpeed Cache documents three actions, litespeed_purge_all, litespeed_purge_post and litespeed_purge_url, in its developer API. WP Rocket documents rocket_clean_domain() and recommends a function_exists() check first.
function tweakswp_purge_page_caches( int $post_id ): void {
if ( function_exists( 'rocket_clean_domain' ) ) {
rocket_clean_domain();
}
// Fires for LiteSpeed Cache; does nothing if the plugin is absent.
do_action( 'litespeed_purge_post', $post_id );
}
// checked on 15 Nov 2026 against the LiteSpeed and WP Rocket documentationAnd the WP-CLI side, which several hosts also wrap in their own commands (SiteGround documents wp sg purge):
wp cache flush # object cache
wp transient delete --expired # expired transients only
wp cache type # which object cache is active
# checked on 15 Nov 2026When don’t you need a caching plugin?
You may not need one if your host already runs a page cache and your pages are mostly static, or if the site is behind a full-page edge cache, or if your slowness is somewhere else. A slow admin, a slow checkout and a slow first byte on uncached pages are not page-cache problems: look at the object cache, OPcache and database first. Our guide to reducing time to first byte shows how to tell which layer is the slow one.
FAQ
Can I use two caching plugins at once?
Not two page caches. You can pair one page-cache plugin with an optimisation-only plugin such as Autoptimize and with a separate object-cache plugin such as Redis Object Cache. Two plugins that both create page caches, or both want the same drop-in file, will conflict.
Do I need a caching plugin on managed WordPress hosting?
Often not. Kinsta, WP Engine and SiteGround each document server-level page caching. Keep the host’s cache as the page cache and add a plugin only for tasks the host does not do, such as JavaScript delay or critical CSS.
Is LiteSpeed Cache useful if my host does not run LiteSpeed?
Partly. Its page caching needs a LiteSpeed server or QUIC.cloud. Its optimisation features, such as minify, combine, lazy load and database cleaning, work on any server, but other plugins cover that ground too.
Which is the best free caching plugin?
It depends on your host. On a LiteSpeed host, LiteSpeed Cache. On a plain host, WP Super Cache or Cache Enabler for simple page caching, and W3 Total Cache if you want every option. Pair any of them with Autoptimize if you need CSS and JavaScript tuning.
Why does my site show old content after an update?
One of the layers is still serving a stored copy. Purge from the origin outwards (plugin cache, host cache, CDN), then check the headers to see which layer answered. If the content is right in a private window but wrong in your normal browser, it is your own browser cache.
How do I know if my host has its own page cache?
Request the page twice with curl -I and look for a hit/miss header from the table above. If the second request shows a HIT while your caching plugin’s cache folder stays empty, the host cache is answering.
Should logged-in users be cached?
Only if the cache keeps each user’s copy separate and your pages are safe to store. For stores and communities the safer rule is to leave logged-in page caching off and use an object cache for speed.
Do transients count as a cache?
Yes, a small one. They store temporary values with an expiry, in the options table or, with a persistent object cache, in memory. Cleanup of expired rows is covered in our expired transients guide.
What to do next
Run the header check on your home page today and write down which layer answers. Compare it with the host table above and switch off the extra page cache if there are two. If you manage a store or community on a stack you do not fully control, our team at Wbcom Designs can audit the cache layers for you; we would start with the header check and a logged-in test, which is the same free check described in this guide.
Related reading
Plugins we build and run
We maintain these ourselves, which is why we can support them on your site.
- BuddyNextThe self-hosted community engine for WordPress
- BuddyXFree community theme, Pro when you outgrow it
- ReignPremium community theme. Add pieces, build anything
- JetonomyCommunity forum and Q&A for WordPress
- EventonomyEvents and RSVPs for WordPress communities
- LearnomyCourses and learning communities on WordPress
- ListoraDirectories and listings your members can browse
- SnipShareCode sharing built for developer communities
- WB Ad ManagerAd placements that turn traffic into revenue
- WP Career BoardA job board your community actually uses
- WP Sell ServicesSell services with offers, orders, and payouts
- MediaVersePhotos, video, and media albums for members
- WB GamificationPoints, badges, and rewards that keep members active
- Product RoadmapPublic roadmaps with voting your users trust
Related Posts

LiteSpeed Cache Vulnerability CVE-2026-93389: Check Your Version and What Was Exposed

Freemius SDK Stored XSS: How to Find Every Bundled Copy on a Client Site (Anything Under 2.13.5)

