Walkthrough · Beginner · 20 minutes
How to Test Your Website Speed
Measure honestly, so whatever work follows aims at evidence rather than guesswork — a hands-on walkthrough in plain words that names the classic mistake before you reach it.
The short answer
One line covers it: measure honestly, so whatever work follows aims at evidence rather than guesswork — 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.
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 whole job in one view
Over the whole job, you will run the two reference tools, test more than the homepage, keep field data apart from lab data, read ttfb as the hosting metric and retest after every single change.
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
Chasing a perfect lab 100. Lab scores wobble with the test server and the moment, whereas field vitals are what rankings actually use. A consistently green real-user experience beats a fragile perfect number every time.
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.
The support desk's own short cut
Measure from where your audience is. Test a UK site from a US node and the transatlantic hop is charged to your account; the location sits in a dropdown on most tools.
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.
Should a step still misfire, support answers at any hour with an actual fix rather than a knowledge-base link and a shrug. Half the guides on this site began as repeat patterns in our ticket queue.
Why this job is shorter on our plans
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.
The rate you register at is the rate you renew at, so year two costs precisely what year one did — nothing lying in wait on the invoice.
- 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
Help that keeps your hours, not ours
Stuck on step three at midnight? Support answers at any hour, mid-walkthrough included.
5 steps, nothing padded
Each stage is a few minutes of steady clicking, and the fiddly moments are labelled fiddly.
Every undo written out
Any step that could bite is marked, together with the exact way to wind it back.
The snag, flagged up front
The classic error for this particular task is named before step one, which is how 20 minutes stays 20 minutes.
Works exactly as printed
Every step is proven on the platform we run — none of the 'your host may vary' hedging.
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
Run the two reference tools
PageSpeed Insights for Core Web Vitals and lab detail, WebPageTest for the waterfall. Between them you get the whole picture instead of half of one.
- 2
Test more than the homepage
The homepage, a product or service page, a content page. Each template behaves differently, and the homepage is often the least representative page on the site.
- 3
Keep field data apart from lab data
The field numbers are gathered from real Chrome users, and those are the ones ranking feeds on. Lab runs are diagnostic instruments. A lab score of 60 with green field vitals beats the other way round.
- 4
Read TTFB as the hosting metric
What TTFB measures is the thinking time before a single byte of content moves. Where that number is high, look at hosting and caching; where the delay comes later in the load, the page itself is carrying too much.
- 5
Retest after every single change
One change, one measurement. Attribution is the whole point of testing, and five changes at once leave you with a quicker site and no idea what earned it.
Built In
Fitted to every plan
- The name's first year included when you order annually
- A renewal figure identical to the one you registered at
- WebP image optimisation built in, at no extra charge
- Softaculous included for one-click application installs
- Money back within 30 days on hosting plans, 7 on reseller
- Your existing site brought across by our engineers, at no charge
- No set-up charge at any point, and no joining fee
- 99.9% uptime as the target, watched around the clock
- Spam and virus screening on every mailbox by default
- LiteSpeed caching in the server itself rather than bolted on by plugin
Frequently Asked
The questions that come up most
Why do repeated runs on one page give different scores?
That is lab variance: test-server load, network conditions, a cold cache against a warm one. Run three, take the median, then rely on field data, weeks of aggregated real visits, for any decision you intend to act on.
What TTFB should I be aiming at?
A cached page on decent hosting serves nearby visitors comfortably under 200ms. Readings persistently above roughly 600ms point at hosting, caching or the application, and no amount of image shrinking will move that figure.
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.
If I cancel, what becomes of my site and files?
They remain yours. Download a full copy from the panel whenever you like, before or during cancellation. Names stay registered in your name for the term you paid for and can move to any registrar once the standard 60-day window has passed.
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 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.
DNS (Domain Name System) (Glossary)
The full definition, along with the practical consequence nobody bothers to mention.
Business Hosting
Shared hosting carrying the whole developer kit, from SSH through Node.js and Python to PostgreSQL.
WordPress Hosting
WordPress looked after for you — LiteSpeed caching, staging copies and a daily backup.
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.
NVMe hosting with SSL and the migration included, people answering at any hour, and a price that stays where it was.
View Business Hosting plans