Network Latency and Jitter Explained: What They Mean and What TryYourGear's Test Measures
What latency, round-trip time and jitter mean, why a fast connection can still lag, and what TryYourGear's Network Latency Test does and doesn't measure.
You can have a fast plan and still see lag in a call or a game. “Fast” usually refers to bandwidth, how much data can move per second. Lag depends on latency, how long a message takes, and on how steady that time is, which is jitter. This guide explains the three, and then shows exactly what TryYourGear's Network Latency Test measures, because that is narrower than the word “ping” suggests.
The short version
The Network Latency Test measures the round-trip time between your browser and the TryYourGear server. It is not your Internet ping, it is not a speed test and it is not a full diagnosis of your connection.
Latency, round-trip time and jitter
- Latency is the time data takes to get from one point of a network to another. Cloudflare describes it as the time a packet needs to travel from your device to the service you are using and back.
- Round-trip time (RTT) is the time for a message to go out and for the reply to come back. It is what most tools call latency or ping, and it is what this test measures.
- Jitter is how much latency varies from one measurement to the next. Cloudflare defines it as the average variation found in consecutive latency measurements: a lower number means more consistent times. TryYourGear's test uses the same idea: the average absolute difference between consecutive valid RTT samples.
Two connections can share almost the same average and behave very differently. With these made-up numbers, five samples of 20, 22, 21, 23 and 20 ms average 21.2 ms and have a jitter of 2.0 ms. Five samples of 5, 40, 8, 45 and 8 ms also average 21.2 ms, but their jitter is 35.25 ms. The second connection is far less steady, and a call or a game would feel it, even though the average alone looks the same.
Why a fast connection can still lag
Bandwidth is capacity; latency is delay. Downloading a large file is limited mostly by bandwidth. A video call, a game or a page made of many small requests is limited by how long each round trip takes and how steady that time is. A wide highway lets many cars travel at once (bandwidth), but it doesn't shorten the trip (latency) or make every trip take the same time (jitter). A plan sold in Mbps says nothing about latency or jitter on its own.
For illustration only: a 500 Mbps plan can still take, say, 80 ms to answer a tiny request. A big download will be quick, and a game that sends many small updates will feel that delay on each one.
Three different things you might want to measure
| Scope | What it is | Does TryYourGear's test measure it? |
|---|---|---|
| To the TryYourGear server | The round trip between your browser and this site's server, through your own network and the route across the Internet. | Yes. It is the only thing this test measures. |
| To another destination | A game server, a video-call service, a DNS server or another website. Each is in a different place and reached by a different route, so each gives a different number. | No. Use the latency display of that game or service, or another tool. |
| Inside your local network | The Wi-Fi or cable segment between your device and your router. | Not on its own. It is part of the path, but the test gives one total and can't split it. |
Distance matters because signals need time to travel and each network on the route adds some delay. Congestion adds more, and it can change by the hour. That is why one connection can give different numbers to different destinations. Wi-Fi is a shared radio channel: interference, distance from the router and other devices on the network can make delivery time vary more than it does on a cable, so when jitter is high, comparing Wi-Fi with a cable is one of the most informative checks. This is general networking behaviour; the test doesn't measure it directly.
What the Network Latency Test does
One warm-up request
It isn't counted, so the first request has already gone through before anything is measured.
Ten timed requests
Each one is a tiny request to
/api/pingon TryYourGear, which answers with an empty response. The page notes the time before sending and after the reply arrives, usingperformance.now(). That gap is the RTT. Every request carries a unique parameter and asks the browser not to cache, so a cache can't answer instead of the server.Pauses and time limits
About 0.3 seconds separate the samples, each request has a 5-second timeout and nothing is retried.
Average, minimum, maximum and jitter
The test shows the average, the minimum and the maximum of the valid samples, the jitter and how many samples were valid. Failed samples are listed and left out of the statistics.
Errors
It needs at least five valid samples to show numbers, and after three failures in a row it stops instead of waiting for eleven timeouts. If it can't produce a result it says why: you appear to be offline, the server didn't answer in time, it returned an error response or the requests couldn't reach it.
The page also adds a rough label that applies to this server only: under 50 ms is low, 50 to 150 ms is moderate and over 150 ms is higher. Those are guide values, not a standard and not a verdict on your connection.
Reading a result
| What you see | What it suggests | What to try |
|---|---|---|
| Low average and low jitter | The trip to this server was quick and steady during this run. | Nothing to fix. It says nothing about other destinations. |
| Low average but high jitter, with a wide gap between minimum and maximum | Usually fast, but some requests took much longer: variability. Wi-Fi interference, other traffic on your network or a busy moment are common suspects. | Run it again, try a cable and pause downloads and streams. |
| High average and low jitter | Consistently slow to this server: distance, the route or a slow link rather than instability. A VPN or proxy can add distance too. | Run it with the VPN off, at another time and, if you can, on another network. |
| High average and high jitter | Slow and unsteady. | Start with your local network: a cable, being closer to the router, fewer devices in use. |
| Failed samples, or an error instead of a result | Some requests, or nearly all of them, didn't complete within 5 seconds. Being offline, a blocked connection or a busy server can look like this. It is not a packet-loss measurement. | Try again in a moment and check that you are connected. |
| A different number every time you run it | Normal to a degree: networks change from moment to moment. One run isn't a permanent measurement of your connection. | Run it several times at different moments and look at the spread. |
What the test can't tell you
- Your Internet ping to anything else. It measures the trip to the TryYourGear server only, whose location you can't choose.
- A speed. It doesn't measure download or upload speed.
- Where a delay appears. The total can't be split into your Wi-Fi, your provider and the route.
- Packet loss. Failed requests are shown, but they only mean a request didn't complete in time.
- An ICMP ping. It times an HTTP request made through the browser, so browser, HTTP and server processing time are inside the number.
- A permanent picture of your connection. One run is a snapshot of one moment.
TryYourGear doesn't store the results; as with any web request, the hosting provider may keep technical logs of it, which the Privacy Policy explains.
A practical way to use it
Run the test
Keep the tab in front and let it finish. Note the average, the minimum, the maximum and the jitter.
Run it again, two or three times
Do it at different moments if you can. A single run doesn't characterise a connection.
Compare the variability, not just the average
A steady result with low jitter matters more than one very low number.
Compare a cable with Wi-Fi, and check the VPN
Repeat the test on a cable if you can, and with any VPN or proxy off. Pause big downloads and streams while you test.
Use other tools when you need the whole picture
To diagnose a connection to a specific place, use that game's or service's own latency display, your operating system's
pingcommand to that address, or a dedicated speed and quality test. TryYourGear's test only answers for its own server.
Summary
- Latency is delay, RTT is a round trip and jitter is how much that delay varies. Bandwidth (Mbps) is a different thing.
- The Network Latency Test measures the round-trip time between your browser and the TryYourGear server: one warm-up and ten timed samples to
/api/ping, with average, minimum, maximum and jitter. - It is not your Internet ping, not a speed test and not a full diagnosis. The distance to the server, the route, congestion and Wi-Fi all shape the result.
- Repeat it, look at the variability and compare a cable with Wi-Fi. Use other tools for other destinations.