Results
Waiting
Measure the latency, jitter and packet loss on the connection you are using now. The test sends a stream of small packets to our server at the rate a voice call does, and tells you whether any loss is on the way up or the way down.
Waiting
The packets travel over WebRTC, the same technology as browser-based calls, without retransmission, so a lost packet stays lost just as it would on a call. If your network blocks it, the test falls back to timing ordinary web requests, which measures latency and jitter but cannot see packet loss. To compare idle latency with a busy connection, run the bufferbloat test. For packet-size problems that make large transfers hang, run the MTU and CGNAT test.
Jitter is the variation in delay between packets that should arrive evenly spaced. A call sends a packet every 20 ms; if one arrives after 25 ms and the next after 60 ms, the receiving end must either hold audio in a buffer to play it smoothly, which adds delay, or drop the late packets, which sounds choppy. This test sends packets at that same 20 ms rate and reports jitter as the average difference between successive round trips. Wi-Fi interference, a congested line and a busy router are the usual causes; a wired connection often steadies it.
Packet loss is the share of packets sent that never reach the other end. Web pages and downloads resend what is lost, so there it shows up as slowness; calls, video and games cannot wait for a resend, so the gap is heard or seen. The test sends 250 numbered packets and our server counts how many reached it, which tells loss on the way up from loss on the way down. Loss only on the upload often points to a busy uplink or Wi-Fi near you.
These are the bands this test uses for its findings. They are general guidance for everyday use, not an industry standard and not a Netavo service guarantee; a particular game or calling service may need more or tolerate less.
To check DNS, IPv6, packet size and website reachability at the same time, run the full Connection Health Check.
On a wired UK connection, a ping under 30 ms is excellent and under 100 ms is fine for calls and most games. At 100 ms or more, callers notice a delay. This is general guidance, not a Netavo guarantee.
Under 15 ms is low, 15 to 30 ms is moderate, and 30 ms or more is high enough that calls may sound choppy. Wi-Fi and a busy line are the usual causes.
None is the aim. Loss below 1% is usually tolerable on calls; 1% or more is noticeable on calls and video. The Netavo ping test also shows whether the loss is on your upload or your download.
Some networks block the UDP packets the test sends, so it times ordinary web requests instead. Those resend lost packets, so latency and jitter are measured but packet loss cannot be.
We run our own network, broadband and hosted voice, engineered for low latency and no loss.