Latency versus jitter: the two numbers behind a responsive connection
Learn the difference between network delay and variation, why both matter, and how they affect gaming, calls, browsing, and streaming.
Bandwidth tells you how much data a connection can move. Latency and jitter tell you what that movement feels like in real time.
You can have a very fast download result and still notice delayed reactions in a game or choppy conversation on a call. Usually, that is where these two measurements enter the story.
Latency is delay
Latency is the time required for data to travel to another point and for a response to come back. It is usually measured in milliseconds and often called ping.
Distance matters because signals cannot travel instantly. Routing matters because internet traffic does not always take the shortest geographic path. Local Wi-Fi, a busy router, a VPN, and congestion can add more waiting along the way.
Lower latency usually feels more immediate:
- A website begins responding sooner.
- A game registers an action sooner.
- Conversation has less awkward overlap.
- Remote desktops feel closer to a local computer.
There is no single perfect latency number for every task. A reading that feels excellent for browsing may still be noticeable in a competitive game, while a slightly higher but stable reading can work perfectly well for streaming.
Jitter is variation
Jitter describes how much latency changes from one sample to the next. Imagine several round trips measuring 20 ms, 21 ms, 19 ms, and 20 ms. That is stable. Now imagine 20 ms, 85 ms, 23 ms, and 140 ms. The average may hide the real problem: packets are arriving on an unpredictable schedule.
Real-time apps dislike that unpredictability. Voice and video systems can buffer a small amount of variation, but large or frequent spikes can create pauses, robotic audio, or dropped frames. Games may show rubber-banding even when the normal ping looks fine.
Why jitter appears
Common causes include crowded Wi-Fi channels, weak signal, a router handling more traffic than it can comfortably queue, mobile network changes, and another device suddenly using the connection. A large upload can also create delay if the router lets a long queue form ahead of small interactive packets.
This queue-related delay is commonly discussed as bufferbloat. It explains why an idle connection can show a nice ping while the same connection feels terrible during a large transfer.
Reading both together
Treat latency as the baseline wait and jitter as its steadiness. Low and stable is ideal. Higher but stable can still be usable. Low most of the time with frequent large spikes often feels worse than the average suggests.
When troubleshooting, run a few tests and watch for patterns:
- Compare Wi-Fi with Ethernet.
- Pause backups and large uploads.
- Move closer to the access point.
- Test at quiet and busy times.
- Compare with and without a VPN.
IP Frog shows both measurements because a connection is more than its biggest Mbps number. For the other half of the picture, see how download and upload differ.