You run a speed test and it says 250 Mbps download. Your ISP plan says "up to 300 Mbps." So you are getting 83% of what you pay for. Is that good? It depends on what you are actually testing.
Most people interpret speed test results as "the speed of my internet." What they are actually measuring is "the speed between my device and a specific server, at this moment, through my WiFi, my router, my modem, my ISP's network, and the peering between my ISP and the test server." Every link in that chain is a potential bottleneck.
What speed tests actually measure
Download speed. How fast you can pull data from a server. Measured by downloading a large file (or multiple files) and calculating the throughput. Reported in Mbps (megabits per second).
Upload speed. How fast you can push data to a server. Usually much slower than download for residential connections (asymmetric). Important for video calls, file uploads, and streaming.
Latency (ping). The round-trip time for a small packet to reach the server and return. Measured in milliseconds. Important for gaming, video calls, and interactive applications. Under 20ms is excellent. Under 50ms is good. Over 100ms is noticeable.
Jitter. The variation in latency over time. Low average latency with high jitter produces an inconsistent experience. Video calls stutter, games lag intermittently.
Why your results vary
Run a speed test 5 times in a row. You will get 5 different numbers. This is normal and does not indicate a problem.
WiFi interference. Your neighbor's WiFi, Bluetooth devices, microwaves, and other 2.4GHz devices all share the same spectrum. 5GHz is less congested but has shorter range.
Distance from router. Signal strength decreases with distance and obstructions (walls, floors, furniture). Standing next to the router gives dramatically different results than testing from the far bedroom.
Network congestion. If someone on your network is streaming 4K video or downloading a large file, the remaining bandwidth is reduced. Speed tests during peak usage hours (7-10 PM) are typically slower than early morning.
Server selection. Testing against a server 50 miles away gives different results than one 500 miles away. Most speed test tools auto-select the nearest server, but "nearest" varies between services.
Time of day. ISP network congestion varies by time. Evening peak hours can reduce speeds by 20-50% compared to off-peak hours, depending on your ISP and area.
Testing correctly
For meaningful results:
Test on a wired connection (Ethernet) first. This establishes your internet speed without WiFi variables. If wired is fast but WiFi is slow, the problem is your WiFi setup.
Test at different times. Run tests at morning, afternoon, and evening over several days. The pattern reveals whether your ISP is throttling during peak hours.
Test from the same location. If comparing results over time, test from the same physical position for consistency.
Use multiple servers. Your ISP may prioritize traffic to speed test servers (making their network look faster). Test against different servers or services.
Close other applications. Any application using bandwidth during the test skews the results downward.
What the numbers mean practically
| Activity | Required Download Speed |
|---|---|
| Email and web browsing | 1-5 Mbps |
| SD video streaming | 3-5 Mbps |
| HD video streaming | 5-10 Mbps |
| 4K video streaming | 25 Mbps |
| Video conferencing | 5-10 Mbps (+ 5 Mbps upload) |
| Online gaming | 10-25 Mbps (low latency more important) |
| Large file downloads | 50+ Mbps |
For a household with 4 people streaming simultaneously, 100 Mbps is comfortable. 50 Mbps is tight. 25 Mbps will cause buffering.
I built a WiFi speed test at zovo.one/free-tools/wifi-speed-test that measures download speed, upload speed, latency, and jitter from your browser. It runs against multiple test points and reports results with enough context to understand what they mean for your actual usage patterns.
I'm Michael Lip. I build free developer tools at zovo.one. 500+ tools, all private, all free.
Top comments (0)