Fix guide · LiteSpeed

LiteSpeed is serving the old page. Here’s how to clear it.

LiteSpeed caches whole pages on the server, in front of WordPress. It is fast, and it is the layer people forget, because it is a server setting rather than a file anyone wrote. Hostinger’s Cache Manager, for one, is LiteSpeed’s cache.

LiteSpeed answers from the server, before WordPress runs. Clearing a plugin cache or your browser does not clear it.

Not sure this is the layer? Paste your URL and the checker reads the headers for you.

Check my site

How to tell it’s LiteSpeed

Look at the response headers. Our checker shows them, or use your browser’s developer tools on the Network tab.

x-litespeed-cache: hitLiteSpeed served this page from its cache. source

x-litespeed-cache: hit,privateServed from a private, per-visitor cache entry. source

x-litespeed-cache: missNot from cache this time. LiteSpeed has started storing a copy for the next visitor. source

x-qc-cacheQUIC.cloud, LiteSpeed’s CDN, is also in front of the site. It keeps its own copy, so purge it too. source

(no LiteSpeed header)LiteSpeed didn’t serve this from cache. If the page is still old, look at the browser (below).

How to clear it

WordPress with the LiteSpeed Cache plugin

One page: hover the LiteSpeed icon in the black admin bar and choose Purge this page – LSCache. source
Everything: in wp-admin go to LiteSpeed Cache → Toolbox → Purge and press Purge All. It clears everything except Critical CSS, Unique CSS and LQIP. source
Command line: wp litespeed-purge all, or one URL with wp litespeed-purge url <url>. source
If QUIC.cloud is on: open the QUIC.cloud dashboard and press Purge All CDN Cache in the Domain Overview section. source

Not WordPress

Your app can tell LiteSpeed to drop cached pages by sending a response header: X-LiteSpeed-Purge: * for everything, or X-LiteSpeed-Purge: url=/path for one page. source On Hostinger, the Cache Manager in hPanel does the same from a button: see the Hostinger guide.

If the old page comes straight back

The LiteSpeed header is missing, but the page is still old. That is the browser. LiteSpeed’s own troubleshooting says to check the page for a cache-control header telling the browser to revalidate, then Purge All and refresh. source
Old CSS or JavaScript, new HTML. The plugin’s Browser Cache setting tells visitors’ browsers to keep static files, and its default TTL is 604,800 seconds, a week. Returning visitors can see old styling for that long unless the file name changes. source
It always says miss. That is the opposite problem: something is stopping LiteSpeed caching at all. The troubleshooting guide covers it. source

Working without it for a while

LiteSpeed Cache → Toolbox → Debug Settings → Disable All Features turns off caching and optimisation while you debug. Turn it back on afterwards. source

Other fix guides

Cloudflare Hostinger WordPress Vercel Netlify nginx Service workers

Sources

Every step above was written from these pages, read on 11 Sep 2026. Vendors move buttons; if one has moved, the source page will say where.