Speed & performance · Explainer
Do You Need a Cache Plugin on LiteSpeed Hosting?
Short answer
Yes, you need a cache plugin on LiteSpeed hosting, and the right one is LiteSpeed Cache. The host provides the server-level cache engine, but the plugin switches it on, sets how long pages stay cached, and clears old pages when you edit content. Without the plugin, that engine sits idle and every visit rebuilds each page from PHP and the database.
Key takeaways
- LiteSpeed hosting includes a server-level page cache, but the LiteSpeed Cache plugin is what switches it on and controls it.
- A page cache stores a finished HTML copy so repeat visits skip PHP and database queries.
- LiteSpeed Cache needs WordPress 6.0 or higher and PHP 7.4 or higher, as of November 2026.
- The default public cache TTL is 604800 seconds, which is 1 week, while private cache defaults to 1800 seconds.
- OpenLiteSpeed does not support ESI, so dynamic parts of a page need a different setup there.
- Logged-in pages, cart pages and checkout pages need private cache or exclusion, not public cache.
Do you need a cache plugin on LiteSpeed hosting?
Yes, you need the LiteSpeed Cache plugin, because LiteSpeed hosting provides the cache engine and the plugin controls it.
LiteSpeed hosting runs a server with a built-in page cache, called LSCache. LiteSpeed documentation states that the plugin lets you set up and manage that server cache from your WordPress admin screen.
Without the plugin, WordPress has no way to tell the server which pages to store, how long to keep them, or when to clear them. The cache engine alone does not know your site rules. That is why the plugin is the missing link, not an optional extra.
What is LiteSpeed hosting, and what does its cache do?
LiteSpeed hosting is hosting that runs on LiteSpeed Web Server or OpenLiteSpeed instead of Apache or NGINX.
A page cache stores a finished HTML copy of a page after WordPress builds it once. LiteSpeed documentation explains that the next visitor gets that stored copy at once, with no fresh PHP run and no fresh database queries.
This matters because WordPress pages do not exist as files. Each visit normally builds the page from PHP code and database rows. A stored copy cuts that work out for repeat visits, which lowers server load and shortens wait time.
How does LiteSpeed Cache differ from a normal cache plugin?
LiteSpeed Cache works at the server level, while most other cache plugins work at the PHP level.
A PHP-level plugin runs inside WordPress, so WordPress still starts up before it can serve a stored page. The WordPress.org plugin page states that LSCache is a server-level cache, so it is faster than PHP-level caches.
A page cache lets the server skip PHP and database queries altogether for a stored page. LiteSpeed notes that its close link to the server also lets it track page links, so it can clear only the pages that changed when you edit a post.
What happens if you install no cache plugin at all?
If you install no cache plugin, your LiteSpeed host still runs WordPress, but it builds every page from scratch on every visit.
WordPress developer docs list caching as the first and easiest step in WordPress optimization, and warn that a site without caching slows down as requests pile up. That warning fits LiteSpeed hosting too, because the server cache needs instructions from a plugin.
You may still get some browser caching from the server, but that only helps repeat visits to the same files in the same browser. It does not store full pages at the server, so new visitors still wait for a full page build.
What does the plugin add besides page caching?
The plugin adds page caching plus a set of speed tools that work on any server, even without LiteSpeed.
The WordPress.org plugin page lists minify for CSS, JavaScript and HTML, lazy loading for images and iframes, database cleaning, object cache support for Memcached and Redis, and browser cache support among its general features.
It also adds automatic purge rules, private cache for logged-in users, separate desktop and mobile cache, REST API caching, and a preload crawler. For the full list of settings and what each one does, see our LiteSpeed Cache settings explained.
| Feature | Needs LiteSpeed server? | What it does |
|---|---|---|
| Automatic page caching | Yes | Stores finished HTML at the server |
| Automatic purge on edit | Yes | Clears pages linked to edited content |
| Private cache for logged-in users | Yes | Stores a separate copy per user session |
| Minify CSS, JavaScript and HTML | No | Shrinks code files before they are sent |
| Lazy loading images | No | Loads images only when they near the screen |
| Object cache support | No | Stores database results in memory |
When is LiteSpeed Cache not enough on its own?
LiteSpeed Cache is not enough when your site needs a CDN, image work done in the cloud, or a separate host cache check.
The plugin connects to QUIC.cloud, LiteSpeed's CDN, which can cache pages at edge nodes near visitors across its network of 77 points of presence, as of November 2026. Our guide to set up LiteSpeed Cache with QUIC.cloud walks through that link step by step.
The plugin is free and open source, as the WordPress.org plugin page states, but some QUIC.cloud services need payment at higher use levels, as of November 2026. Check your QUIC.cloud dashboard before you switch on paid services, so you know what each one costs.
How do you check that caching is working?
You check caching by looking at the response headers for a page, then loading the page twice.
Open a page in a private browser window, open developer tools, and look at the Network tab. The first load should show a cache miss, and the next load of the same page should show a cache hit in the X-LiteSpeed-Cache header.
If you see no such header, the page is not being cached. First confirm that Enable Cache is set to ON under LiteSpeed Cache > Cache, then check that your host has set up the cache root at the server level.
What about WooCommerce, logged-in users and dynamic pages?
WooCommerce pages, logged-in pages and other personal pages need private cache or exclusion, not public cache.
Public cache holds one copy for all visitors, so it must never hold a cart, a checkout page, or an account page. LiteSpeed documentation states that logged-in pages are stored in private cache by IP address and session ID.
The plugin can also punch holes in a cached page with ESI, or Edge Side Includes, so a small part stays live while the rest stays cached. ESI is not available in OpenLiteSpeed, so sites on OpenLiteSpeed need a different plan for cart widgets and other live parts.
How long does LiteSpeed Cache keep a page stored?
LiteSpeed Cache keeps a public page for 604800 seconds by default, which is 1 week.
LiteSpeed documentation lists the default public cache TTL as 604800, the default private cache TTL as 1800 seconds, and the default TTL for 404, 403 and 500 pages as 3600 seconds, or 1 hour.
A longer TTL means fewer rebuilds, but it also means a longer wait before an old copy expires on its own. That is why purge rules matter more than a long TTL: when you edit a post, the plugin should clear that post and its linked archive pages at once.
What do the version and server rules mean for you?
The version and server rules tell you whether the cache features will work on your host at all.
LiteSpeed documentation requires WordPress 6.0 or higher and PHP 7.4 or higher for the plugin, as of November 2026. The WordPress.org plugin page lists the server options as LiteSpeed Web Server Enterprise with the LSCache module (v5.0.10 or higher), OpenLiteSpeed (v1.4.17 or higher), LiteSpeed WebADC (v2.0 or higher), or QUIC.cloud CDN.
If your host runs Apache or NGINX with no LiteSpeed product and no QUIC.cloud, the cache features will not work.
You can still use the plugin for minify, lazy loading and image work. For a different page cache, read our guide on WP Rocket versus host caching.
How does browser caching fit in?
Browser caching stores static files on the visitor's device, so repeat visits skip downloading them again.
web.dev calls the browser HTTP cache the first line of defence against needless network requests, and notes that it works in all browsers. For versioned files, it recommends Cache-Control: max-age=31536000, which is 1 year.
LiteSpeed Cache sets a browser cache TTL of 31557600 seconds, or 1 year, as its recommended value. That setting covers images, CSS and JavaScript files, while page cache covers the HTML itself, so the two layers work together rather than replacing each other.
What mistakes should you avoid?
Do not stack a second page cache plugin on top of LiteSpeed Cache, and do not cache pages that must stay personal.
Two page cache plugins can fight over the same pages, purge each other's copies, and make faults hard to trace. Pick one page cache and switch the other one off.
- Cache the login page only if you have a clear reason, since it defaults to
OFFas of plugin version 7.9. - Do not set a very long TTL and then forget purge rules, or visitors will see old content for days.
- Do not cache cart, checkout and account pages as public pages.
- Do not judge speed from one load, since the first load is a cache miss and the second load is the cached result.
- Do not skip the header check above, since a plugin that is installed but not caching looks the same as one that works.
For a wider speed plan beyond caching, see our guide on how to speed up WordPress.
Frequently asked questions
Is LiteSpeed Cache free on LiteSpeed hosting?
Yes, the LiteSpeed Cache plugin is free and open source. The cache features need a LiteSpeed server, OpenLiteSpeed, LiteSpeed WebADC or QUIC.cloud CDN. Some QUIC.cloud services, such as image work and CDN use above free levels, can need payment, so check the QUIC.cloud dashboard for current costs before you switch them on.
Can I use WP Rocket instead of LiteSpeed Cache on LiteSpeed hosting?
You can install WP Rocket, but it runs at the PHP level while LiteSpeed Cache runs at the server level, so LiteSpeed Cache can serve stored pages without starting WordPress. Running both page caches at once is a bad idea, since they can clash over purging and storage. Pick one page cache and use the other plugin only if its page cache is off.
Why do visitors still see an old page after I edit it?
Visitors see an old page when the edited page or its linked archive pages were not purged. Check the auto purge rules under LiteSpeed Cache, Cache, Purge, and make sure the right archive types are selected. You can also purge a single URL by hand. If the page still looks old, clear your browser cache and check again in a private window.
Should I cache pages for logged-in users?
You can cache pages for logged-in users, but only in private cache, never in public cache. Private cache stores a separate copy per user session, so one user never sees another user's account page. Leave cart, checkout and account pages out of public cache, and use ESI or exclusion rules for parts of a page that must stay live for each visitor.
Does LiteSpeed Cache work on OpenLiteSpeed?
Yes, LiteSpeed Cache works on OpenLiteSpeed, which is the free open-source edition of LiteSpeed Web Server. Most cache features work there, but ESI is not available in OpenLiteSpeed, so dynamic page parts need another setup. Some setting changes that edit the htaccess file also need a server restart on OpenLiteSpeed.
Sources
- LiteSpeed Cache for WordPress overview LiteSpeed Documentation
- Cache settings screen by screen LiteSpeed Documentation
- LiteSpeed Cache plugin page WordPress.org
- Prevent unnecessary network requests with the HTTP Cache web.dev
- Optimization WordPress Developer Resources
- QUIC.cloud – Accelerate, Optimize, Protect your WordPress QUIC.cloud
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
