There is a specific kind of frustration in seeing a speed test report 200 Mbps and then watching a video call turn into a slideshow. It feels like a contradiction, but it is not: bandwidth and responsiveness are different properties of a connection, and a speed test measures both. Most people only read the first number.
Bandwidth is width, latency is delay
The standard analogy is a road, and it holds up well. Bandwidth — your Mbps figure — is how many lanes the road has. It determines how much data can arrive at once, which is what matters for downloading a large file or streaming high-resolution video.
Latency — your ping, measured in milliseconds — is how long it takes one car to make the trip. It determines how quickly the connection responds. Adding lanes does not make the journey shorter, which is exactly why upgrading from 100 to 500 Mbps does nothing for a laggy game.
The three numbers that govern how a connection feels
Ping (latency)
The round-trip time for a single packet. Under 20 ms is excellent, 20-50 ms is good and fine for nearly everything, 50-100 ms is noticeable in fast games but acceptable for calls, and over 150 ms makes real-time interaction genuinely difficult. Physical distance sets a floor here — a server on another continent cannot respond quickly no matter what you pay.
Jitter
How much your ping varies between packets. This is the number almost nobody looks at and the one that most often explains bad calls. Live audio and video have to be played back at a steady rate, so the receiving end buffers a little and assumes packets will keep arriving on schedule. When arrival times are erratic, that buffer runs dry, and you get the robotic voice, the frozen frame, the half-second of silence.
Under 5 ms is excellent, under 20 ms is fine for calls and most gaming, and consistently over 30 ms is worth investigating. Crucially, high jitter alongside a high download speed is completely normal — and it means the problem is almost certainly your wifi or router rather than your provider.
Packet loss
The percentage of packets that never arrive. Anything above about 1% is a problem, and above 2-3% is severe. Lost packets must be retransmitted, which shows up as stalling rather than slowness. Packet loss usually points at a hardware fault, a badly overloaded router, or serious wifi interference.
Diagnosing it
Run a speed test and read all four numbers rather than just the first. The pattern tells you where to look:
- High download, high jitter — wifi interference or an overloaded router. Try 5 GHz, move closer, or test wired.
- High download, high ping — usually distance to the server, or a VPN routing your traffic through another country.
- Everything poor at certain hours only — peak-hour congestion on a shared line.
- Everything poor constantly, even wired — a line or router fault worth raising with your provider.
Test both wired and over wifi. The comparison is diagnostic on its own: if jitter is bad over wifi and clean over Ethernet, you have found your answer and no plan upgrade will help.
Fixing responsiveness
- Use 5 GHz, or a cable. The 2.4 GHz band is crowded and its interference is the single most common source of jitter in a home.
- Move the router. Central, elevated, not inside furniture. This is free and often the largest single improvement.
- Reduce contention. Cloud backups and game updates running in the background inflate both ping and jitter. Schedule them overnight.
- Turn off the VPN while testing. A VPN adds distance and processing; expect higher ping and lower throughput while it is on.
- Replace an old router. If a wired test is clean but every wireless device shows high jitter, the router's radio is the constraint.
The takeaway
If calls stutter and games lag on a connection that tests fast, stop looking at the Mbps figure — it is not the one describing your problem. Look at jitter first, then ping, then packet loss, and test wired versus wifi to find out which side of the router the fault is on. The fix is usually a position, a band or a cable, and almost never a bigger plan.
