Stop Screenshotting Your Speed Test: The Numbers That Actually Tell You What's Wrong

Everyone has a speed test screenshot. It's the home networking equivalent of a trophy fish photo — impressive, slightly exaggerated, and honestly not that informative. Because here's the thing: download speed tells you how big your pipe is. It says nothing about whether the water comes out steady.

If your video calls glitch, your games rubber-band, or your pages hang on that weird half-loaded state, your problem almost certainly isn't bandwidth. It's one of the quieter numbers below. Let's learn to read them.

First, Run a Real Test

Go to a test that measures more than speed — Waveform's bufferbloat test or a quality-focused test like speed.cloudflare.com will do. Then, crucially, run the test twice: once on an idle network, and once while something else is happening (a video streaming, a big download running). The difference between those two runs is where most home network problems hide.

Now, the numbers.

1. Download Speed

Yes, it's on the list, if only to calibrate. Anything above roughly 50 Mbps handles a busy household fine for most uses. If you're paying for 500 and getting 480, congratulations — your speed test is done, and your actual problem is somewhere below.

2. Upload Speed

The forgotten sibling. Video calls, cloud backups, and online gaming all lean on upload. Under 10 Mbps and a house full of chatty cameras and calls will feel congested even with blazing download. Under 5, expect pain.

3. Idle Latency (Ping)

This is the round-trip time for a tiny packet to reach a server and come back, measured in milliseconds. Under 20 ms is excellent. 20–50 is fine. Above 100, and you'll feel it in games and calls. This is the number that determines whether things feel snappy.

4. Latency Under Load

Now run that same ping while the network is busy. If your idle latency is 15 ms and your loaded latency is 300 ms, congratulations — you've found why your calls collapse every time someone presses play on Netflix. This gap is the most diagnostically powerful number in home networking, and almost nobody looks at it.

5. Bufferbloat

This is the grade you get for that gap. Bufferbloat happens when your router (or your ISP's equipment) accepts more data than the line can send and queues it up, adding latency for everyone. A grade of A means your latency barely moves under load. A grade of D or F means one download can wreck the whole house. It's also, conveniently, one of the most fixable problems — more on that at the end.

6. Jitter

Jitter is the wobble in your latency — how much your ping varies from test to test. Steady 40 ms beats erratic 10-to-90 ms every time. Real-time stuff (voice, video, games) hates jitter more than raw latency. Above roughly 30 ms of variation, calls start sounding like a walkie-talkie.

7. Packet Loss

The bleakest number. Packet loss means data is literally vanishing en route — usually from a bad cable, a failing port, weak Wi-Fi, or a problem at your provider. Anything over 1% is a genuine problem. 0% is the only acceptable answer on a wired connection; Wi-Fi can tolerate a whisper of it.

8. DNS Resolution Time

When you type an address, a DNS lookup has to translate it into an IP first. If that lookup takes 500 ms, every new site feels sluggish no matter how fast your connection is. Most tests skip this. If pages hang before they start loading, this is your suspect.

9. Wi-Fi Signal Quality

Not a speed test number, but the most common root cause behind bad versions of all the others. Check what band you're on (2.4 GHz crawls but penetrates walls; 5 GHz is fast but short-range), and look at signal strength where you actually use the internet — not where the router lives.

Reading the Story

Here's how the numbers combine. Fast speeds, terrible bufferbloat? Fixable with router QoS settings or a router with SQM-based queue management. High idle latency everywhere? Probably distance or a congested node — an ISP conversation. Great wired, terrible Wi-Fi? Stop blaming your provider and move your router or add an access point. Packet loss on wired? Check the cable before you check anything else.

The point isn't to turn you into a network engineer. It's to make sure that when something's wrong, you're describing the actual symptom — because "my internet is slow" and "my latency quadruples under load" are two completely different support tickets.