How-to · Beginner · 20 minutes

How to Test Your Website Speed

Measure honestly, so the work that follows aims at facts rather than hunches — a practical, jargon-free walkthrough with the classic mistake flagged before you make it.

See the plans Ask us a question

Straight answer first

In a line: measure honestly, so the work that follows aims at facts rather than hunches — a beginner-level task that takes 20 minutes.

Below you get the exact steps, the classic snag, and a tip from the support desk. Where our platform handles a step for you, the guide says so rather than making you do the robot's work.

Written by the Hosting Seller staff · Checked 1 August 2026

Beginner

Skill needed

Stages to finish

Free

Help included

Tested

On our own kit

You do not need to be technical for this. The walkthrough is written for first-timers, tested on our own platform, and honest about which parts are genuinely fiddly and which are merely unfamiliar.

One promise before you start: nothing in this guide is irreversible. Where a step could bite, we say so and give you the undo.

The whole job at a glance

From start to finish, you will use the two standard tools, test more than the homepage, keep field and lab data apart, read ttfb as the hosting number and retest after every single change.

No stage needs code or a terminal unless the guide says so outright, and where it does, the exact commands are printed. The full step-by-step sits below; the sections around it give the context that makes it stick.

Where this goes wrong, and how not to

Chasing a lab score of 100. Lab runs move about with the test server and the moment, while field vitals are what rankings actually read. A steady green real-user experience beats a fragile perfect number every time.

Forewarned really is forearmed here. This one mistake accounts for most of the frustration the subject produces, and it is entirely avoidable once somebody names it.

The shortcut, straight from the support desk

Test from where your customers actually are. A UK site measured from a US node reports transatlantic latency as though it were your fault, and most tools let you choose the test location from a dropdown.

It costs a minute now and pays that back every time the job comes round again — which, like most hosting jobs, it certainly will.

What runs by itself here

Several steps in this guide exist only because hosting historically made you do them. On our plans SSL issues itself, backups run daily without being asked, and one-click installers replace the manual setup entirely. What is left is the part that is genuinely yours.

And when a step misbehaves anyway, support answers at any hour with the actual fix, not a knowledge-base link and a shrug. Half our best guides began life as a pattern in the ticket queue.

The hosting this guide is written against

Every walkthrough on our how-to shelf is tested on the platform we actually run — cPanel, LiteSpeed, NVMe, one-click installs — so the instructions match your screen instead of gesturing vaguely at it.

Mailboxes on your own domain are part of the plan, never an add-on sold back to you at checkout.

Step by step, tested exactly as printed
The snag flagged before you reach it
The dull steps are already automated
People on hand at any hour if you stall

Why Hosting Seller

On every plan, as standard

Help on the counter

Stuck on step three at midnight? Support answers at any hour, mid-guide included.

5 steps, no filler

Each stage is a few minutes of steady clicking, with the fiddly parts marked as fiddly.

The undo is always named

Where a step could bite, the guide says so and tells you how to put it back again.

The snag, named early

The classic mistake for this exact job is flagged before step one, so 20 minutes stays 20 minutes.

Works exactly as written

Every step tested on the platform we run — no 'your host may differ' hand-waving anywhere.

Written from real tickets

Our guides come off the support desk, so the snags flagged here are the ones people genuinely hit.

First Steps

From choosing to live

1
Use the two standard tools
PageSpeed Insights for Core Web Vitals and the lab detail, WebPageTest for the waterfall. Between them you get the whole picture rather than half of it.
2
Test more than the homepage
Homepage, a product or service page, a content page. Templates differ, and the homepage is often the least representative page on the entire site.
3
Keep field and lab data apart
Field data comes from real Chrome users and is what ranking reads. Lab runs are diagnostics. A lab score of 60 with green field vitals is healthier than the reverse.
4
Read TTFB as the hosting number
Time to first byte separates server response from page weight. A high TTFB points at hosting and caching; slowness after the first byte points at the page itself.
5
Retest after every single change
One change, one retest. Attribution is the whole value of measuring, and a batch of five changes leaves you with a faster site and no idea which change did it.

In the Box

Packed with every plan

WebP image optimisation built in and costing nothing
A 30-day money-back guarantee on every hosting plan
Site migration done for you by our staff, at no charge
Nothing added at setup — no joining fee, ever
The renewal price printed on the tag matches the order price
Spam and virus filtering fitted to every mailbox
A backup taken daily, with restores you run yourself
Staging copies so changes get tested before they go live
A domain free for year one when you order annually
Real people on the counter, every hour of every day

Across the Counter

The questions we get asked most

Why does the same page score differently every run?

Lab variance: test-server load, the state of the network, cold cache against warm. Run three and take the median, then lean on field data — which aggregates weeks of real visitors — for anything you intend to act on.

What counts as a good TTFB?

A cached page on decent hosting answers nearby visitors comfortably under 200ms. Sustained figures above roughly 600ms point at hosting, caching or the application itself, and no amount of shrinking images will move that number.

What if the site outgrows the plan I bought?

You move up 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 whole dedicated servers. Growing becomes a line change on your account rather than a hunt for a new host.

What happens to my files if I leave?

The site and the files stay yours. Pull a full backup from the panel whenever you like, before or during cancellation. Domains remain registered in your name for the term you paid for and can move to any registrar once the standard 60-day window has passed.

What does round-the-clock support actually stretch to?

People at the counter at every hour, and a scope that takes in the practical work: mailbox setup, DNS records, WordPress trouble, restores. Not 'the server responds, ticket closed'. Ask us something hard before you order — the reply is a fair sample of what you would get afterwards.

How do I pay, and does it bill again on its own?

Orders go through a secure checkout by credit or debit card, and the renewal is taken at the same price you first paid. Every invoice sits in the client area for you to read, and switching auto-renewal off is a toggle in your account rather than a phone call.

What uptime do you commit to, and who is watching?

We commit to 99.9% uptime and watch it continuously. That figure is an operational target rather than a poster line, and the alerting behind it usually has an engineer on a problem before the first customer notices anything is wrong.

Packing up and moving host? Take our checklist.

A plain running order for a move nobody notices: what to copy first, how to carry email across without dropping a single message, when to point DNS, and the two slips behind nearly every hour of downtime we get called about.

Get online, with no games at checkout.

Quick NVMe hosting, SSL and the move in included, and real people on the counter at any hour — on a price that doesn't shift.

See the plans