Packet loss, jitter and lag

Laggy internet is often delay, not a lack of megabits. You can test internet speed, see a healthy download, and still miss headshots or freeze on a call. Ping, jitter and packet loss are the names for that. Treating every complaint as “I need more Mbps” is how people buy a faster plan and keep the same ugly lobby.

Capacity still matters for 4K and big downloads. Delay matters for anything that has to happen now. The two are easy to confuse because both feel like “the internet is bad.” A speed test that only shouts a download number is half an instrument. SpeedMetric reports ping with the rest of the result so you can see whether you have a fat, late pipe.

Ping versus megabits

Ping is round-trip time. Mbps is how much data fits in a second. A fat pipe with 120 ms ping still feels sluggish in a lobby. Ping and jitter belong in every serious speed test, not only the headline download. Distance to the server, Wi-Fi retries, a VPN, and a congested route all add delay. A quiet Ethernet run with 15 ms ping and a sofa run with 90 ms ping is a radio story, not a plan story.

“Good” ping depends on the job. Under about 30 ms feels snappy for most games and calls. 50 to 80 ms is usable for a lot of people. Over 100 ms, real-time apps start to feel late even if the download gauge looks proud. Video can hide some delay by buffering. Competitive games cannot. That is why two people on the same plan can disagree about whether the internet is fine.

Jitter, packet loss and bufferbloat

Jitter is how much ping jumps. A stable 25 ms ping feels better than a 15–80 ms bounce. Voice and video codecs can hide a little jitter. Large swings show up as choppy audio or frozen frames. Packet loss is data that never arrives. The app must wait, guess, or skip. Wi-Fi interference, a saturated upload — someone backing up while you talk — or a congested ISP hop can cause both.

Bufferbloat is when a queue on the router or modem adds delay under load. Speed looks high until someone uploads, then ping explodes. The line is not “slow” in megabits. It is polite to a fault: it holds too much data in a buffer instead of signalling congestion quickly. You notice it as a call that dies the moment a cloud backup starts, even though the download test was fine five minutes earlier.

How to isolate delay

Test on Ethernet if you can. Radio loss looks like random lag and will waste an evening of settings. Stop the backup, then test again during a call. Pause the VPN for a second measurement; a distant VPN server is a ping machine. If wired ping stays high at several hours, follow the slow-internet debug path toward the ISP. If only Wi-Fi is jumpy, you are back in wireless versus cable territory.

Other devices on a small upload deserve suspicion. Many home plans are asymmetric. A laptop sending photos can fill the climb out of the house and leave the call gasping. Pause the upload, watch ping fall, and you have the cause without buying anything. QoS or smarter queueing on a capable router can help chronic bufferbloat; random “gamer mode” checkboxes usually do not.

What to chase first

For games and voice, chase stable, low ping first. Capacity still matters — check whether your Mbps is enough — but extra megabits will not hide 180 ms of delay. For films, chase a steady download and a radio that does not drop. For mixed households, measure at dinner, not only at midnight. How to test internet speed is the prep so the delay numbers are as honest as the megabits.

Write ping down every time you write download. That single habit separates “we need a faster plan” from “we need a cable to the desk” from “we need to pause the backup.” It is the difference between buying equipment and actually fixing the lobby.

When the application is the late one

Not every stutter is your last mile. A game server on another continent, a call routed through a distant region, or a website having a bad afternoon can feel like “the internet” while the tester looks fine. That is why a local speed test is the first instrument, not the last. If ping to the test endpoint is low and the lobby is still late, the delay is farther out. Switching servers, pausing overlays, or trying a second app is then more rational than buying megabits.

Keep notes anyway. A pattern of high jitter only on Wi-Fi, only at dinner, or only with a backup running is still your house. A pattern of fine local ping and one bad game is not. The slow-internet article is for capacity complaints. This page is for the case where capacity was never the right question.

Common questions