Walkthrough · Intermediate · an afternoon
How to Speed Up WordPress
Strip load times down using the few changes that actually move the needle — a hands-on walkthrough in plain words that names the classic mistake before you reach it.
The short answer
One line covers it: strip load times down using the few changes that actually move the needle — a intermediate-level job of roughly an afternoon.
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
Intermediate
Experience required
5
Stages, start to finish
Free
Support included
Proven
On the platform itself
No prior knowledge assumed — a hosting account, a browser and afternoon of attention is the whole entry requirement. Every instruction runs on our platform exactly as printed, and carries over to any standard cPanel host.
A promise before step one: nothing here is a one-way door. Any step with teeth is flagged, and the way back is printed beside it.
The route, mapped end to end
The work falls into a few clean stages: measure before you change anything, turn caching on at the server, sort the images out, drop the plugins and scripts nobody uses and look at the engine underneath.
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.
Where it comes off, and how to stay on
Running three caching plugins for extra speed. Overlapping caches fight, serve stale pages and occasionally corrupt one another. One well-tuned cache layer beats any stack of them.
It earns a section of its own because it is no obscure edge case — it is the single commonest reason this task reaches a support queue. Knowing it in advance turns the whole job from risky into routine.
What we tell every customer
Tune for the number that survives real traffic rather than the laboratory trophy. A dependable 90 beats a fragile 100 propped up with tricks. Measure again after each change, so you never lose the link between cause and effect.
A minute spent now repays itself every time this job comes round again — and like almost every hosting job, come round it will.
Where this platform takes work off you
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.

The hosting these steps were tested on
Every walkthrough in this library is run on the platform we actually operate — cPanel, LiteSpeed, NVMe, one-click installs — so the instructions match your screen rather than gesturing at it from a distance.
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
Jargon never charges you
Every term is defined on the spot or linked to the jargon buster — nothing assumes prior knowledge.
The snag, flagged up front
The classic error for this particular task is named before step one, which is how an afternoon stays an afternoon.
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.
Honest about how big it is
Strip load times down using the few changes that actually move the needle is a intermediate-level job — set aside an afternoon, with the platform-absorbed steps marked.
Taken from real tickets
These guides came out of the support queue, so every snag flagged is one people genuinely hit.
Quick Start
Order placed to site online
- 1
Measure before you change anything
Put your main pages through PageSpeed Insights and record the TTFB separately. Without a baseline there is no way to tell a real gain from wishful thinking, and TTFB is what separates a server problem from a page problem.
- 2
Turn caching on at the server
On LiteSpeed hosting, set the LSCache plugin up. Page caching turns most anonymous visits into a pre-built file the server hands straight over, and nothing else available to you comes close to it.
- 3
Sort the images out
WebP output, dimensions that match their containers, lazy loading below the fold. Images are the heaviest cargo on most pages, and the plugin handles all three of those jobs.
- 4
Drop the plugins and scripts nobody uses
Remove plugins whose features go unused, and page-builder weight wherever a plain block would do. Each script levies a charge on every visitor, on every page they open.
- 5
Look at the engine underneath
Confirm you are on PHP 8.x and that Redis object caching is available. Dynamic pages and the admin lean on both, even where page caching covers the public side.
Built In
Fitted to every plan
- 99.9% uptime as the target, watched around the clock
- LiteSpeed caching in the server itself rather than bolted on by plugin
- DDoS filtering absorbed at the network edge
- Staging copies for trying a change before it goes live
- People on the support desk every hour of every day
- NVMe SSD storage on every tier, not only the dear ones
- Webmail in the browser plus IMAP, POP and SMTP for any client
- Money back within 30 days on hosting plans, 7 on reseller
- Spam and virus screening on every mailbox by default
- Free SSL on every plan, reissued before the old one lapses
Frequently Asked
The questions that come up most
Which single change buys the most speed?
Server-level page caching, by a distance. It takes PHP and the database out of most requests entirely. Everything else on the list improves the minority of hits that still have to be built fresh.
Why is the public site quick while wp-admin drags?
The admin deliberately skips page caching, which exposes raw PHP and database performance with nothing to soften it. PHP 8.x, Redis object caching and NVMe storage fix most of it, and cutting heavy dashboard plugins deals with the rest.
How do payments and auto-renewal work?
You pay by credit or debit card through a secure checkout, and renewals bill at the same rate as the original order. Every invoice sits in your client area, and auto-renewal switches off with a toggle in the account — no telephone call needed.
Does hosting include mail?
Yes — every hosting plan includes mailboxes at your own name, with webmail, IMAP, POP and SMTP plus spam filtering on from the start. There is standalone email hosting too, for a name whose website lives somewhere else.
Keep reading
How to Use a WordPress Staging Site
Test every risky change on a copy the public never sees — beginner level, about 10 minutes to set up, and hours saved on a regular basis.
How to Park an Extra Domain
Turn the idle names you hold into something useful instead of a dead end — beginner level, about 5 minutes each.
Best Drupal vs WordPress
A shortlist with the working shown: what to check, and the single trap most buyers fall into.
Web Hosting
cPanel hosting on NVMe drives — SSL, the migration and year one of the name all included.
Email Hosting
Proper mailboxes at your own name, for one flat rate.
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.
Your site has earned better hosting.
From a first website to a rack of machines, moving up is a change to the account rather than a migration.
View Web Hosting plans