Jitter Test

Measure jitter, ping and lag spikes, then see if your connection is steady enough for games and calls.
Server Cloudflare, nearest data centre
  • Jitter–
  • Ping (median)–
  • Min – max–
  • Lag spikes–
  • Timeouts–
Each round tripMedianNo answer

Press start: the test sends a small request every 250 ms and draws each round trip.

Measured in your browser against Cloudflare's edge. Nothing is sent to us. A browser request adds a few ms to a raw ping; jitter is barely affected.

A jitter test measures how much your ping varies from one moment to the next. Under 10 ms of jitter is excellent, under 30 ms is good for calls and gaming, and above 50 ms voices break up and games lag. Press start to measure yours, with lag spikes (ping spikes), live.

What Is Jitter?

Network jitter is the variation in delay between packets: if one packet takes 20 ms and the next 60 ms, the 40 ms difference is jitter.

Two connections with the same 30 ms average ping: the steady one takes 30, 31, 29, 30, 30 and 31 ms, jitter 1 ms; the jittery one takes 15, 48, 22, 55, 18 and 24 ms, jitter 27 ms
Jitter is about how even the delay is, not how long it is.

Live audio, video and games send a steady stream of small packets and play them as they arrive. When the delay keeps changing, packets come in bunches and gaps: calls sound robotic or cut out, video freezes, and game characters jump or "rubber-band". Apps hide a little jitter with a buffer, which adds delay, so a steady connection matters as much as a fast one. Films and downloads don't care: they buffer seconds ahead.

Speed tests calculate jitter as the average difference between consecutive pings, the method this page uses. RFC 3550, the standard behind voice and video calls (RTP), uses the same differences, smoothed over time. Games such as Counter-Strike 2 and Deadlock show the same idea as "net jitter" to their own server.

What Is a Good Jitter?

Under 30 ms is good for almost everything; competitive gaming wants under 10 ms.

JitterRatingWhat you notice
Under 10 msExcellentNothing: fine for competitive gaming and HD calls
10–30 msGoodCalls and most games are smooth
30–50 msFairOccasional choppy audio, small stutters in fast games
Over 50 msPoorRobotic or cut-off voices, lag and rubber-banding
UseJitterPingSource
Competitive gamingUnder 10 msUnder 50 msCommon guidance for fast shooters
Microsoft Teams callsUnder 30 msUnder 100 ms round tripMicrosoft's network requirements for Teams
Voice over IP (VoIP)Under 30 msUnder 150 ms one wayCisco voice guidance; ITU-T G.114 for delay
Streaming, browsingNot criticalNot criticalPlayers buffer several seconds ahead

Jitter vs Latency vs Packet Loss

Latency is how long a packet takes, jitter is how much that time varies, and packet loss is how many never arrive.

What it measuresWhen it's badGood value
Latency (ping)Round-trip time to a serverEverything reacts late: delay in games, people talk over each otherUnder 50 ms
JitterHow much latency changes between packetsStutter, choppy audio, rubber-bandingUnder 30 ms
Packet lossShare of packets that never arriveGaps in calls, teleporting players, freezes0%
BandwidthHow much data per second the line carriesSlow downloads, low video qualityDepends on use

A fast plan doesn't guarantee low jitter: a 1 Gbps line on bad Wi-Fi can jitter more than a 50 Mbps line on a cable. Check your bandwidth and latency under load with the speed test, and read what latency is for ping in detail.

What Causes High Jitter?

Wi-Fi and a busy line cause most jitter; a VPN, mobile data and an overloaded router cause the rest.

  • Wi-Fi: walls, distance, neighbours' networks on the same channel and the crowded 2.4 GHz band make radio retries, which arrive late.
  • Bufferbloat: when someone uploads, streams or downloads a game, the router's queue fills and your packets wait in it for a varying time. The speed test grades it as "latency under load".
  • A VPN or a far server: a longer path through more networks, some of them busy.
  • Mobile, 5G home internet and satellite: the radio link changes all the time; jitter of 20 to 50 ms is common.
  • Background traffic: cloud backups, system updates, game launchers and cameras uploading video.
  • Old or overloaded router, and evening congestion at the internet provider.

How to Fix High Jitter

Test on a cable first: it tells you whether to fix your Wi-Fi or your line.

  1. Use Ethernet for a gaming PC, console or work computer. If you must use Wi-Fi, stay close to the router on 5 or 6 GHz, or add a mesh point.
  2. Stop what fills the line during calls and games: pause backups, uploads and big downloads, or schedule them at night.
  3. Turn on SQM or QoS in your router (often called "Smart Queue", "fq_codel" or "CAKE"). It keeps the queue short, which cures bufferbloat.
  4. Restart and update the router. If it's more than five or six years old, a new one often helps.
  5. Turn off the VPN or pick a nearby server, and choose the nearest region in games.
  6. Test at different times. Still high on a cable at quiet hours? Copy your results and send them to your provider: the history on this page keeps your last five tests.

