Toolchain Check
LSCache is a plugin; LiteSpeed is the reason it works
You have seen the caching combination that keeps finishing first in independent tests, and the thing worth understanding before you buy is which half of it does the work.
The short answer
Hosting served by LiteSpeed with LSCache already configured — Turbo WordPress at $5.59 a month — because the pairing is what produces the result and neither half achieves much alone.
This is a difference of architecture, not a difference of degree. Server-level caching returns the finished page before WordPress has started up at all. A plugin cache running on another web server can only approximate that from several steps further back in the request, because PHP has to boot before it can answer.
By the HostingFast team · Reviewed 15 August 2026
Free
Migration in, at no cost
24/7
Humans answering, any hour
Daily
Backups, every day
$0
Setup fees
Caching arguments usually turn into plugin arguments, which is why they never resolve. The interesting distinction is not between two plugins, it is between two places a cache can live: inside the web server, or inside the application the web server is trying to avoid starting.
Once you frame it that way, the measurement is obvious and takes about a minute. Everything below is how to run it and what to read from the result.
Prove a cache hit from the response headers
Request a page twice in a private window and read the headers on the second request. A served-from-cache response returns x-litespeed-cache: hit. A miss says so plainly, and its absence altogether means nothing at the server level is caching anything.
curl -sI against the URL prints the headers without loading the page, which makes this a one-line check you can run against any site, including a prospective host's own customers.
Then compare time to first byte on the hit against the miss. The gap between those two figures is the entire value of server-level caching, expressed in milliseconds on your own site rather than in somebody's benchmark.
The trap: the plugin without the server
Installing the LiteSpeed Cache plugin onto a server with no LiteSpeed underneath is the classic version of cargo-cult optimisation. The plugin installs, the settings pages appear, some of the optimisation features work, and the caching that produced the benchmark scores does not exist at all.
The header check catches it immediately: no x-litespeed-cache header means no server-level cache, whatever the plugin's dashboard is reporting.
The mirror-image mistake is running a second page-caching plugin alongside LSCache on a genuine LiteSpeed server. Two caches fighting over the same pages produces stale content and inconsistent results, and troubleshooting it wastes an afternoon.
What comes with the server beyond caching
HTTP/3 support arrives with the web server rather than as a separate purchase, and it is worth confirming in the browser's network panel: add the protocol column and reload.
The LSCache plugin ships with sensible defaults already applied on our WordPress plans, so the cache is working from the first login rather than waiting on configuration homework. Image optimisation and critical CSS generation sit inside it as optional extras when you want to tune further.
The server-level cache also pairs properly with Redis object caching, which covers the logged-in requests the page cache is not allowed to serve. Together they cover both halves of a WordPress site.
Check that it is available across the range
Some providers wall the LiteSpeed advantage inside a premium tier. Here NVMe storage behind a LiteSpeed cache is the standard build on every plan, from Sprint at $2.42 upward, with the WordPress tiers adding LSCache preconfigured.
Test us the way you would test the claim anywhere: run the header check on a site we host, compare renewal against order price, and look up the company — HostingFast is a trading name of Vitalcare at Home Ltd, registered in England and Wales. Migration is free and normally within 24 hours.
One header, one answer
Caching claims are hard to argue about and trivial to check. A single response header settles whether a platform is doing what its marketing says, which is why this page leads with it.
Every plan ships with a free SSL certificate that renews itself ahead of expiry — the padlock is never something you have to remember.
- x-litespeed-cache read straight from the headers
- Hit and miss timings compared on your own URL
- LSCache preconfigured on the WordPress tiers
- Renewal charged at the order rate
Why HostingFast
Standard on every plan
Caching inside the web server
A hit is returned before WordPress boots, which is where the saved milliseconds come from — not from a plugin doing it afterwards.
LSCache configured on arrival
Sensible defaults already applied on our WordPress plans, so the cache works from the first login rather than after a weekend of tuning.
Turbo WordPress, specified
$5.59 a month for 2 cores and 4 GB, 20 GB of NVMe, 25 sites and a 400k monthly visit allowance.
HTTP/3 with the server
The modern protocol stack comes along with LiteSpeed, and the browser's network panel will confirm it per request.
Redis for the other half
Object caching covers logged-in and dynamic requests, which page caching is deliberately not allowed to serve.
Standard across the range
NVMe behind a LiteSpeed cache on every plan rather than walled off inside a premium tier.
Prices Side by Side
Our numbers next to the big names
Typical intro and renewal pricing across the market, lined up against ours — including the renewal figure most comparison charts skip.
| Feature | HostingFastMost popular | Typical household-name host | Typical bargain host | Typical loss-leader deal |
|---|---|---|---|---|
| Starting price / mo* | $2.42/mo | $4–$6 | $2–$4 | $1–$3 |
| Renewal price / mo | $2.42/mo | $10–$15 | $8–$12 | $4–$6 |
| Cheapest plan renews at its sign-up price | ||||
| SSL as standard | ||||
| Migration done for you | ||||
| NVMe drives on the cheapest tier | ||||
| Daily backups from the first tier | ||||
| Real humans on support, 24/7 |
*Our number is the lowest-priced plan we sell on an annual term, pulled live from the same catalogue that powers our pricing page — it physically cannot fall out of date. The other three columns show the ranges shared hosts in each bracket typically advertise: introductory offers that mostly demand a one-to-four-year commitment, then jump once it expires. We no longer name rivals or print their prices, because a figure we cannot verify on the day you read it has no business on this page. Line us up against whichever host you are really weighing — and give the renewal row the hardest look.
Quick Start
From order to online
- 1
Run curl -sI against the page twice
Read x-litespeed-cache on the second request. Hit means the server answered; no header at all means nothing is caching at the server level.
- 2
Compare hit and miss timings
Time to first byte on a cache hit against a deliberate miss. That gap is the value of server-level caching, measured on your own URL.
- 3
Remove the second caching plugin
On a genuine LiteSpeed server, LSCache alone is the correct configuration. Two page caches fighting produces stale pages and an afternoon of confusion.
Built In
Loaded onto every plan
- LiteSpeed serving requests, with the cache inside the web server
- A readable x-litespeed-cache response header so hits are verifiable
- LSCache preconfigured with sensible defaults on the WordPress plans
- HTTP/3 and the modern protocol stack supplied by the server
- Redis object caching for the logged-in half of the site
- NVMe SSD storage behind the cache on every tier
- Server-level caching available across the range, not walled into a premium plan
- Image optimisation and critical CSS available inside LSCache when you want them
- Daily backups with self-service restores from the panel
- Free migration from your current host, usually within 24 hours
Frequently Asked
What people ask us most often
How do I prove a page was served from the LiteSpeed cache?
Run curl -sI against the URL, or open the response headers in your browser's network panel on a second request. A served-from-cache response returns x-litespeed-cache: hit. A miss says so. No such header at all means nothing is caching at the server level, whatever a plugin dashboard is reporting.
What happens if I install LSCache without LiteSpeed underneath?
Some optimisation features still work and the caching that produces the benchmark results does not exist. The plugin cannot create a server-level cache on a server that has none, so pages continue to boot WordPress on every request. The header check catches it in about ten seconds.
Can I run another caching plugin alongside LSCache?
You should not. On a genuine LiteSpeed server, LSCache alone is the correct configuration, and a second page cache fighting over the same URLs produces stale content and results that change between reloads. Object caching with Redis is the complement you actually want, because it covers a different layer.
Where does server-level caching stop helping?
At the logged-in boundary. Cart, checkout, account pages and wp-admin are excluded by design, because every one of them is unique to a session. That half is what Redis object caching and CPU allocation are for, which is why the two layers are specified together rather than treated as alternatives.
Keep reading
Hosting for Portfolios With Booking
A portfolio that also has to fill a diary, judged on booking flow and image weight.
Game Server VPS
Tick rate and memory per player, sized the way this page sizes a cache — from measurement.
LiteSpeed (Glossary)
The definition in full, with the difference between a server cache and a plugin cache made explicit.
WordPress Hosting
Managed WordPress with LSCache preconfigured and Redis behind it for the logged-in half.
Secure Hosting
Imunify360 and isolated accounts, for sites where hardening matters as much as the cache does.
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 before WordPress wakes up.
LiteSpeed on every plan with LSCache preconfigured, Redis for the rest, free migration and a flat renewal figure.
View WordPress Hosting plans