What is jitter on broadband?
Published by Pulse (SearchSwitchSave.com). Reviewed April 2026 by the UKSpeedTest editorial team led by Dr Alex J Martin-Smith.
Jitter is variation in delay. Even with good download speed, high jitter can make calls choppy and games inconsistent.
Why jitter matters
Real-time apps need stable timing. Jitter spikes can cause uneven voice, stutter, and short drops.
Common causes at home
- Busy Wi-Fi channels and distance from router.
- Background updates and cloud sync.
- Peak-time congestion patterns.
What to do next
Use Ethernet for one comparison run, pause other traffic, and repeat tests across times to find patterns.
Pulse measures download speed, latency, and jitter. Upload speed is not measured in the current release.
Related guides
Useful tools from the FBRE network
If you want a second opinion or next-step tools, try HowFast for an additional speed-check perspective, Laggy for latency-focused checks, Broadband Map for postcode availability context, and BroadbandSwitch.uk when you are comparing deals before switching.
You can browse the wider site list at FBRE.uk.
FAQ
Can high jitter happen with high Mbps?
Yes. A high download number does not guarantee smooth real-time apps. Jitter measures how much latency wobbles over time, which affects voice, video, and online games even when throughput looks strong on paper.
Does Ethernet help jitter?
Often yes, because Ethernet avoids Wi-Fi airtime contention and many sources of variability in the room. If jitter drops sharply on a wired test compared with Wi-Fi in the same time window, improving home wireless layout is a sensible next step.
Is jitter always an ISP fault?
No. Local Wi-Fi congestion, background uploads, VPNs, and busy household usage are common causes. Use fair repeat tests before assuming the street cabinet is the problem, and compare Ethernet against Wi-Fi to separate home factors from line factors.
What should I log for support?
Log the date and time, whether you used Wi-Fi or Ethernet, which room you tested in, and two or three results rather than a single screenshot. That pattern helps your provider reproduce the issue and avoids one-off spikes being treated as proof.