What different test patterns suggest
| Pattern | Likely area to check | Next step |
|---|---|---|
| Plan typical speed is below your need | Plan capacity | Compare a plan whose Typical Download and Typical Upload meet the modeled need. |
| Near-router median is below need | Delivery or local equipment | Check modem, router, wiring, congestion, and provider delivery before buying more speed. |
| Near router passes; problem room fails | Wi-Fi coverage | Improve placement, backhaul, or coverage before upgrading the plan. |
| Both locations pass | Not an obvious throughput shortage | Check latency, jitter, packet loss, VPN, server, device, or application limits. |
Repeat the test under controlled conditions
Pause large transfers and VPN traffic, then run at least three tests near the router or over Ethernet and three in the problem room. The tool uses the median so one unusual result does not decide the diagnosis.
Compare against the plan's Typical Download and Typical Upload values, not only the marketed maximum.
Sources: United States Government (S21)Mbps is only one part of performance
Congestion can add queueing delay, and real-time applications can be sensitive to latency, jitter, and packet loss. VPN routing, the remote server, device limits, browser behavior, and storage speed can also make one task feel slow even when a throughput test passes.
Sources: Microsoft (S19), IETF / RFC Editor (S20)