Live website speed test
Live checkThis measures the server’s first response from an Indian point of presence. TTFB under 600 ms is a good server answer; anything over 2 s and your visitors are paying for slow infrastructure. Read the full method below, then see speed optimisation if the numbers are poor.
What a website speed test online measures
The test is a reading of one URL, not a grade of the whole company. Load time is how long the page takes to finish. Largest contentful paint is when the biggest visible block appears. Layout shift is how much the page jumps while loading. Interaction delay is how long a tap waits before the page responds. This page does not run the test for you. It tells you which numbers to trust when a test does.
| Figure | What it measures | Good line |
|---|---|---|
| Largest contentful paint | When the largest visible block has painted | Under 2.5 seconds |
| Layout shift | Unexpected movement while the page loads | Under 0.1 |
| Interaction delay | Wait between a tap and the next paint | Under 200 milliseconds |
| Time to first byte | Wait for the first byte from the server | Under 0.8 seconds |
Green, amber and red on a typical report follow those bands: under the good line, between the good line and the poor line, and past the poor line. Change one thing, then run the test again.
How to test server speed with time to first byte
To test server speed, isolate time to first byte from the rest of the load. That figure is the server answering, before images and scripts finish. A page that is heavy in the browser can still have a fast first byte. A page that waits two seconds before any byte is a server or network problem, even if the HTML is tiny.
Distance adds delay. A test run far from the host reads a different first byte than a visitor near the host. Run more than one location when the audience is spread out. The WebJi homepage is the hosting start if the server itself is what you need to change.
How to read a hosting server speed test
A hosting server speed test is the same clock, read for the host. If time to first byte is the slow part, look at the server, the application and how far the test sat from the machine. If the first byte is fine and largest paint is slow, look at images, fonts and scripts on the page. Do not buy a bigger server for a picture that was never compressed.
Field numbers, from real visitors, and lab numbers, from one simulated browser, answer different questions. Use the lab pass to find a cause. Use the field pass to see whether visitors actually improved. When the page is WordPress, the next write-up on this site is WordPress speed optimization.
Frequently Asked Questions
How do I read a website speed test?
Read load time, time to first byte, largest contentful paint, layout shift and interaction delay. Good lines used on this page are under 2.5 seconds for largest paint, under 0.1 for layout shift, and under 200 milliseconds for interaction delay.
What is a good largest contentful paint?
Under 2.5 seconds is the good line. Over 4 seconds is poor. The number is when the largest visible block finished painting.
What does time to first byte tell me?
It is the wait before the first byte returns. A high time to first byte, with the rest of the page light, points at the server. That is the hosting server speed test reading.
Why can mobile look slower than desktop?
A lab test often uses a slower phone and a slower network than a desktop wired test. Field data is real visitors. Lab data is one controlled run. They can disagree.
Does a green lab score mean real visitors are fine?
No. A lab score is one simulated load. Real visitors bring other devices and networks. Retest after a single change so you know what moved.