📡 Ping & Jitter Test (Detailed)
Run 15 rapid latency samples and see your average ping, jitter, and packet loss, with a full sample-by-sample breakdown.
Sample-by-sample results
| # | Latency | Status |
|---|
About Ping & Jitter Test (Detailed)
This is a more thorough version of a latency test: it fires 15 rapid round-trip requests at a test server in quick succession and reports the average ping, the jitter (how much those samples varied), and the packet loss rate (how many requests failed to get a response), along with a table showing every individual sample. Where the basic ping test gives you one summary number, this gives you the underlying data so you can see whether a high average was caused by one bad spike or by consistently elevated latency.
The per-sample table is genuinely useful for troubleshooting rather than just headline numbers: a connection with one outlier sample and 14 fast ones points to a brief, transient hiccup, while steadily climbing or erratic samples point to an ongoing problem worth investigating further — congestion, a failing piece of hardware, or Wi-Fi interference. This level of detail is closer to what a network engineer would look at than a simple pass/fail speed check.
As with the other latency tools here, this measures round-trip time over HTTPS rather than raw ICMP, since browsers can't send true ping packets — 15 samples is enough to average out normal random variation without making you wait long for results. Run it again if the first pass shows something unexpected, since a single bad sample can happen for reasons unrelated to your connection, like the test server briefly being under load.
Frequently asked questions
Why 15 samples?
Enough samples smooth out random spikes so the average, jitter and loss figures reflect your real connection rather than a single lucky or unlucky moment.
Is this the same as a command-line ping?
It's similar but not identical — browsers can't send raw ICMP pings, so this measures round-trip time for small HTTPS requests instead, which is a very close real-world proxy.
What does the packet loss column in the results table mean?
It flags which of the 15 individual samples failed to get a response at all, as distinct from samples that responded slowly — loss and high latency are different problems and this breakdown lets you tell them apart.
Why might jitter be high even if average ping looks fine?
Averages can hide instability — a connection alternating between 15ms and 65ms can average out to a normal-looking 40ms while still producing the high jitter that causes choppy calls.
Is 15 samples enough to diagnose an intermittent problem?
It's enough to catch a problem that occurs frequently, but a truly rare or periodic issue (like a router dropping connection every few minutes) may not show up in one run — running the test several times over a longer period gives a more complete picture.