Search "why does my game lag" and you'll run into a wall of jargon — ping, packet loss, jitter — but almost nothing explains which one causes which kind of "lag." Understanding the difference is what lets you actually read a test result and know what to fix.
Ping (latency): how long a round trip takes
Latency is the time it takes for a data packet to travel from your device to a server and back, measured in milliseconds (ms). Lower is faster response.
- Under 30ms: essentially imperceptible — ideal for anything requiring fast reactions.
- 30-80ms: solid experience in most games; competitive titles might feel a hair behind.
- 80-150ms: playable, but fast-paced competitive games will feel noticeably delayed.
- Above 150ms: most real-time games start to feel actively affected.
Ping is the most talked-about number, but it's only one of three metrics that matter — low ping doesn't guarantee smooth gameplay, and the two below are often the hidden culprits.
Packet loss: did the data actually make it there
Network data is sent in small pieces called packets, and packet loss is the percentage of those packets that never arrive. Even with low latency, occasional packet loss shows up as your character "teleporting," a skill that doesn't fire, or a sudden freeze followed by a snap back to normal — that stutter is often packet loss, not latency.
So how much packet loss is normal? Start with the tool's resolution. PartyPing sends 20 packets in the first pass, so one loss would equal 5%. Any loss triggers two more passes, expanding the final sample to 60 packets. The result can then move only in roughly 1.67-point steps; it cannot honestly distinguish 0.5% from 1%. Under PartyPing's current rating:
- 0%: packet loss does not lower the verdict.
- More than 0% but less than 5%: the verdict is capped at Playable, and a retest is recommended.
- 5% to under 10%: the verdict is capped at Laggy.
- 10% or more: the verdict is Unplayable; investigate the local network or try another region.
These steps describe PartyPing's measurement resolution and rating, not an official threshold shared by every game or the exact packet-loss figure from a game client. Loss is random, so repeat the test during your actual play hours before judging a route; see Are Ping Test Results Accurate? for how confirmation works.
Jitter: stability matters more than the raw number
Jitter is how much your latency fluctuates — 30ms one second, then a sudden jump to 120ms the next. Games generally care more about stability than about hitting the lowest possible number: a connection steady at 60ms usually feels better than one averaging 40ms but occasionally spiking to 150ms.
You can't judge jitter from a single average — you need to look at the distribution: where most of the latency lands, and how high the occasional spikes go. A tool that only reports "average latency" hides this kind of instability completely.
How to read all three together
Looking at any one metric alone can lead you to the wrong conclusion:
| Situation | Likely feel | What to check |
|---|---|---|
| Low latency, low packet loss | Smooth | — |
| Low latency, occasional packet loss | Random teleports, brief freezes | Packet loss |
| Latency isn't bad, but fluctuates a lot | Persistent choppy stutter | Jitter / latency range |
| High latency, but stable | Feels a bit slow but not choppy | Raw latency |
So judging whether a network path is actually good means looking at the latency number, its fluctuation range, and packet loss together — not just one number in isolation.
How to test it yourself
No dedicated client needed — your browser is enough. Hit the button at the end of this article: within seconds you get a latency range (not a single number) and packet loss for regions worldwide, with no account required.
Testing with a group and want a region that works for everyone? See How to Pick the Best Server Region for a Whole Group (in 5 Minutes).
Next time you look at a test result, don't just fixate on the latency number — packet loss and jitter matter just as much.