Jitter Test
Measure how stable your network latency is over time. High jitter causes choppy voice calls, video stutters, and lag spikes in gaming — even when your average ping looks fine. This tool sends the same kind of browser-based HTTP requests as our ping test — see that page for how latency measurement from a browser actually works.
Live latency waveform
Latency (ms)
Jitter delta (ms)
80
60
40
20
0
Click Start Test to see your waveform
0s
5s
10s
15s
20s
--
Avg jitter
--
Max jitter
--
Avg ping
--
Min ping
--
Packet loss
Sample history
Sample results will appear here as pings complete
Jitter quality guide — what your result means
< 10ms
Smooth — excellent for everything
Voice calls, video conferencing, and competitive gaming all feel perfectly stable at this jitter level.
10–20ms
Good — good for most uses
Video calls stay clear. Casual gaming is fine. Competitive players may notice occasional input inconsistency.
20–50ms
Rough — noticeable in calls
Voice calls start to break up. Video stutters. Gaming shows lag spikes. Check your Wi-Fi and router.
> 50ms
Poor — calls drop, games lag
VoIP calls become unusable. Video disconnects. Gaming is severely impacted. Investigate router and ISP.
What causes high jitter
Wi-Fi interference
The most common cause. Neighbouring networks on the same channel, microwave ovens, and Bluetooth devices all cause packet retransmissions that spike jitter dramatically.
Overloaded router
A router with too many connected devices or an outdated CPU queues packets unevenly. This creates bursts of delay that show up as high jitter even when average ping is low.
Network congestion
ISP congestion during peak hours causes variable queuing delays. Packets waiting longer in the queue create jitter spikes that correlate with evening usage peaks.
VPN overhead variability
OpenVPN processing times are inconsistent under load, adding variable encryption delay. WireGuard is significantly more consistent due to its simpler kernel-level implementation.
Background processes
Active downloads, cloud sync, or video streaming competing for bandwidth cause variable packet delivery times — raising jitter without necessarily raising average ping.
Long network paths
More hops between you and the server means more chances for variable queueing delays. Geographically distant servers almost always show higher jitter than nearby ones.
Ping vs jitter — why you need both numbers
Ping (latency)
Average time for one round-trip
Measures raw speed of your connection
Low ping ≠ stable — can still have high jitter
Example: 22ms average ping
Jitter (variance)
Difference between consecutive ping values
Measures stability of your connection
High jitter causes choppy calls even at low ping
Example: jumps 18ms to 38ms and back
What the waveform doesn't tell you at a glance
Jitter is a more nuanced metric than a single number suggests. These are the mechanics behind the numbers on this page — how they're actually calculated and what typically causes them.
Not every tool calculates "jitter" the same way
The telecom standard for jitter (RFC 3550, used for RTP/VoIP) defines it as a smoothed running average of the absolute difference between consecutive packet delays — not a simple standard deviation or a raw max-minus-min spread, which is what many consumer speed-test sites actually compute and label "jitter." The two numbers can differ meaningfully on the same connection. This tool's waveform shows both the raw latency line and the consecutive-delta line so you can see the actual variation pattern rather than trusting a single averaged figure.
Bufferbloat, not congestion, is usually what's really spiking your jitter
Most home routers and ISP modems queue far more packets than they should before dropping any — a problem known as bufferbloat. Under light load this is invisible, but the moment something starts a large upload or download, packets queue up behind it and your other traffic's delay becomes wildly inconsistent, even though your raw bandwidth hasn't changed. This is the actual mechanism behind "background processes raise jitter" — the fix is enabling Smart Queue Management (SQM) or Active Queue Management (AQM) on a router that supports it, not just closing the offending app.
A TCP-mode VPN can turn one dropped packet into a jitter spike
VPN protocols that tunnel over TCP (some OpenVPN configurations) inherit TCP's head-of-line blocking: if a single packet is lost, every packet behind it in that TCP stream has to wait for retransmission before any of them are delivered, even ones that arrived fine. This means a single, isolated packet drop can produce a jitter spike far larger than the drop itself would suggest. UDP-based tunnels (WireGuard, and OpenVPN in UDP mode) don't have this problem — each packet is independent.
A jitter buffer is why a "Rough" score doesn't always sound as bad as it looks
VoIP and video-call apps don't play incoming audio the instant it arrives — they hold a small buffer of upcoming samples and release them at a steady rate, absorbing network jitter at the cost of a little extra latency. A larger buffer smooths out more jitter but adds delay; a smaller one is more responsive but more prone to audible glitches. This is why two people on the same "Rough" connection can have very different call experiences depending on their app's buffer settings.
One big spike isn't the same thing as consistently high jitter
Average jitter and maximum jitter measure different problems. A single 200ms spike from a brief Wi-Fi interruption barely affects your average if the rest of the test was smooth, but it can still cause one audible glitch in a call. Consistently elevated jitter across the whole sample — visible as a wide, busy waveform rather than one tall spike — points to an ongoing structural issue like bufferbloat or Wi-Fi contention rather than a one-off event.
Frequently asked questions
“What's a good jitter score for gaming vs. video calls vs. voice calls?”
Under 10ms is smooth for everything. 10–20ms is fine for video calls and casual gaming, with competitive players occasionally noticing input inconsistency. Above 20ms, voice calls start to audibly break up and gaming shows visible lag spikes — voice tends to tolerate jitter worse than video because there's less buffering headroom before delay becomes noticeable mid-sentence.
“Why is my jitter high even though my ping looks fine?”
Ping measures average speed; jitter measures how consistent that speed is. A connection can average a fast 20ms while still swinging between 10ms and 50ms sample to sample — the average looks great, but the swings are exactly what causes choppy calls and gaming lag. This is the entire reason jitter is tested separately from ping.
“Is jitter measured the same way by every speed-test tool?”
No, and the differences are meaningful. The telecom standard (used for VoIP/RTP) defines jitter as a smoothed average of consecutive packet-delay differences. Some consumer tools instead report standard deviation or a raw max-minus-min range across the whole test — both are valid ways to describe variability, but they produce different numbers from the same raw data, so jitter scores aren't always directly comparable across different sites.
“Does switching from 5GHz to 2.4GHz Wi-Fi change my jitter?”
Often significantly. 2.4GHz has fewer non-overlapping channels and is more likely to be shared with neighbouring networks and other devices, causing more contention-related delay variance. 5GHz (and 6GHz on newer routers) typically has less interference and more available channels, which usually shows up as lower, more consistent jitter — though 5GHz has shorter range, so distance from the router matters too.
“Can a VPN increase my jitter even if it doesn't change my ping much?”
Yes. VPN jitter comes less from encryption speed and more from how the protocol handles a lost or delayed packet. TCP-mode tunnels can turn a single dropped packet into a cascading delay for every packet behind it. WireGuard and UDP-mode OpenVPN don't have that problem, which is why they typically show noticeably more consistent — not just faster — results. See the VPN speed comparison tool to check this directly.
“What is a jitter buffer, and does it fix bad jitter?”
A jitter buffer is a short delay that calling and streaming apps add on purpose, holding incoming data briefly so it can be played back at a steady rate instead of exactly when it arrives. It doesn't fix the underlying network instability, but it hides moderate jitter from you at the cost of a small amount of extra latency — which is why call quality can hold up reasonably well even on a "Rough" connection, up to a point.
“Why did my jitter spike briefly during the test but come back down?”
A short, isolated spike usually reflects a one-off event — a Wi-Fi retransmission, a brief burst of background traffic, or a single congested hop — rather than an ongoing problem. Check the average jitter figure and the shape of the waveform rather than reacting to a single sample: a narrow single spike is a very different situation from a consistently wide, busy waveform.
“How do I actually fix high jitter?”
Start with the most common cause: switch to a wired Ethernet connection or move to 5GHz Wi-Fi to rule out interference. If it persists under load specifically, look into enabling Smart Queue Management (SQM) on your router to address bufferbloat. If you're on a VPN, check whether it's running in TCP or UDP mode — UDP is more jitter-resistant. Run the test again after each change to confirm it actually helped rather than guessing.