Performance Reference
LiteSpeed: what the server does that a plugin cannot
You have used four caching plugins and none of them could answer a request without booting WordPress first.
The short answer
LiteSpeed is an event-driven web server that reads Apache configuration as written and holds its page cache inside the server itself, above PHP rather than inside it.
That placement is the whole argument. A cached response is returned before the PHP interpreter is invoked, so a hit costs roughly what serving a static file costs. No plugin can reach that position, because by the time a plugin runs, WordPress has already booted and the expensive part has already happened.
By the HostingFast team · Reviewed 12 August 2026
0
Hand-waving in this entry
100+
Entries wired to each other
Real
Numbers you can reproduce
Free
To read, no gate
The pairing is what you actually operate. LiteSpeed provides the cache engine; the LiteSpeed Cache plugin is the control surface for it on WordPress, handling page caching, ESI, image optimisation and HTTP/3 as one configured set rather than four plugins negotiating with each other.
Compatibility is the other half of the design. Your .htaccess rules, rewrites and the bulk of your Apache configuration transfer without an edit, which means two decades of accumulated Apache documentation remains valid here. That is not a small thing when you are migrating a site somebody else built.
Where the cache sits changes the arithmetic
A PHP caching plugin can only save you the work that happens after WordPress has loaded — and loading WordPress is a substantial share of the cost. A server-level cache answers before any of that begins. The gap between the two shows up most clearly in uncached-versus-cached response time on the same page.
It also changes what a traffic spike does to you. Requests answered above PHP never touch the worker pool, so ten thousand arrivals for the same article cost roughly what one costs plus the bandwidth.
ESI: keeping one fragment alive on a cached page
The usual objection to full-page caching is that something on the page must stay dynamic — a basket total, a greeting, a stock count. ESI answers it by punching a hole: the page is cached whole, and the named fragment is assembled per request while everything around it is served from the cache.
That is the difference between excluding an entire template from caching and excluding a single element of it. Shops in particular tend to disable caching across whole sections when three ESI blocks would have kept the rest of it fast.
Confirming it is actually hitting
Request the page and read the response header. x-litespeed-cache: hit means the server answered it directly; miss means the request went through to PHP. Test logged out, because an admin session is excluded by design and will show you a miss on a perfectly healthy site.
If the header is absent entirely, the cache module is not engaged for that hostname and no amount of plugin configuration will change it. That is a support question, and it is a short one.
What you get here without buying up
LiteSpeed caching is built into the server on every tier here, entry plan included, and the LSCache plugin ships with the WordPress plans rather than being pointed at in a guide. Per-site PHP version switching sits in the same panel, so an older application and a current one can share an account without either being held back.
Neighbouring entries: Cache, Apache, Nginx and WordPress. Free migration moves an existing site across, normally within a day, and it keeps serving visitors throughout.
Performance entries with the measurement attached
Nothing here asks you to take a speed claim on trust. Each entry names the header, the command or the panel screen that shows you the current state of your own site.
LiteSpeed caching sits in the web server on every tier, and per-site PHP switching is a dropdown rather than a support ticket.
- Headers and panel screens named
- Server behaviour, not plugin behaviour
- Cross-linked to neighbouring terms
- Written by our support engineers
Why HostingFast
Standard on every plan
Cache above PHP
A hit is answered before the interpreter starts, which is a position no plugin can occupy.
Spikes stop costing workers
Requests served above PHP never touch the worker pool, so a viral article costs bandwidth and little else.
ESI instead of exclusions
Punch a hole for the basket total rather than excluding the whole template from caching.
Apache config comes with you
Rewrites and .htaccess rules transfer as written, so a migrated site keeps its behaviour.
One header to verify
x-litespeed-cache: hit, read while logged out, is the entire diagnostic.
Included, not an upgrade
In the server on every tier, with the LSCache plugin shipped on the WordPress plans.
Quick Start
From order to online
- 1
Check the header logged out
An admin session is excluded from the cache by design, so testing while signed in will show a miss on a perfectly healthy site.
- 2
Replace exclusions with ESI
Find every template excluded from caching for the sake of one dynamic element, and put that element in an ESI block instead.
- 3
Compare cached against uncached
Time the same page hit and missed. That gap is what the server-level cache is actually worth on your site.
Built In
Loaded onto every plan
- SSH, Git and Composer on the developer-focused plans
- Per-site PHP version switching from the control panel
- DDoS filtering absorbed out at the network edge
- WordPress Toolkit, with updates handled for you
- WordPress and 400+ other applications installed in one click
- Human support on duty every hour of every day
- In-place account upgrades — no migration when you change plan
- Spam and virus screening on every mailbox as standard
- A renewal price identical to the price you signed up at
- Zero setup charges — there is no joining fee, ever
Frequently Asked
What people ask us most often
Why is a server-level cache faster than a caching plugin?
Position. A plugin can only start work once WordPress has loaded, and loading WordPress is a large share of what an uncached request costs. LiteSpeed answers a cache hit before PHP is invoked at all, so the response costs roughly what a static file costs. Both approaches cache the same HTML; only one of them avoids the expensive part.
How do I keep a basket total live on a cached page?
With ESI. The page is cached in full and the named fragment is assembled per request, so the basket updates while the surrounding layout is still served from cache. The alternative most sites reach for — excluding the whole template — throws away the caching on every element that never needed excluding.
Will the .htaccess rules from my old host still work?
That compatibility is a design goal rather than a happy accident. Rewrites, redirects and the bulk of your Apache configuration are read as written, which is why a migrated site behaves the same on arrival. If a rule does misbehave, send it to support with the URL it applies to and it gets sorted quickly.
Do I have to install the cache plugin myself?
The LiteSpeed Cache plugin ships with the WordPress plans, because it is the control surface for the cache engine in the server and no general-purpose caching plugin can reach that engine. On other applications the server cache still works; the plugin is the WordPress-specific way of steering it.
Keep reading
WordPress
The platform behind a large share of the web, and what it costs per uncached request.
Nginx
The other event-driven server, and where the two differ once configuration is involved.
Best LiteSpeed Hosting
The buyer's version: what to verify about a LiteSpeed platform before you sign.
Domain Names
Find, register and transfer names, with the first year free alongside annual hosting.
OpenCart Hosting
One-click OpenCart on storefront-tuned PHP, with free SSL and staging included.
Changing hosts? Run through our checklist first.
A straightforward sequence for a switch your visitors never feel: which files move first, how to shift email across without losing a single message, the right moment to repoint DNS, and the two mistakes behind almost all the downtime we get asked to rescue.
Answer the request before PHP wakes.
LiteSpeed caching in the server on every tier, NVMe storage underneath, free SSL and free migration.
View Domain Names plans