Working with LiteSpeed?

LiteSpeed caching the wrong thing? We fix it.

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.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

lsws_error.log

still failing

What it is

LiteSpeed at a glance

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.

Type
Web server
First released
2003
License
Commercial for LiteSpeed Enterprise; GPLv3 for OpenLiteSpeed
Maintained by
LiteSpeed Technologies
Typically used for
Shared and VPS WordPress hosting, high-traffic PHP sites, drop-in Apache replacement with page caching

The honest version

LiteSpeed pros and cons

No technology is all upside. This is where LiteSpeed earns its place and where it tends to cause trouble.

Where LiteSpeed is strong

  • Drops in where Apache wasIt reads the same .htaccess files Apache does, so most PHP applications move across without any rewrite work on your part.
  • Page caching is built inLSCache runs inside the server itself, with official plugins for WordPress, WooCommerce, Magento, Prestashop, OpenCart and others handling the purge logic.
  • HTTP/3 and QUIC out of the boxModern transport protocols are available without a separate proxy or load balancer, which matters on mobile connections with high packet loss.
  • Lighter on memory than ApacheThe event-driven worker model keeps RAM use down on busy sites, which is the usual reason shared hosts choose it in the first place.
  • OpenLiteSpeed is freeThe open-source branch is genuinely free to use, so you can run the same engine on your own VPS without a commercial licence.
  • QUIC.cloud and image optimisationAn integrated CDN handles image compression, WebP conversion and critical CSS generation without needing a separate service account.

Where LiteSpeed bites

  • The licence is commercialLiteSpeed Enterprise is proprietary and priced per worker count or per server, and only OpenLiteSpeed is free to run at any scale.
  • LSCache misfires in ways that are hard to seeThe plugin can purge the entire cache on every post save, serve stale pages after a price change, or silently break ESI fragments on logged-in users.
  • QUIC.cloud quotas surprise peopleImage optimisation and critical CSS use credits that quietly run out mid-month, after which features stop working with no obvious error on the site.
  • cPanel pins the versionOn cPanel servers the LiteSpeed install is tied to a specific build chosen by your host, and you cannot upgrade or downgrade independently.
  • Tuning the plugin takes real timeThe default LSCache settings suit a brochure site, and getting WooCommerce or a membership plugin right means working through dozens of toggles.
  • Debugging is harder than a reverse proxyWith nginx sitting in front of PHP you can watch the proxy layer separately, whereas LiteSpeed and its cache are one process and one set of logs.

Sound familiar?

Common LiteSpeed problems we fix

The LiteSpeed problems that bring people to us, and what you have once each one is fixed.

stale cached page served after price change

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

503 Service Unavailable

The server crashes under load

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

QUIC.cloud credits exhausted

Image optimisation stopped mid-month

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

.htaccess conflicts with lscache rewrite rules

Rewrites are fighting each other

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

WebAdmin on port 7080 open

The admin console is exposed

OpenLiteSpeed's WebAdmin is reachable from the public internet on its default port, with default credentials still in place.

Admin locked to your network

cPanel swap pending

The host wants to switch servers on you

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

LiteSpeed help, from rescue to upkeep

Call us for one stale cache, or hand us the whole server.

Rescue
Workers crashing, cache serving the wrong page, or a WooCommerce checkout that bypasses purge. We get it serving correctly first.
LSCache tuning
Purge rules, ESI blocks, guest mode and object cache settings worked through for WooCommerce, membership and multilingual sites.
QUIC.cloud setup
Image optimisation, critical CSS and CDN quotas configured against your real traffic, not the demo defaults.
Migrations
Moving between LiteSpeed hosts, swapping to nginx or Apache, or finishing a move somebody else started.
Security
Locking down the WebAdmin console, reviewing mod_security rules that block the REST API, and hardening the shared hosting account.
Managed Tech
Monitoring, updates and a team to call, on an ongoing basis.

How it works

From first message to fixed

  1. Look Free estimate

    Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.

  2. Fix

    We fix the cause, not the symptom. If something is down, getting it back up comes first.

  3. Harden

    Backups, monitoring, updates and access, so the same problem can't quietly come back.

  4. Hand back or stay on

    You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.

Often found together

Running LiteSpeed alongside something else?

We work on the whole stack, so the problem can be wherever it actually is.

Questions

LiteSpeed questions

Something else? Call+1 737 727 7327

Why is our LiteSpeed Cache serving stale content?

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.

Why does our LiteSpeed server crash under load?

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.

Should we switch from LiteSpeed to nginx or Apache?

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.

How do we configure LiteSpeed Cache properly for WooCommerce?

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.

Can you take over LiteSpeed configuration from a previous developer?

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.

How much does LiteSpeed help cost?

Estimates are free. Tell us what's going wrong and you get a price before any work begins.

Free estimate

LiteSpeed giving you trouble?

Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.

  • No charge to find out what it will take
  • If it's urgent, say so

Replies come from a person. By sending, you authorize us to email you back. No marketing.