Ping vs latency vs jitter
Latency is the delay in getting data from one point to another. Ping is the round-trip measurement of that delay, and in everyday use the two words mean the same thing. Jitter is how much the number varies between measurements — and for calls and gaming, high jitter is usually worse than a high but steady ping.
The three numbers side by side
| Term | What it measures | Good value | What bad looks like |
|---|---|---|---|
| Latency | Delay for data to travel to a server (one way) | Under 25 ms | Everything feels a beat behind |
| Ping | The same delay measured as a round trip, there and back | Under 50 ms | Lag in games and calls |
| Jitter | How much ping varies between consecutive measurements | Under 30 ms | Robotic audio, frozen video, rubber-banding |
| Packet loss | Share of packets that never arrive at all | 0% | Words dropping out, sudden disconnects |
Ping is roughly twice the one-way latency, which is why the two get used interchangeably even though they aren't quite the same measurement.
Step by step
- 1Run a ping test. Use the tool below. It reports the round-trip time for each request, which is your ping.
- 2Read the average for latency. The average across all requests is the number people mean when they say "my latency." Halve it for a rough one-way figure.
- 3Read the spread for jitter. Subtract your best reading from your worst. That gap is your jitter — under 30 ms is healthy, over 50 ms will be audible in calls.
- 4Watch for missing responses. Requests that never return are packet loss. Even 1–2% is enough to break a video call, no matter how good the average ping looks.
- 5Repeat on Wi-Fi and wired. Jitter is usually a Wi-Fi problem. If a cable flattens the spread, interference or distance from the router is the cause.
Measure all three now
Round-trip latency to our server
—
Averages 5 requests. Browser security prevents true ICMP ping, so this measures HTTP round-trip time — a close, practical equivalent.
What the result means
A single ping number hides the thing that usually causes trouble. Two connections can both average 60 ms: one delivers every packet at 58–62 ms and feels perfect, the other swings between 15 ms and 200 ms and makes voices break up. The average is identical; the experience is not.
This is why real-time apps buffer. A video call absorbs jitter by holding a fraction of a second of audio in reserve, which is why bad jitter shows up as robotic or delayed speech rather than as an obvious "slow" connection. Reducing jitter almost always means fixing Wi-Fi or removing something saturating your uplink.
Frequently asked questions
Are ping and latency the same thing?
In practice yes. Strictly, latency is the one-way delay and ping is the round-trip measurement of it — so ping is roughly double the latency — but almost everyone uses the words interchangeably.
What causes jitter?
Wi-Fi interference, distance from the router, congested ISP links, and other devices saturating your connection. Anything that makes packets queue for varying amounts of time produces jitter.
What is a good jitter?
Under 30 ms is fine for calls and gaming. Under 10 ms is excellent. Above 50 ms you'll hear audio break up and see video freeze even if your average ping looks acceptable.
Is jitter worse than high ping?
Often, yes. A steady 120 ms ping is usable for calls; a ping averaging 60 ms but swinging by 150 ms is not, because applications can't predict when data will arrive.
Does packet loss affect ping?
Packet loss is measured separately, but it makes the effects of latency far worse. Lost packets have to be resent, which adds delay on top of your baseline ping.