Jitter test
Press Start and the test sends about 60 pings over 20 seconds, then shows your jitter: how much ping changes from one round trip to the next, on average. Under 10 ms is good for competitive gaming, and under 30 ms is fine for video calls. Higher than that, voices break up and movement in games feels uneven.
The test needs JavaScript.
- Jitter
- –
- Ping
- –
What jitter is
Every message across the internet takes a slightly different time. Jitter is how much that time varies. A connection with a steady 40 ms ping has low jitter. One that swings between 15 ms and 90 ms has high jitter, even though its average looks fine.
Jitter matters most for things that happen live. A video call sends a small packet of sound every few milliseconds, and each one has to arrive in time to be played. A game sends your moves many times a second. When packets arrive unevenly, the app either waits for the late ones (adding delay) or plays without them (choppy sound, skipping players). Downloads and streaming barely notice, because they fill a buffer first.
How we compute jitter
The test sends about 60 tiny HTTP requests to the nearest Cloudflare location, one after another, and times each round trip. Jitter is the average change between consecutive pings: take each ping, compare it with the one before, and average those differences.
A worked example with five pings:
| Ping | Round trip | Change from the one before |
|---|---|---|
| 1 | 20 ms | – |
| 2 | 22 ms | 2 ms |
| 3 | 19 ms | 3 ms |
| 4 | 35 ms | 16 ms |
| 5 | 21 ms | 14 ms |
The changes add up to 35 ms over four steps, so jitter is about 9 ms. Ping (the median of the five) is 21 ms.
This is the method used by Cloudflare's open-source speed test engine, which runs the test. Other tools compute jitter in other ways (some use the standard deviation, some the gap between the highest and lowest ping), so their numbers can differ from ours on the same line. Compare results from the same tool.
This page runs more pings than the ping test (about 60 against about 20). A longer run is more likely to catch the occasional spike that a short one misses. Like every ping on this site, these are HTTP round trips, not ICMP: browsers can't send ICMP. How it works has the details.
How much jitter is acceptable
These are our thresholds, the same ones the full test uses for its verdict:
| Use | Acceptable jitter | Why |
|---|---|---|
| Competitive gaming | 10 ms or less | Fast games update many times a second, so a swing of more than 10 ms is enough to make movement stutter or a shot land late. |
| Video calls | 30 ms or less | Call apps hold back a little audio to smooth out late packets. Past about 30 ms, that buffer runs out and voices break up or sound robotic. |
| Streaming and downloads | No limit | They buffer ahead, so uneven arrival doesn't matter. |
The test also shows ping. Low jitter doesn't save a high ping, and a low ping doesn't excuse high jitter: games and calls need both. Acceptable jitter goes through more examples.
What causes jitter
- Wi-Fi interference. Wi-Fi shares the air. Other networks on the same channel, a microwave, Bluetooth devices, thick walls and distance all make the router resend packets, and each resend adds a few milliseconds at random. Wi-Fi is the most common cause of jitter at home. Compare a run on Wi-Fi with one on a cable to see how much of yours it causes (Wi-Fi vs Ethernet).
- Bufferbloat. When something else uses the connection, such as a game download, a cloud backup or a 4K stream, the router queues packets. Some of yours wait behind the queue and some don't, so ping jumps around. Run the bufferbloat test to grade it.
- A busy line. In the evening, when many people in the area are online, the shared parts of cable, 5G home internet and satellite networks get crowded. Jitter often rises then and falls late at night.
- Weak mobile or satellite signal. Cellular and satellite links change speed as signal changes, which shows up as jitter. Our guides for T-Mobile home internet and Starlink cover those.
- Background apps. Updates, cloud sync and other tabs on the same device compete for the connection.
Reading your result
- Jitter under 10 ms: steady. If games or calls still have problems, check ping and packet loss with the lag test.
- 10 to 30 ms: fine for calls, a little uneven for fast games. A cable instead of Wi-Fi often brings it down.
- Over 30 ms: calls will stutter. Test again on a cable with nothing else running. If it drops, the cause is in your home (Wi-Fi or bufferbloat). If it stays high, it's the line or your provider.
Jitter changes from minute to minute, so one result is a snapshot. Run the test a few times, and run it while the problem is happening. Our guide to high ping and jitter on Wi-Fi lists the fixes in order.
Sources
- Cloudflare speed test engine (@cloudflare/speedtest), README: jitter is the average distance between consecutive latency measurements (checked November 2026)