Mini
One site, properly served
—
- 15 GB NVMe storage
- 1 website
- 10 subdomains · 5 MySQL databases
- 10 branded mailboxes
- 5 MB/s I/O · 512 IOPS
- 100,000 files · 1 CPU core · 1 GB RAM
- Unlimited bandwidth
- Free domain on the 3-year term
Enterprise not OpenLiteSpeed with the label swapped
A web server that does not rebuild the page
Cached responses never reach PHP at all. On a database-driven site that is the difference between a page assembled on demand and one already sitting in memory.
See the plans → Coming from another host?
8x
Typical gain on
a cached page
a cached page
14days
Money back,
conditions apply
conditions apply
24/7
Real engineers,
not a queue
not a queue
Starter Lite
A site under real load
—
- 25 GB NVMe storage
- 5 websites
- 25 subdomains · 15 MySQL databases
- 30 branded mailboxes
- 10 MB/s I/O · 1,024 IOPS
- 250,000 files · 1 CPU core · 1 GB RAM
- Unlimited bandwidth
- Free domain on the 3-year term
Starlight
Two or three, or one busy one
—
- 40 GB NVMe storage
- 10 websites
- 50 subdomains · 30 MySQL databases
- 60 branded mailboxes
- 20 MB/s I/O · 2,048 IOPS
- 400,000 files · 2 CPU cores · 2 GB RAM
- Unlimited bandwidth
- Free domain on the 3-year term
On every plan not a tier above, not an add-on
LiteSpeed Enterprise
LSCache for WordPress
HTTP/3 and QUIC
Brotli and gzip
.htaccess read natively
ESI for partial caching
Image optimisation via LSCache
Crawler to keep cache warm
Where it runs
15 cities, because cache cannot beat distance
A cached page still has to travel. Put the site near its readers and the two savings compound.
America 4
New York
USA
Los Angeles
USA
Miami
USA
Montreal
Canada
Europe 6
London
United Kingdom
Frankfurt
Germany
Amsterdam
Netherlands
Roubaix
France
Zurich
Switzerland
Helsinki
Finland
Asia 5
Mumbai
India
Singapore
Singapore
Tokyo
Japan
Hong Kong
Hong Kong
Sydney
Australia
Caching removes the time spent building a page. It does nothing about the time spent travelling. A page served from memory in Frankfurt still takes 250ms to reach Sydney, and no server software fixes that — only a shorter distance does.
Who asks for it
Four situations where the web server is the bottleneck
If your site is quiet, any web server will do. These are the four where the choice starts to show.
A WordPress site with traffic
Every uncached request is PHP plus a dozen queries. LSCache serves the cached copy from the server itself, so PHP is never called — not called and returning quickly, but not called.
A shop, where half the page cannot be cached
ESI caches the parts that are the same for everybody and leaves the basket alone. Most caching is all-or-nothing; this is the reason to care.
Anyone whose rules live in .htaccess
LiteSpeed Enterprise reads Apache's rules as they are. OpenLiteSpeed does not — it wants them rewritten, which is where most migrations come unstuck.
Mobile readers on poor connections
HTTP/3 over QUIC recovers from packet loss without stalling the whole connection. On a good line it changes little; on a train it changes a lot.
What actually happens
Three things, in the order a request meets them
Worth being precise about, because "faster server" is what everybody says and almost nobody explains.
The cache check comes first
Before PHP, before WordPress, before the database. A hit is served from memory in single-digit milliseconds; a miss costs the same as it would anywhere else.
Connections are handled by events, not processes
Apache gives each connection a worker. LiteSpeed uses an event loop, so a thousand slow connections cost memory rather than a thousand workers.
What is left goes out compressed
Brotli where the browser accepts it, gzip where it does not, and HTTP/3 to carry it. Small savings, but on every response.
What you get
Twelve things, on the cheapest plan too
Nothing here is a tier above or an add-on at checkout.
LiteSpeed Enterprise
Licensed, not the open-source build
LSCache for WordPress
Page cache, object cache, and a warming crawler
ESI
Cache the page, leave the basket alone
HTTP/3 and QUIC
Better on lossy mobile connections
Brotli
Smaller than gzip on text, on every response
.htaccess, natively
Your Apache rules, unedited
Image optimisation
Through the cache plugin, not a separate service
Critical CSS
Generated and inlined by LSCache
PHP 8.3
With LSAPI rather than PHP-FPM
CloudLinux
Your slice of the machine stays yours
Free SSL
AutoSSL, issued and renewed
cPanel
The panel, unchanged, on top of all of it
Turning it on
Three steps, and most of it is one tick
1
Get the site here
A cPanel backup restores as it is. Moving in takes about an hour, most of it waiting.
2
Install LSCache
From the WordPress plugin screen. It is free, and it is the plugin the server is built to talk to.
3
Enable page cache
One tick. Then leave the rest alone until you have a reason — the defaults are sensible and most of the gain is in that first setting.
What people say
Read them where we cannot edit them
We are not going to print testimonials on our own page and ask you to take our word for it. These are the aggregate figures, and the link goes to every review.
4.7
Trustpilot
340
Reviews, all public
4.28
ForexPeaceArmy
across 43 reviews
across 43 reviews
Reviews on our service overall — most of them about the VPS side rather than hosting.
Read all of them →Questions
From people who already know what this is
Is this Enterprise or OpenLiteSpeed?
Enterprise, licensed. The difference that matters day to day is .htaccess: Enterprise reads Apache rules as they are, OpenLiteSpeed needs them rewritten. Several hosts advertise the open build without saying which it is — ask, wherever you end up.
How much faster is it, really?
On a cached page, several times — the request never reaches PHP. On an uncached page, very little, because the work is the same work. Anybody quoting one number for both is quoting a benchmark, not your site.
Do I have to use the LSCache plugin?
For WordPress, it is what talks to the server cache, so without it you get a fast server and no caching. Other plugins work but write files instead, which is slower and duplicates what the server already does.
What about non-WordPress sites?
The server is the same. Caching is configured in .htaccess or through the panel rather than a plugin, and static sites benefit without any configuration at all.
Does HTTP/3 need anything from me?
No. Browsers that support it use it, browsers that do not fall back to HTTP/2. Nothing to enable and nothing to break.
Will it fix a slow site?
Sometimes, and it is worth being honest: if the site is slow because of a badly written plugin or an unindexed database, a faster server hides it rather than fixes it. Caching buys you room; it does not repair the underlying work.
Cached in memory, never rebuilt
LiteSpeed Enterprise, LSCache and HTTP/3, on a machine in whichever city your readers are in.
See the plans →Running WordPress? The WordPress page has the specifics