Trade Terms
LiteSpeed — The Line on Your Sales Page That You Can Actually Substantiate
Most hosting sales pages claim to be fast. This is one of the few specifics you can put your name to and have a client verify.
Straight answer first
For a reseller, LiteSpeed is chiefly useful as a claim that holds up. It is a high-performance web server that reads Apache configuration as it stands and carries caching at server level, so 'server-level caching on every site we host' is a sentence a client can go and check rather than a slogan.
Operationally it also removes a decision from every build. Because the cache engine lives in the server rather than in a plugin somebody chose, the caching arrangement across your entire client book can be the same one — which is where the support saving actually is.
Written by the Hosting Seller staff · Checked 24 August 2026
0
Terms left for clients to decode
100+
Entries in the trade file
Real
Real examples, real kit
Free
To read, and to reuse
It reads .htaccess files and Apache rules unchanged, then serves requests with an event-driven design that handles far more of them per machine. Its server-level cache, driven on WordPress by the LSCache plugin, answers a request before PHP has been woken at all.
The pairing is what does the work: LiteSpeed underneath and LSCache on top gives page caching, ESI for the fragments that must stay dynamic, image optimisation and HTTP/3, wired together rather than assembled by hand out of four plugins with overlapping opinions.
What you can put on the page, and what you cannot
You can state that caching runs at server level on every account, that Apache rules carry across untouched, and that the caching plugin is the one written for that server rather than a generic alternative. All three are checkable, which is what makes them worth writing.
What you cannot do is quote a speed figure. Any number you print becomes a promise about a client site you have not seen, running a theme you did not choose. Describe the mechanism and let the client's own test produce the number.
Migrating a client's existing site onto it
This is where the Apache compatibility earns real money. A client site arriving from an Apache host brings its .htaccess rules, rewrites and redirects, and they continue to work — so a migration is a file and database move rather than a configuration project.
Two things to do on arrival: remove whatever generic caching plugin the site came with, and install the one built for this server. Leaving both in place is the most common cause of a migrated site behaving oddly, and it is the first thing to check when a client says the new host feels wrong.
The conversation with the client's developer
Somebody who has spent years tuning a stack elsewhere will occasionally object to swapping their caching plugin. The answer is not a debate about which plugin is better; it is that the cache engine lives in the server here and only one plugin can drive it. Everything else is a page cache in PHP competing with a page cache in the server.
Framed that way it is a compatibility fact rather than a preference, and it usually settles in one exchange. Put it in your migration notes so the same conversation does not need having per site.
Where it saves you money rather than the client
Cached requests never wake PHP, so the density you can safely run on a reseller tier is higher than it would otherwise be. That is the mechanism behind overselling working as a business model rather than as a gamble: the accounts are generous on paper because most requests cost almost nothing to serve.
It also standardises your support. One caching arrangement, one purge instruction, one plugin to know — across every account you create. That saving does not show up on any invoice, which is exactly why it is worth protecting.
Every term, costed
A trade file for resellers and agencies. What a term means, what you can claim because of it, and where it quietly changes your cost per client.
LiteSpeed caching runs at the server on every plan rather than being bolted on by plugin, and NVMe disks sit underneath every tier rather than only the top one.
- Written for the person who sends the invoice
- Claims a client can go and verify
- Migration traps flagged in advance
- Escalation behind you at any hour
Why Hosting Seller
On every plan, as standard
A speed claim that survives a test
Server-level caching on every account is checkable. That is rarer than it sounds on hosting sales pages and worth more than an adjective.
Apache rules that carry across
A client site arriving from an Apache host brings its rewrites and redirects intact, which turns a migration into a copy rather than a project.
One caching arrangement, everywhere
The engine is in the server, so every account you create can run the same setup — one purge routine and one thing for staff to learn.
The migration trap named
Two caching plugins fighting is the usual reason a freshly moved site feels wrong. Remove the generic one on arrival, every time.
A settled answer for a client's developer
Only one plugin can drive a server-level cache. That is compatibility, not preference, and it ends the argument in a single exchange.
Density you can sell against
Requests that never reach PHP cost almost nothing, which is what makes generous packages on a modest tier a business model rather than a gamble.
First Steps
From choosing to live
- 1
Strip the old caching plugin on arrival
Remove whatever came with the migrated site before installing the one built for this server. Two page caches competing is the classic post-move fault.
- 2
Write the claim once, checkably
Server-level caching, Apache compatibility, the matching plugin. Three verifiable statements beat any speed figure you could print.
- 3
Standardise across every account
One caching setup on every client site you create, so the purge instructions you send are the same document every time.
In the Box
Packed with every plan
- NVMe SSD underneath and LiteSpeed caching in front
- WHM for you, and a cPanel of their own for every client
- PHP versions picked per site from the panel
- WordPress Toolkit, with updates applied for you
- One-click installs for WordPress and 400+ other applications
- Client sites you host elsewhere moved across at no charge
- Staging copies so client changes get tested before they go live
- Overselling switched on from the first account you create
- Nothing charged at setup on any reseller tier
- Real people answering, for you and for your clients
Across the Counter
Things people ask us all the time
Is it safe to tell clients their site will be faster here?
Tell them what the platform does rather than what their site will score. Server-level caching, NVMe storage and current PHP are facts; a percentage improvement on a site you have not seen is a promise about somebody else's theme. Describe the mechanism, invite them to test before and after, and let the number be theirs.
A client's developer wants to keep their existing caching plugin. What do I say?
That only one plugin can drive a server-level cache, and the one written for this server is that plugin. Anything else is a PHP page cache competing with a server page cache, which is slower than either alone. It is a compatibility constraint rather than a preference, and put that line in your migration notes so it only needs explaining once.
Do the client's existing Apache rules survive a migration?
Yes — .htaccess rules, rewrites and most Apache configuration carry across as written, which is the whole point of the compatibility. It is the single biggest reason moving a client site here is a copy job rather than a reconfiguration job, and it is worth mentioning in a migration quote.
How does server-level caching affect what I can safely oversell?
Substantially. Requests answered from cache never wake PHP, so a busy brochure site consumes a fraction of what its traffic figures suggest. That is the real mechanism behind generous packages on a modest tier — though dynamic surfaces like shops and membership areas are the part you still size honestly.
Read next
Domain Names
Names to register and transfer for clients, with year one free on annual hosting.
OpenCart Hosting
Storefront hosting for the OpenCart builds on your list, with SSL and staging included.
Moving your site to another host? Start with this checklist.
A step-by-step order of work for a move your visitors never spot: which files to copy first, how to carry email across without losing one message, the right moment to repoint DNS, and the two mistakes behind nearly every hour of downtime people ring us about.
Stock it, brand it, sell it.
Server-level LiteSpeed caching and NVMe storage on every tier, with WHM, private nameservers and nothing to pay at setup.
See Domain Names plans