Reading a stability trace
What latency, jitter and loss mean, and which patterns point to your Wi-Fi, your provider or the device itself.
What the test records
The connection stability tester asks BenchDevice's server for a one-byte file four times a second and times every answer, for one, five or fifteen minutes. An answer that has not arrived after two seconds counts as lost. While it runs you see a strip chart, one bar per round trip with the newest on the right, and red marks where requests were lost. When it ends you get a set of numbers. This guide is about reading both.
The three words
Latency is how long one round trip takes: your request out to the server and its answer back, in milliseconds. The results show four views of it: the fastest, the typical (median), the slow one (the 95th percentile, which only one request in twenty was slower than) and the slowest. The median is your everyday experience. The 95th percentile is what you feel when things hiccup.
Jitter is how much the latency wobbles. The test takes each pair of consecutive answered round trips, measures the gap between them, and averages those gaps. A round trip that is the same every time has almost no jitter, however long it is; one that swings between a low and a high value every few requests has a lot, and that is what makes voices stutter and games rubber-band.
Loss is the share of requests that got no answer in time. The results give the count and the percentage, and the longest drop: the longest run of lost requests in a row, in seconds. Isolated losses happen on any connection; a long drop is a different thing: for that long, your connection was simply not there.
What is normal
The tool gives numbers only and does not judge them. What the numbers mean for you depends on what you do, which is why the tool does not grade them. A good way to get a feel for your own line is to run the test at a quiet hour and again at a busy one, and compare the medians, the jitter and the longest drop between the two runs.
Patterns and what they point to
A flat trace with spikes. The median is fine but tall bars appear now and then, sometimes with a lost request beside them. This is the signature of Wi-Fi: a weak signal, a crowded channel, a microwave oven, a neighbour's network on the same frequency. Run the test again on a cable to the router. If the spikes vanish, the radio is the cause.
Slow steps up and down. The bars climb over a few seconds, stay high, then fall back. Something on your network is downloading or uploading, and the queue in your router is filling: that is bufferbloat. The bufferbloat tester measures this directly, and its guide says what to do about it.
A regular rhythm. Spikes that come at the same interval every time usually have a device behind them: a laptop's power saving on Wi-Fi, a phone backing up photos, a smart speaker checking in. Turning devices off one at a time finds the culprit.
Long drops. Runs of red marks lasting several seconds. If they appear on cable as well as Wi-Fi, the line itself is dropping: a modem re-syncing, a provider's fault, or a cable or connector that has seen better days. Note the time and length of the drop; a provider's support line can match it against their logs.
High everywhere, no pattern. A high median with high jitter even on cable, at any hour, points past your house to the provider or the path they use to reach the wider internet. A mobile or satellite connection also looks like this by nature.
A test that pauses. If you switch to another tab the test pauses, says so, and goes on when you come back. The results count those pauses; they are not drops.
Telling the parts apart
A browser cannot see your Wi-Fi signal, your channel, or which hop adds the delay. But you can isolate the parts with two runs. First on Wi-Fi where you normally sit; second on a cable to the router, with the same length. Whatever disappears in the second run belonged to the Wi-Fi. Whatever stays belongs to the router, the line or the provider. If you can, run a third from a different device on the same cable: if that one is clean, the first device, its drivers or its own software was the problem.
What to do next
For Wi-Fi faults, move closer, switch to the 5 GHz band, change channel, or run a cable where you can. For bufferbloat, read the bufferbloat guide and look for Smart Queue Management in your router. For drops and high latency on cable, restart the modem once, check the cables, and if it continues, take the test's numbers and times to your provider.