Walkthrough · Beginner · 20 minutes
How to Enable LiteSpeed Caching
Turn the server's cache engine on and verify it is genuinely delivering hits — a hands-on walkthrough in plain words that names the classic mistake before you reach it.
The short answer
One line covers it: turn the server's cache engine on and verify it is genuinely delivering hits — a beginner-level job of roughly 20 minutes.
Below are the precise steps, the classic stumble, and one tip from the support desk. Wherever the platform already does a step for you, the guide says so rather than handing you a machine's chores.
By the Hosting & Domains team · Reviewed 18 August 2026
Beginner
Experience required
5
Stages, start to finish
Free
Support included
Proven
On the platform itself
No technical background needed. This walkthrough was written for first-timers, proven on our own hardware, and honest about which parts are genuinely tricky rather than merely unfamiliar.
First rule: read the snag section before you start, not afterwards. It was distilled from the tickets of everyone who tried the other order.
How the work divides up
Over the whole job, you will get litespeed cache onto the site, leave the defaults alone for now, look at the response headers, check the exclusions took and purge after structural edits.
No part of this needs code or a terminal unless the guide says so plainly — and where it does, the exact commands are printed. The step-by-step is below, with the surrounding sections supplying the context that makes it hold.
The well-worn snag
Judging the cache while signed in as an admin. Administrators bypass it deliberately, so the owner's own browser is the one place the acceleration cannot be seen. Test signed out, or from a private window.
Forewarned is genuinely forearmed here. This one mistake accounts for most of the frustration the topic ever causes — and it disappears entirely once somebody points it out.
What we tell every customer
Pair page caching with the plugin's browser-cache headers. First visits come from the server cache, return visits skip the network altogether, and the two layers stack rather than collide.
A minute spent now repays itself every time this job comes round again — and like almost every hosting job, come round it will.
The parts that look after themselves here
Some steps in this guide exist only because hosting traditionally forced them on you. Here the SSL issues itself, the copy is taken daily without being asked, and one-click installers remove the manual setup. What is left is the part that was always genuinely yours.
Stopped mid-guide at an awkward hour? That is exactly what round-the-clock support is for — say which step you are on and we take it from there.
A quick platform makes for a short guide
Tutorials written against imaginary hosting go stale fast. Ours are written against the real thing: the same panel, installer and defaults waiting in your account.
Mailboxes at your own name are part of the plan — mail is included, not sold back to you at the checkout.
- Every step checked exactly as published
- The snag named before it arrives
- The dull steps taken out of your way
- People reachable at any hour you stall
Why Hosting & Domains
Standard on every plan
Honest about how big it is
Turn the server's cache engine on and verify it is genuinely delivering hits is a beginner-level job — set aside 20 minutes, with the platform-absorbed steps marked.
Help that keeps your hours, not ours
Stuck on step three at midnight? Support answers at any hour, mid-walkthrough included.
Taken from real tickets
These guides came out of the support queue, so every snag flagged is one people genuinely hit.
5 steps, nothing padded
Each stage is a few minutes of steady clicking, and the fiddly moments are labelled fiddly.
Works exactly as printed
Every step is proven on the platform we run — none of the 'your host may vary' hedging.
Every undo written out
Any step that could bite is marked, together with the exact way to wind it back.
Quick Start
Order placed to site online
- 1
Get LiteSpeed Cache onto the site
With WordPress on our LiteSpeed servers, the plugin is the control surface for the server's own engine. Install it, activate it, switch caching on.
- 2
Leave the defaults alone for now
The stock lifetimes and rules suit most sites well. Resist exploring every setting before the basics are proved to work.
- 3
Look at the response headers
Open dev tools, network tab, and read the page headers. x-litespeed-cache: hit on the second visit is your evidence. A permanent 'miss' means the setup needs attention.
- 4
Check the exclusions took
Running WooCommerce? Its cart, checkout and account screens should have opted themselves out of the cache, so confirm they did and then add any custom dynamic URLs to the never-cache list yourself.
- 5
Purge after structural edits
Until you purge, a design or layout change stays invisible to visitors. That purge button answers most 'my changes are invisible' puzzles.
Built In
Fitted to every plan
- 99.9% uptime as the target, watched around the clock
- NVMe SSD storage on every tier, not only the dear ones
- LiteSpeed caching in the server itself rather than bolted on by plugin
- A renewal figure identical to the one you registered at
- Mailboxes that answer at the name you hold
- Money back within 30 days on hosting plans, 7 on reseller
- WebP image optimisation built in, at no extra charge
- PHP versions set per site from the control panel
- Webmail in the browser plus IMAP, POP and SMTP for any client
- The name's first year included when you order annually
Frequently Asked
The questions that come up most
Why does the header say miss on every load?
The usual suspects, in order: caching never actually switched on in the plugin, a cookie from another plugin marking every visitor dynamic, or the test page excluding itself. The plugin's environment report names the culprit.
Can caching break checkout or form submissions?
Not when it is set up properly. Form posts go straight past the cache and commerce pages exclude themselves. The rare clash, usually an expired cached nonce, needs one targeted exclusion rather than a retreat from caching.
What happens when I outgrow the plan?
You upgrade in place. Plan changes are made from the client area with no migration and no downtime, and the range runs from small shared accounts through VPS to full dedicated machines. Growth becomes a setting on the account rather than a search for a new host.
Can more than one website run on a single plan?
From the Turbo tier upward, yes — several sites, each with its own name, mailboxes and certificate, inside one account. If the extra sites belong to clients rather than to you, look at reseller hosting instead: it keeps each one properly walled off.
Keep reading
How to Create an SPF Record
Declare publicly which servers may send email under your domain's name — intermediate level, about 10 minutes.
How to Secure WordPress
Shut the doors WordPress attackers actually use — intermediate level, about an hour of setup.
Best LiteSpeed Hosting
A shortlist with the working shown: what to check, and the single trap most buyers fall into.
Reseller Hosting
White-label WHM hosting — your brand in front, monthly billing behind.
Agency Hosting
Client accounts, staging and care-plan infrastructure arranged for agencies.
Changing hosts? Run through our checklist first.
A plain order of work for a move nobody visiting will notice: which files go over first, how to carry the mail across without losing a message, when exactly to repoint DNS, and the two mistakes behind nearly every outage we are asked to rescue.
Put the site on ground you own.
From a first website to a rack of machines, moving up is a change to the account rather than a migration.
View Reseller Hosting plans