The short answer

Yes, but not in the way most people assume. Packet loss and lag get used interchangeably in everyday conversation, and they’re related, but they’re not the same thing. Lag is what you feel. Packet loss is one of several things that can cause that feeling. The other big ones are high latency and jitter, and the fix for each is different, which is why it matters to know which one is actually hitting you.

Think of it like being late to a meeting. Latency is the meeting starting twenty minutes late because the train was slow. Jitter is the meeting starting at random times each week, so you can never plan around it. Packet loss is the meeting being cancelled entirely and having to be rescheduled. All three feel like “the meetings are bad”, but the causes and fixes are completely different.

How packet loss turns into lag

When a packet goes missing, what happens next depends on the type of traffic. For anything using TCP, like web browsing, file transfers, and most apps, the protocol notices the gap and asks the sender to resend the missing packet. That round trip takes time. So instead of your data arriving in one smooth stream, it arrives, pauses while the missing piece is requested again, then continues. That pause is the lag you feel. The more loss, the more pauses, and the more sluggish everything feels.

For real-time traffic like voice calls, video, and online games, the picture is different because these use UDP, which doesn’t resend missing packets. Instead the application just carries on with whatever data made it through. The lag here isn’t from waiting for resends, it’s from the application having to cover the gap somehow. In a voice call you get a glitch or a robotic stutter. In a game you get rubber-banding, where your character snaps back to where the server last had reliable information about you. Either way, it feels like lag even though no packet is being resent.

This is why competitive gamers care so much about packet loss specifically. A connection with high latency but zero loss feels consistently slow but predictable. A connection with low latency but 2% loss feels jumpy and unreliable, and that unpredictability is far worse for gaming than a steady delay would be.

How to tell which problem you actually have

Run a ping test and look at three numbers, not just one. The packet loss percentage tells you about loss. The average time tells you about latency. The variation between the fastest and slowest replies tells you about jitter. A healthy connection will show 0% loss, low ping times (under 50ms to a nearby server), and small variation between replies.

If your latency is high but loss is zero, the route to the server is just long or slow, and no amount of fiddling with your router will fix it. If loss is high but latency is low, you’ve got a quality problem somewhere in the chain that needs hunting down. If latency varies wildly from packet to packet, that’s jitter, often caused by Wi-Fi interference or a router that can’t keep up with the traffic.

Knowing which of the three you’re dealing with stops you from chasing the wrong fix. Buying a faster broadband package won’t help packet loss. Replacing a dying router won’t help latency to a server on the other side of the world. The diagnosis decides the cure.