LiteSpeed Cache for WordPress

LiteSpeed Cache is the page cache that fits our shared WordPress stack with cPanel and LiteSpeed. It stores full HTML for logged-out visitors so those pages can be served without running PHP on every request. Logged-in users, carts, and checkout should miss the cache on purpose. You should run only this page-cache plugin, purge after you publish, and confirm behavior with the X-LiteSpeed-Cache response header.

curl -sI https://example.com | grep -i x-litespeed-cache

When you are logged out, the second request should show a hit. The first request may miss while the cache fills. No header usually means the plugin is off, the request is bypassed, or the site is not on LiteSpeed. A guest session cookie or a page builder that treats every visitor as unique can keep every response at miss. Test logged out with curl, not from a browser that still holds a cart or admin cookie.

What should hit and what should miss

Anonymous homepage and product pages should hit after the cache is warm. Paths such as cart, checkout, and wp-admin should miss, and so should any logged-in session. If the homepage never hits, inspect Set-Cookie on that first response. A plugin that starts a session for every guest can poison the cache. If cart pages hit, turn that behavior off right away so one shopper never sees another shopper’s cart.

Keep a single page-cache owner

Running LSCache beside another full-page cache or a CDN HTML cache often creates a purge fight. The home page stays cold or serves stale HTML. One page-cache owner is enough, and purge on publish covers normal edits. The optional crawler can warm URLs, but keep it polite. A greedy crawl with a very short TTL can stampede PHP workers for no real gain.

How it fits with the rest of the stack

On our WordPress hosting, LiteSpeed Cache is the intended page cache. Object cache with Redis is a separate layer, and browser cache is Cache-Control on static files. Those layers stack; they do not replace LSCache, and LSCache does not replace them. After a theme or plugin update, purge once and check with curl again. A leftover logged-in cookie from wp-admin in the same browser will make homepage requests miss, which is why curl is the reliable check. For WooCommerce, set exclusions in LSCache’s cache settings rather than adding a second plugin that claims to detect ecommerce on its own.