LSCache keeps serving stale content
Purge rules that never fire for your product pages, an ESI block that silently caches logged-in output, or a CDN layer holding onto pages the origin already dropped.
Purges tied to the right events
Working with LiteSpeed?
Most LiteSpeed sites that reach us were set up by a hosting onboarding wizard and then left alone. LSCache does its job until the day it serves a stale price, purges everything on every post save, or the shared hosting worker limit kicks in on a Monday morning.
What it is
LiteSpeed Web Server comes from LiteSpeed Technologies, a company founded in 2003. It is a commercial, Apache-compatible web server built around an event-driven architecture, which is often faster than Apache on PHP and WordPress workloads while still honouring the .htaccess files your application already ships with.
OpenLiteSpeed is the open-source variant of the same engine, and the LSCache plugin ships for WordPress, WooCommerce, Magento, Prestashop, Drupal, OpenCart and XenForo. According to W3Techs it runs on roughly 13% of all websites, almost entirely through shared hosting brands such as HostGator, Namecheap EasyWP and A2. SiteGround, for comparison, uses nginx instead.
The honest version
No technology is all upside. This is where LiteSpeed earns its place and where it tends to cause trouble.
Sound familiar?
The LiteSpeed problems that bring people to us, and what you have once each one is fixed.
Purge rules that never fire for your product pages, an ESI block that silently caches logged-in output, or a CDN layer holding onto pages the origin already dropped.
Purges tied to the right events
Workers hitting the licence limit, PHP children running out of memory, or a traffic spike colliding with a cache that was never warmed.
Workers sized and cache primed
Free-tier credits run out, new uploads stop being compressed, and critical CSS generation quietly fails for every new page.
Quota and plan matched to volume
Security plugin rules, a redirection plugin, and the LSCache block all writing to the same .htaccess file in the wrong order.
One source of truth for rewrites
OpenLiteSpeed's WebAdmin is reachable from the public internet on its default port, with default credentials still in place.
Admin locked to your network
A support ticket asking to flip between LiteSpeed and Apache, which quietly invalidates the plugin configuration your site depends on.
Swap rehearsed before it happens
What we do
Call us for one stale cache, or hand us the whole server.
How it works
Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.
We fix the cause, not the symptom. If something is down, getting it back up comes first.
Backups, monitoring, updates and access, so the same problem can't quietly come back.
You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.
Often found together
We work on the whole stack, so the problem can be wherever it actually is.
Usually the purge hooks for your plugin are not wired up, so a price or stock change updates the database but never tells LSCache to drop the cached HTML. ESI blocks that were enabled for logged-in users can also hold onto fragments longer than intended, and QUIC.cloud CDN adds another layer that may still be serving the old copy.
The most common reason is hitting the worker limit on your licence or VPS plan, which turns every new visitor into a 503. PHP memory exhaustion and a cold cache after a flush can produce the same symptoms, and the fix depends on which one is actually firing.
Only if the licence cost or the tuning overhead no longer makes sense. For a well-configured WordPress or WooCommerce site LiteSpeed is genuinely fast. For a bespoke application with complex caching needs, nginx in front of PHP-FPM is often easier to reason about.
Guest mode off, cart and checkout excluded from caching, ESI blocks enabled for the mini-cart, object cache pointed at Redis, and purge hooks tied to stock and order status changes. The defaults do not do any of this by themselves.
Yes. We read the current LSCache settings, the .htaccess rules and the QUIC.cloud account, document what is actually happening, and then change it to match how your site is really used.
Estimates are free. Tell us what's going wrong and you get a price before any work begins.
Free estimate
Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.
Your message is with a real person, and we'll get back to you soon.
Rather talk now? Call us: