Your ISP promises 500 Mbps. Speed tests show 480 Mbps. You're getting what you paid for, right? Maybe. The speed test measures the bandwidth between your device and the test server. It says nothing about the bandwidth between you and Netflix, your office VPN, or the game server in another continent.
What speed tests measure
A speed test opens multiple TCP connections to a nearby server and pushes as much data as possible for a few seconds. The peak throughput becomes your "speed." This measures:
- Your connection's maximum bandwidth under ideal conditions
- The path between you and that specific test server
- Performance at that exact moment
It does not measure:
- Bandwidth to any other server
- Consistency over time
- Performance during congestion hours
- Application-level throughput (which is always lower)
Download vs upload vs latency
Download speed: How fast data flows from the internet to you. Matters for streaming, browsing, and downloading files. Most residential connections are asymmetric: download is much faster than upload.
Upload speed: How fast data flows from you to the internet. Matters for video calls (you're uploading your video), cloud backups, and sending large files. Often 10-20% of download speed on cable connections. Fiber typically offers symmetric speeds.
Latency (ping): How long a round trip takes. Matters for gaming, video calls, and interactive applications. 10-30ms is good. 50-100ms is acceptable. 200ms+ is noticeable in real-time applications. Speed tests that only report download/upload miss the most important metric for many use cases.
Jitter: Variation in latency. Low average latency with high jitter means inconsistent performance. This causes video call glitches, game lag spikes, and choppy VoIP.
Why your real-world speed differs
Network congestion: Your ISP oversubscribes the network. At 8 PM when everyone is streaming, available bandwidth drops. Speed tests at 3 AM versus 8 PM can differ by 50% or more.
Wi-Fi bottleneck: Your internet is 500 Mbps but your Wi-Fi link is 200 Mbps. The speed test shows 200 Mbps and you blame your ISP. Test on a wired connection to isolate the WAN speed from the LAN speed.
Server distance: A speed test to a server 20 miles away will show higher speeds than a connection to a server 3,000 miles away. TCP throughput degrades with distance due to latency's effect on congestion window scaling.
VPN overhead: A VPN adds encryption overhead (typically 5-15% bandwidth reduction) and routes your traffic through an additional hop (adding latency).
What "enough" bandwidth looks like
- Email and web browsing: 5 Mbps
- HD video streaming (1080p): 5-10 Mbps per stream
- 4K video streaming: 25 Mbps per stream
- Video calls (Zoom, Teams): 3-5 Mbps upload + download
- Online gaming: 3-5 Mbps (bandwidth matters less than latency)
- Working from home (general): 25-50 Mbps
A household with two people streaming 4K and a third on a video call needs about 55-60 Mbps. The 500 Mbps plan is overkill unless you're frequently transferring large files.
I built a browser-based speed test at zovo.one/free-tools/speed-test that measures download speed, upload speed, latency, and jitter. It gives you a clear picture of your connection's actual performance at this moment.
I'm Michael Lip. I build free developer tools at zovo.one. 500+ tools, all private, all free.
Top comments (0)