Net Jitter in CS2 and Deadlock: What It Means and How to Fix It

"Net jitter" in Counter-Strike 2 and Deadlock means game data reaching the server or your PC too late or not at all, so the game misses ticks: you see rubberbanding, late hits and teleporting players.

  1. Show it in the game. Settings > Game > Telemetry: turn on the Network Problems display. Valve's telemetry HUD counts the ticks missed because data didn't arrive on time.
  2. Run this test on the same connection. High jitter or lag spikes here: the problem is your own connection, so start with the fixes above (Ethernet, nothing downloading, SQM).
  3. Low jitter here, net jitter in the game: this test measures the path to Cloudflare's nearest data centre, so a clean result points to the route to the game's servers or the servers themselves. Pick the nearest region; if many players report it at the same time, it's on the game's side and only waiting or reporting it helps.
  4. In CS2, try "Buffering to smooth over packet loss / jitter" in the game settings: it adds a little delay to hide small gaps, which can feel smoother on an unstable line.

How This Jitter Test Works

PartDetail
ServerThe Cloudflare data centre nearest to you, which serves this site; its airport code is shown above the results. The requests go to /cdn-cgi/trace, answered by Cloudflare's edge, not by our server.
SamplesOne small request every 250 ms for 15, 30 or 60 seconds (60, 120 or 240 round trips). A first request opens the connection and isn't counted.
TimingThe browser's Resource Timing API: from sending the request to the first byte of the answer, on a connection already open (no DNS or TLS setup). Browsers can't send ICMP pings, so the values are a few ms above a raw ping.
JitterAverage absolute difference between consecutive round trips. Ping: the median. Lag spike: a round trip at least 50 ms and twice above the median.
TimeoutsRequests without an answer within 2 seconds. Not packet loss: TCP resends lost packets, so loss shows as delay.
Not measuredPacket loss (needs UDP), jitter to a game server (the server's own network adds to it), and jitter while your line is busy (the speed test measures latency under load).
Your resultsNever sent to us. The last five stay in your browser's local storage; Clear history removes them.
Last verified22 November 2026

Frequently Asked Questions

What is jitter on a speed test?
It's how much your ping changes from one measurement to the next, in milliseconds. A speed test sends a series of small requests and averages the differences between consecutive round trips: 20, 22, 21 ms gives about 1.5 ms of jitter; 20, 60, 25 ms gives about 38 ms. Lower is better.
What is a good jitter?
Under 10 ms is excellent, under 30 ms is good for video calls and most games, 30 to 50 ms is noticeable, and above 50 ms calls break up and games lag. Microsoft asks for under 30 ms for Teams calls.
How much jitter is acceptable for gaming?
For fast competitive games, keep jitter under 10 ms with a ping under 50 ms. Casual and turn-based games stay playable up to about 30 ms of jitter. Lag spikes matter more than the average: one 300 ms spike in a firefight is felt even when the average jitter looks low, which is why this test counts them.
Why is my jitter so high?
Usually Wi-Fi (distance, walls, a crowded 2.4 GHz band), someone else uploading or streaming on the same line (bufferbloat), a VPN, or a mobile or satellite connection. Test once on a cable next to the router: if jitter drops, the cause is Wi-Fi; if it rises while others use the line, it's congestion.
What is net jitter in CS2 and Deadlock?
The games' telemetry HUD (Settings > Game > Telemetry) counts the ticks that arrive too late or not at all because of jitter or packet loss on the way between you and their server. Test here too: high jitter here means your own connection (often Wi-Fi), low jitter here but net jitter in the game points to the route to the game server or the server itself.
Does a VPN increase jitter?
Often a little: traffic takes a longer path through the VPN server, which is shared with other users. A nearby VPN server adds a few milliseconds; a busy or distant one can add tens. Run the test with the VPN on and off to compare.
Does this test measure packet loss?
No. Browsers can only send TCP requests here, and TCP resends lost packets, so a lost packet shows up as a delay (a lag spike), not as a loss. The test counts requests with no answer within 2 seconds as timeouts. A true packet loss test needs UDP; our ping test shows loss to any host from probes around the world.

Next steps

Related Tools

Speed Test
Download, upload, ping and latency under load.
Ping
Latency and packet loss to any host, from many countries.
Traceroute
Where on the route the delay comes from.
DNS Speed Test
Sites slow to start? Time your DNS.