If your cPanel account runs on LiteSpeed (most SkyServer shared and reseller plans do), you have access to a caching layer that's a level above a typical WordPress caching plugin. It's called LSCache, and it caches pages at the web server itself rather than inside PHP — which means a cached page can be served without WordPress, PHP, or MySQL waking up at all. Set up wrong, though, it either does nothing or breaks your cart. Here's how to get it right.
What Makes LSCache Different From a Regular Caching Plugin
Plugins like WP Super Cache or W3 Total Cache still run through PHP to decide whether to serve a cached page. LSCache skips that step. The LiteSpeed web server itself intercepts the request and, if a valid cached copy exists, returns it directly — PHP never loads. That's why LSCache-cached pages are usually noticeably faster than plugin-only caching, especially under load.
The catch is that LSCache only works if two pieces are in place together: the LiteSpeed web server (server-side, which SkyServer already runs on compatible plans) and the free LiteSpeed Cache plugin (site-side, which talks to the server and handles cache rules, exclusions, and purging). Install the plugin without server-side LiteSpeed and it just falls back to being a slower, PHP-based cache — that's usually the first thing to check when someone says "I installed LSCache and nothing changed."
Symptom: The Plugin Is Active but Pages Still Feel Slow
This is the most common support ticket. You've installed LiteSpeed Cache, activated it, maybe even seen a "cache is working" message — but page load times haven't moved, or worse, the site behaves oddly for logged-in users or during checkout. A few things are usually going on:
- The hosting account isn't actually on a LiteSpeed web server, so the plugin has nothing to talk to.
- Caching is enabled but the TTL (time-to-live) is so short it's barely caching anything.
- A security plugin or another caching plugin is fighting with LSCache for control of the response headers.
- Every page looks "not cached" because you're testing while logged into wp-admin, and logged-in users are excluded from cache by design.
Test cache status properly: open the page in an incognito window (logged out), view the page source, and search for X-LiteSpeed-Cache in the response headers using your browser's Network tab. A value of hit means it's serving from cache; miss means it just built the page fresh and cached it for next time.
Step-by-Step: Installing and Configuring LSCache
- Confirm LiteSpeed is running. In cPanel, check under Software for a "LiteSpeed Web Cache Manager" icon. If it's there, you're on LiteSpeed and can proceed.
- Install the plugin. From wp-admin, go to Plugins > Add New, search "LiteSpeed Cache," and install the one published by LiteSpeed Technologies. Activate it.
- Run the Quick Start wizard. Under LiteSpeed Cache > Dashboard, the plugin offers a guided setup that picks reasonable defaults for caching, CSS/JS optimization, and image handling — start there rather than the raw settings pages if you're not sure what each toggle does.
- Set your cache TTL. Under Cache > TTL, set "Default Public Cache TTL" to something reasonable — 604800 seconds (a week) works for most content sites. Pages purge automatically on publish/update regardless of TTL, so a long TTL is safe.
- Enable Object Cache if available. Under Cache > Object, if your hosting provides Redis or Memcached, LSCache can use it for database query caching on top of the page cache. Check with SkyServer support whether your plan includes this.
- Turn off any competing cache plugin. Running WP Rocket or W3 Total Cache alongside LSCache causes duplicate, conflicting cache headers and unpredictable behavior. Pick one.
Excluding WooCommerce Cart, Checkout, and Logged-In Pages
This is where most LSCache misconfigurations bite people running a store. If the cart page gets cached, every visitor sees whatever was in the first visitor's cart. The plugin auto-detects WooCommerce in most cases, but it's worth verifying manually:
- Go to LiteSpeed Cache > Cache > Excludes and confirm the Cart, Checkout, and My Account URLs are listed under "Do Not Cache URIs."
- Under Cache > ESI (Edge Side Includes), enable ESI for the cart/mini-cart widget if your theme supports it — this lets the rest of the page stay cached while the cart count updates dynamically per visitor.
- Confirm "Private Cache for Commenters" and logged-in user exclusions are on, so account pages and order history never get served to the wrong person.
If you're not using WooCommerce but have a membership site, forum, or anything with per-user content, apply the same logic — exclude those URL patterns explicitly rather than trusting auto-detection.
Common LSCache Issues and Fixes
| Symptom | Likely Cause | Fix |
|---|---|---|
| Changes to a page don't show up after publishing | Stale cache didn't purge, or a CDN in front of the site is caching separately | Use LiteSpeed Cache > Toolbox > Purge All; if using Cloudflare, purge its cache too |
| Logged-in users see cached content meant for logged-out visitors | Private cache misconfigured or theme not sending proper no-cache headers on dynamic elements | Enable "Cache Logged-in Users" only if you understand the ESI implications, otherwise leave it off |
| White screen or 500 error right after enabling LSCache | Conflicting .htaccess rules from a previous cache plugin | Deactivate the old plugin fully, then regenerate .htaccess from LSCache's Toolbox |
| Cart total resets or shows wrong items | Cart/checkout pages are being cached | Add exact cart and checkout URLs under Cache Excludes |
| Site is fast for you, slow for others | You're testing while logged in, which always bypasses cache | Test in a private/incognito window, not your admin session |
Prevention: Keep the Cache Healthy Long-Term
A cache that works today can quietly stop helping a month from now if it isn't maintained. A few habits keep it reliable:
- After any theme or plugin update, do a manual "Purge All" once — some updates change markup in ways the automatic purge logic doesn't catch.
- Re-run the Quick Start wizard after major WordPress core updates; LiteSpeed occasionally ships new optimization options that aren't enabled by default for existing installs.
- Check the crawler feature (Crawler > General) if you have a large site — it can pre-warm the cache for your most important pages on a schedule so the first visitor after a purge doesn't hit a slow "cache miss."
- Keep only one caching layer active. Stacking LSCache with a plugin-based cache or an aggressive CDN cache without coordinating TTLs is the single most common cause of "my changes aren't showing up" tickets.
If your account isn't on LiteSpeed and you'd like to be, that's a hosting plan question — SkyServer support can confirm which plans include it before you spend time chasing a plugin that has nothing to connect to.
Frequently Asked Questions
Do I need to buy anything extra to use LSCache?
No. The LiteSpeed Cache plugin is free, and if your hosting account runs on a LiteSpeed web server, server-side caching is included. You only pay for LiteSpeed Enterprise if you're managing your own VPS or dedicated server outside a plan that already includes it.
Can I use LSCache and Cloudflare together?
Yes, and it's a common combination — Cloudflare caches at the network edge, LSCache caches at the server. Just make sure a "Purge All" in WordPress is followed by a Cloudflare cache purge too, otherwise Cloudflare can keep serving an old version even after your origin cache is fresh.
Why does my staging site show cached content from production?
Usually because the staging copy was cloned with the cache plugin's settings intact, including old cached files in the same directory structure. After cloning a site, always run Toolbox > Purge All on the new copy and confirm the domain in LSCache's settings matches the staging URL, not the live one.
Will LSCache conflict with a security plugin like Wordfence?
Generally no — they operate at different layers. The one thing to check is whether your security plugin rewrites .htaccess rules on its own schedule, which can occasionally strip out the LSCache rule block. If pages stop caching after a security plugin update, regenerate the .htaccess from LiteSpeed Cache > Toolbox.
How do I know if my SkyServer plan includes LiteSpeed?
Look for "LiteSpeed Web Cache Manager" in your cPanel's Software section. If it's not there, reach out to SkyServer support — LiteSpeed availability depends on the specific hosting plan and server.
