I used to stare at a 22ms ping in the corner of my screen during Valorant matches and get confused about why I’d still lose duels I should’ve won. On paper, 22ms is excellent — pro players compete at under 15ms, and anything under 50ms is considered great for ranked play. But I was still getting rubberbanded mid-fight, watching enemies teleport a few feet, and eating bullets that should’ve missed. The ping number was lying to me, or at least telling me half the story.
The number that actually explained what I was feeling wasn’t ping. It was jitter — how much that ping bounces around from packet to packet. And once I started watching that instead, the “why does my connection feel fine on paper but terrible in-game” mystery stopped being a mystery.
Ping is a single number. Jitter is the story behind it.
Ping measures the round-trip time of one packet at one moment. Jitter measures how much that round-trip time varies over time. A connection can report a great average ping and still be jittery as hell, because the average smooths out the spikes. Two connections with the same average ping can feel completely different to play on if one is stable and the other isn’t.
This matters more than it sounds like it should because of how games actually handle your connection. Most online games use prediction and interpolation to hide latency — they guess where you and other players will be a few milliseconds from now, and smooth the visuals accordingly. That system works well when latency is consistent, because the guesses are close to reality. It falls apart when latency jumps around, because the game’s prediction keeps getting it wrong, and you see the correction as rubberbanding, snapping, or a hit that should have landed but didn’t.
The comparison that actually proves it
Here’s the version of this that convinced me to stop obsessing over shaving a few milliseconds off my average ping: a connection running 20ms average ping with 15ms of jitter plays noticeably worse than a connection running 25ms average ping with 1ms of jitter — even though the second one has a higher number on the scoreboard. A rock-stable 80ms connection will outperform a connection that swings between 40ms and 150ms, because the swinging is what breaks hit registration, not the baseline number.
That’s a hard thing to accept if you’ve spent years treating ping as the only stat that matters, but it lines up with what most competitive players actually notice: it’s never the “high ping” games that feel the worst to play, it’s the games where the number keeps jumping.
Why Wi-Fi hides this problem until it doesn’t
This is where the Wi-Fi versus Ethernet debate actually gets interesting, because the raw ping difference between the two is smaller than people assume. Wired Ethernet with a decent Cat 6 cable typically runs 1-3ms of latency with close to zero jitter. Wi-Fi 6 averages somewhere around 3-7ms under normal conditions — a gap of a few milliseconds that most players would never notice in isolation.
The real difference shows up under contention. Wi-Fi has to share airtime with every other device on the network and deal with signal encoding and retransmissions, so the moment someone else in the house starts streaming, downloading, or a smart-home device wakes up and starts chattering, your jitter spikes even though your average ping barely moves. Ethernet doesn’t have that problem, because it’s not sharing a wireless medium with anything. That’s why “my speed test says everything’s fine” and “my game feels like garbage right now” can both be true at the same time — the speed test measures average throughput and latency, not the jitter spikes caused by momentary contention.
How to actually check your jitter, not just your ping
Most built-in game network stats (CS2’s net_graph, Valorant’s stats overlay) only show current ping, not variance over time, so you have to go looking for it specifically.
1. Run a jitter-specific test, not a standard speed test
A regular speed test gives you one ping number from one moment. Tools built around gaming latency testing will show ping over a rolling window and report jitter as its own number — that’s the one to watch, not the average.
2. Watch your ping during a normal play session, not an idle test
Jitter caused by household contention only shows up when the contention is actually happening. Testing your connection at 3am when nobody else is using the network will look great and tell you nothing about what happens during your actual play window in the evening.
3. If you’re on Wi-Fi, isolate the variable before blaming your ISP
Before assuming your internet plan is the problem, check whether your jitter spikes correlate with other devices being active on the same network. If they do, the fix is a wired connection or better Wi-Fi channel management, not a faster internet plan — a faster plan doesn’t reduce jitter caused by wireless contention.
What this means for your setup
If you’re chasing a lower ping number and still losing fights you shouldn’t, the fix probably isn’t a faster internet plan. It’s stability. A wired connection will almost always beat Wi-Fi for competitive play, not because the ping difference is huge, but because it removes the jitter caused by sharing a wireless medium with every other device in your house. If running Ethernet isn’t practical, the next best thing is reducing contention on your Wi-Fi network during play sessions — pausing large downloads, moving smart-home traffic to a separate band if your router supports it, and playing on 5GHz rather than 2.4GHz where possible.
None of this requires spending money before you’ve confirmed it’s actually your problem. Watch your jitter for a few sessions first. If it’s spiking specifically when other devices are active, you’ve found your answer, and a cable will fix more of your losses than a new router will.
Why this looks different in different games
Jitter doesn’t hit every game the same way, because not every game leans on prediction equally hard. Fast-twitch shooters like Valorant and CS2 are especially sensitive because hit registration depends on the server and client agreeing on exactly where a player was at a precise moment — a jitter spike right as you pull the trigger is exactly when a shot that should’ve connected doesn’t. Slower-paced games, strategy titles, or anything turn-based barely notice jitter at all, because there’s no split-second interaction depending on perfectly consistent timing. That’s part of why the “just check your ping” advice feels incomplete to competitive FPS players specifically — it’s the genre where variance actually costs you rounds, not just average latency.
FAQ
Is jitter more important than ping for competitive gaming?
For most competitive play, yes. A stable connection with a slightly higher average ping consistently outperforms an unstable connection with a lower average ping, because games rely on prediction systems that only work well when latency stays consistent.
What’s a good jitter number for gaming?
Under 5ms of jitter is considered excellent and won’t meaningfully disrupt prediction systems. Jitter in the 10-15ms range or higher is where players start noticing rubberbanding and inconsistent hit registration, even if the average ping still looks acceptable.
Does Wi-Fi 6 have worse jitter than Ethernet?
Under light network load, the gap is small. Under contention — other devices streaming, downloading, or active on the same network — Wi-Fi jitter spikes noticeably because of shared airtime and retransmissions, while wired Ethernet stays stable since it isn’t sharing a wireless medium with anything.
