What Is Network Quality, and Why Speed Isn't Enough
Your internet is 200 Mbps but Zoom still freezes? Speed isn't the whole picture. Here's what actually determines whether your connection feels fast or slow.
Your speed test says 200 Mbps. So why does your Zoom call keep freezing? Why does your game lag? Why does everything feel slow even though you're paying for "fast" internet?
Because speed isn't the whole picture. There are four things that determine whether your internet actually feels good — and most speed tests only measure one of them.
The Four Things That Matter
Think of your internet connection like a delivery service. Bandwidth (speed) is how many packages the truck can carry at once. But that's not the only thing that matters — you also care about how long deliveries take, whether they show up on time, and whether packages get lost along the way.
1. Bandwidth (Speed)
This is the one everyone knows — how much data your connection can move per second, measured in Mbps. It matters for big transfers: downloading games, streaming 4K video, uploading large files.
But here's the thing most people don't realize: most everyday activities barely use any bandwidth. A Microsoft Teams audio call needs just 58 kbps — that's 0.058 Mbps. Your 200 Mbps connection is 3,400x more than that call needs. So if your call is choppy, bandwidth is almost certainly not the problem.
2. Latency (Delay)
Latency is how long it takes for data to make a round trip — from your device to a server and back. It's measured in milliseconds (ms).
Low latency (under 30ms) feels instant — clicks respond immediately, video calls feel natural, games are responsive. High latency (over 100ms) feels like everything is happening in slow motion. You click, then wait. You speak, then hear an echo.
Microsoft sets the bar for good Teams call quality at under 60ms. Anything above 500ms and the call is essentially broken.
3. Jitter (Inconsistency)
Jitter is how much your latency bounces around. Steady 50ms latency? Your brain adapts and it feels fine. Latency that jumps between 20ms and 200ms every few seconds? That's when video freezes mid-sentence, audio cuts in and out, and games rubber-band.
Microsoft's target for good call quality is jitter under 3ms. Above 30ms, calls start falling apart.
4. Packet Loss (Missing Data)
Sometimes data packets just don't arrive — they get dropped somewhere along the way. When this happens during a file download, your computer requests them again and things slow down. According to ThousandEyes, even 1% packet loss can cut download speeds by up to 75%.
But for video calls and games, lost packets can't be resent in time — they're just gone. That's why voices turn robotic, video gets blocky, and game actions don't register. Microsoft considers anything above 0.5% packet loss problematic for calls.
What Your Apps Actually Need
Here's a reality check on what popular services require:
| App | Bandwidth needed | What actually matters |
|---|---|---|
| Microsoft Teams (HD video) | 1.5–4 Mbps | Latency, jitter, and packet loss |
| Zoom (1080p) | 3–4 Mbps | Latency, jitter, and packet loss |
| Netflix (4K) | 15 Mbps | Mostly just bandwidth |
| Online gaming | Under 1 Mbps | Almost entirely latency and packet loss |
| GeForce NOW (4K cloud gaming) | 45 Mbps | Bandwidth AND latency |
See the pattern? The apps where people most often complain about "slow internet" — calls, gaming, remote work — barely need any bandwidth. What they need is low latency, steady timing, and no lost packets.
The Hidden Problem: Bufferbloat
There's one more thing that can silently ruin your connection: bufferbloat.
Here's how it works: your router has a buffer (a waiting area for data). When someone in your house starts a big download, that buffer fills up. Now every other piece of data — your Zoom audio, your DNS lookups, your game inputs — has to wait in line behind all that download traffic.
The result: your speed test still shows great bandwidth, but everything interactive feels terrible. Your video call freezes the moment someone starts downloading a game on the same network.
This problem is so common that the networking community built an entire algorithm (FQ-CoDel) specifically to fix it, and major router operating systems like OpenWRT now ship with it enabled by default. As the Bufferbloat project puts it: "The perceived speed of the internet depends more on latency response times than raw bandwidth capacity."
How to spot it: Compare your latency when nothing is happening to your latency while someone is downloading a large file. If the difference is more than 50ms, you have a bufferbloat problem — and upgrading to a faster plan won't help.
Why Speed Tests Don't Tell the Full Story
A traditional speed test maxes out your connection and reports the peak throughput. That number tells you how fast you can download a file, but nothing about how your connection handles real-time activities.
Think about it this way:
- Connection A: 100 Mbps, 5ms latency, 0% packet loss
- Connection B: 500 Mbps, 80ms latency, 2% packet loss
Connection B wins every speed test by 5x. But Connection A will give you better Zoom calls, smoother gaming, and snappier web browsing. Connection B's packet loss alone makes video calls nearly unusable.
What You Can Do About It
The good news: once you know which metric is causing your problem, the fix is usually straightforward.
- High latency? Try a closer server, switch to a wired connection, or check if your VPN is routing traffic through a distant country.
- High jitter? WiFi is the usual culprit. Switching to Ethernet is the single biggest improvement most people can make.
- Packet loss? Check your cables (loose Ethernet connections are a common cause), restart your router, or contact your ISP — packet loss often happens outside your home network.
- Bufferbloat? Enable SQM (Smart Queue Management) on your router if it supports it, or upgrade to a router running OpenWRT with FQ-CoDel.
Test Your Connection
Run a network quality test to see all four metrics. You might be surprised — the number that matters most probably isn't your download speed.