Testing website speed: how to measure load time properly
3 min read below · WebYes knowledge base
Test your website speed with lab and field data. Learn which tools to use, which values matter and how to make a slow site faster.
You test a website's speed by loading a page under realistic conditions and measuring how quickly the content appears and responds. The key metrics are the Core Web Vitals; a good test covers multiple pages and simulates a mobile connection.
What does a speed test actually measure?
A good speed test looks beyond how long the page takes to load. Three moments matter: how quickly the first visible part appears, how quickly the largest element (usually the hero image or main heading) renders, and how quickly the page responds once you click or scroll. Visual stability counts too: if the layout jumps around while loading, the site feels slow and you misclick.
These moments are standardised in the Core Web Vitals: LCP, INP and CLS. If you know those three values, you almost always know where the problem is.
Test under realistic conditions
Most owners test their site on a fast laptop with fibre, while the majority of visitors arrive on a phone over a mobile network. So always test with a simulated mobile connection and an average device. A page that loads in 1 second at the office can easily need 5 seconds on 4G.
Also test more than just the homepage. Product, category and contact pages often have different problems: more images, more scripts, different templates. That is why the WebYes scan measures multiple pages per site and includes the result in the speed pillar.
Look at the metrics, not the report grade
Many testing tools show a total score, and that invites point-chasing. Usually that is wasted effort. A score is a weighted summary; the underlying measurements tell you what a visitor actually notices. A site can climb from 82 to 91 points without anyone feeling a difference, and conversely a half-second improvement in LCP can be immediately noticeable while the score barely moves.
So work from big to small: first the metric that scores worst, and within it the page with the most traffic. A product page that attracts hundreds of visitors a day and loads slowly matters more than a contact page with a perfect score. Combine the test results with your visitor statistics to decide where an improvement pays off most.
From measurement to improvement
Almost every slow site has the same three culprits, in this order of impact:
| Cause | Symptom | Fix |
|---|---|---|
| Oversized images | High LCP, heavy data usage | Compress, use modern formats (WebP/AVIF), correct dimensions |
| Too much JavaScript | Sluggish interaction, high INP | Remove scripts, defer them or load only where needed |
| Slow server response | Long wait for the first byte | Caching, better hosting or a CDN |
Measure again after every change. Speed optimisation is a cycle of measuring, adjusting and verifying; without a new measurement you do not know whether a fix works.
Related articles
What are Core Web Vitals? LCP, INP and CLS explained
Core Web Vitals measure loading speed, responsiveness and visual stability. Learn what LCP, INP and CLS mean and which values score well.
Mobile-friendly website: what does your site need to get right?
A mobile-friendly website works well on every screen. Read where it goes wrong in practice, what Google expects and how to test your own site.
Frequently asked questions
What is a good load time for a website?
Aim for an LCP under 2.5 seconds on a mobile connection, measured at the 75th percentile of your visitors. Above 4 seconds Google rates the page as slow and noticeably more visitors drop off.
Why do different testing tools give different scores?
Tools differ in test location, simulated device and connection speed. So do not compare individual scores between tools; follow the trend within the same tool. The underlying metrics (LCP, INP, CLS) are defined identically everywhere.
How often should I test my site's speed?
Test after every major change (new theme, new plugin, redesign) and periodically on top of that, monthly for example. Sites slow down gradually as scripts, images and features accumulate without anyone watching performance.
The WebYes scan measures this too
Scan your website for free on speed, security, mobile and accessibility and see where you stand.
Start free scan