Client performance · Retainer work · an afternoon
How to speed up WordPress — Work the Server Layer Before You Quote a Rebuild
A client forwards a speed test with a red score and asks what it will cost — and the honest answer is usually an afternoon, not a redesign.
Straight answer first
Start with a written before reading, then turn on server-level caching, because on a LiteSpeed account that single change takes PHP and the database out of most anonymous visits and nothing else on the list comes close to it. Most client sites arriving with a bad score are not badly built; they are uncached, image-heavy and carrying plugins the previous agency left behind.
Work down from there: images to WebP and correctly sized, inherited plugin weight removed, PHP 8.x confirmed and object caching available for the dynamic side. Then re-measure and give the client the two figures side by side. The report is what you are selling; the afternoon of work is how you produce it.
Written by the Hosting Seller staff · Checked 24 August 2026
Intermediate
Level for your team
5
Stages in the pass
Free
Cost of asking us
Tested
On the platform you resell
Written for the person being asked to explain somebody else's speed score. The technical steps are well known; the value is in sequencing them so you can prove which one moved the number.
Take the reading before you touch anything. Without a starting figure you cannot distinguish improvement from imagination, and neither can the client.
The report the client will actually read
Two numbers, before and after, on the pages that matter to their business rather than the homepage alone. Record time to first byte separately from the overall score, because TTFB separates a server problem from a page problem and it is the figure that tells you whether the account or the build is at fault.
Everything else — waterfall charts, opportunity lists, lab versus field data — is your working, not the deliverable. Clients act on two numbers and a sentence explaining what changed.
Caching does most of it, and it is already there
LiteSpeed caching runs at the server on these accounts rather than being bolted on by plugin, and configuring LSCache on the site connects the two. Anonymous visits then get served a page the server already has ready, which is why it outperforms every other change by a wide margin.
It is also the change you do not bill much for, and that is fine. It buys you the credibility to charge properly for the image work and the plugin audit, which are the parts that actually take an afternoon.
The weight the last agency left behind
Inherited client sites accumulate: three plugins doing overlapping jobs, a page builder used for two pages, a homepage slider nobody has updated in years, and a font stack loading six weights. Every script is a toll charged to every visitor on every visit.
Remove rather than optimise. A plugin whose features the client never uses does not need configuring, minifying or deferring; it needs deleting. Do it on staging with the site clicked through afterwards, because inherited sites hide dependencies in places nobody documented.
Making speed a retainer line, not a one-off
A single optimisation pass decays. Content gets added, a plugin arrives, an uncompressed hero image goes up. Sell a quarterly check instead: the same pages, the same tool, the same two numbers, with a short note about what moved.
It is small, recurring, easy to deliver once you have the baseline, and it puts you in front of the client four times a year with evidence that you are doing something — which is worth more than the fee.
What the platform contributes before you touch the site
LiteSpeed caching running at the server rather than bolted on per site, NVMe SSD storage on every tier, WebP image optimisation built in and costing nothing, and PHP versions chosen per client account from the panel.
Reseller tiers from $14.99/mo plus $0.40 for each active client account, with a 99.9% uptime target the monitoring desk is measured against and upgrades applied in place if a client genuinely outgrows the tier.
- LiteSpeed caching at the server, not bolted on per site
- WebP image optimisation built in and costing nothing
- NVMe SSD storage on every tier, not just the top one
- PHP versions chosen per client account from the panel
Why Hosting Seller
On every plan, as standard
A baseline you can point at
Before and after on the pages that matter, with TTFB recorded separately so cause is not guesswork.
The big win first
Server-level caching removes PHP and the database from most visits, and it is already part of the plan.
Inherited weight removed
Overlapping plugins and unused builders deleted rather than optimised, which is faster and cheaper both.
Images handled at the platform
WebP optimisation is built in and costs nothing, so the heaviest part of most pages is not a paid add-on.
Proof the number moved
The same tool, the same pages, the same two figures — a report the client believes rather than a claim.
Recurring, not one-off
A quarterly check turns an afternoon of work into a retainer line and keeps the gains from decaying.
First Steps
From choosing to live
- 1
Take a before reading you can show the client
Run the pages that matter to their business through a speed test and write down the overall figure and the time to first byte separately. Without a starting number you cannot prove improvement, and the client cannot either.
- 2
Turn on server-level caching from the account
On LiteSpeed hosting, configure the LSCache plugin so the site talks to the caching that is already running at the server. Most anonymous visits then become a file the server has ready, and no other single change is close.
- 3
Deal with the images properly
Serve WebP, size images to the box they sit in, and lazy-load anything below the fold. WebP optimisation is built into the platform at no cost, so this is configuration rather than a paid add-on.
- 4
Delete what the previous agency left behind
Remove overlapping plugins, page-builder weight used on two pages, and font weights nobody chose. Do it on staging and click the site through afterwards — inherited builds hide dependencies nobody wrote down.
- 5
Confirm PHP 8.x and object caching, then re-measure
Check the account is on a current PHP release and that Redis object caching is available for the dynamic side and the dashboard. Then run the identical test and put the two numbers next to each other for the client.
In the Box
Packed with every plan
- LiteSpeed caching at the server, not bolted on per site by plugin
- WebP image optimisation built in and costing nothing
- NVMe SSD storage on every tier, not just the top one
- PHP versions chosen per client account from the panel
- Staging copies so changes get tested before a client sees them
- A 99.9% uptime target, watched by monitoring day and night
- Daily backups, with restores you run yourself from the panel
- DDoS filtering handled out at the network edge
- Upgrades applied to the account in place, with no move between plans
- A 30-day money-back guarantee on hosting plans, 7 days on reseller
Across the Counter
Things people ask us all the time
The client forwarded a red speed score — how do I answer before quoting?
Take your own reading first, and record TTFB separately from the overall figure. A slow TTFB points at the account or the build's server-side work; a fast TTFB with a poor score points at images, scripts and layout. That distinction decides whether you are quoting an afternoon or a rebuild.
Which single change should I make first on an inherited client site?
Server-level page caching, and it is not close. It removes PHP and the database from most anonymous visits entirely. Everything else on the list optimises the smaller share of requests that still have to be built from scratch.
The site is quick but the client says the dashboard drags — why?
The admin deliberately bypasses page caching, so it shows raw PHP and database speed with nothing hiding it. PHP 8.x, Redis object caching and NVMe storage fix most of it, and pruning heavy dashboard plugins fixes the rest. It is worth explaining, because clients judge speed by the screen they spend time on.
Can I sell performance work as an ongoing line rather than a one-off?
Yes, and it is one of the easier retainer items to justify. A quarterly check on the same pages with the same tool produces two numbers and a short note, takes very little time once the baseline exists, and puts evidence of your work in front of the client four times a year.
Read next
Web Hosting
cPanel accounts on NVMe behind LiteSpeed, with SSL, free migration and a year-one domain.
Email Hosting
Proper mailboxes on client domains at one flat price, whether or not you host their site.
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.
Put the client on a platform that starts fast.
LiteSpeed at the server, NVMe on every tier and WebP built in — reseller plans from $14.99/mo plus $0.40 per active client account.
See Web Hosting plans