What is jitter and how do you reduce it?

Ping is the round-trip time of one packet. Jitter is how much that time varies from packet to packet. Technical documents such as RFC 8802 define the concept as delay variation.

Make it concrete. Picture two connections: the first sits steadily around 45 ms for a whole match, the second keeps jumping between 25 and 90 ms. The second may even show a lower average, yet the game almost always feels better on the first.

That is because game engines are built around updates arriving at regular intervals. When packets come fast, then slow, the engine struggles to present movement in a smooth order.

Jitter does not announce itself as sharply as packet loss; it registers as inconsistency. Do the same thing twice and you get two different responses. While aiming, an opponent's position may be corrected in small jumps.

In competitive games this directly disrupts muscle memory. Your brain adapts to a given delay; when that delay keeps changing, the adaptation never forms.

Some games report jitter directly — Overwatch 2 and Rocket League's network performance readouts among them. In games that do not, watch the ping value for a while and look at the gap between its lowest and highest readings.

A continuous ping test from the Windows command prompt also gives an indication: the spread in round-trip times to the same target is a rough proxy for jitter. Note that if you target a general host rather than the game server, you are only measuring your home connection's stability.

Whichever method you use, run it for at least a few minutes. A short sample can miss the fluctuation entirely.

Wi-Fi comes first. A wireless link shares a medium; neighbouring networks, walls and distance all make packet arrival times irregular. Jitter can be high even when the signal bars look full.

Second is a saturated home connection. While one device uploads a large file, game packets wait in a queue, and because that queue's length changes moment to moment, the delay fluctuates. This is most pronounced when the upload direction fills up.

Third is congestion along the route. As specific network exchanges fill up in the evening, packets wait for varying amounts of time. In that case jitter appears only at certain hours and toward certain destinations.

The first and most effective step is a cable. A short Ethernet test either removes Wi-Fi-induced fluctuation entirely or takes it off the table. If you cannot use a cable, move closer to the access point and remove walls from the path.

The second step is emptying the connection. Stop large downloads, cloud backups and streams. If your router supports smart queue management, that is genuinely worth investigating for upload-induced jitter.

If neither helps and jitter persists only on specific game servers, the problem may sit on the route. An alternative path can deliver more regular arrival times — but if it does not, the correct decision is not to connect.