Start with measurable causes
Do not infer the source from one speed number. Compare the same device, destination and time under controlled conditions.
If other devices are fast, the bottleneck is usually local to the affected device: its Wi-Fi link, background traffic, browser, VPN, network settings or hardware. Test both devices in the same place under the same conditions.
Do not infer the source from one speed number. Compare the same device, destination and time under controlled conditions.
Test two devices beside each other. Keep other variables stable, then change one condition at a time.
Confirm this possibility with a repeatable comparison before changing equipment or service.
Confirm this possibility with a repeatable comparison before changing equipment or service.
Confirm this possibility with a repeatable comparison before changing equipment or service.
Confirm this possibility with a repeatable comparison before changing equipment or service.
Record the result, keep the test comparable and continue only after this step.
Record the result, keep the test comparable and continue only after this step.
Record the result, keep the test comparable and continue only after this step.
Record the result, keep the test comparable and continue only after this step.
Read throughput together with ping, jitter and packet loss. A browser result describes this device, route and moment; it does not by itself prove an ISP fault.
If other devices are fast, the bottleneck is usually local to the affected device: its Wi-Fi link, background traffic, browser, VPN, network settings or hardware. Test both devices in the same place under the same conditions.
Test two devices beside each other. A same-place, same-time comparison isolates device effects from the router and ISP.
No. Repeat comparable tests over Ethernet and Wi-Fi, on more than one device and at different times.
Save the result, repeat under comparable conditions and use the difference as evidence.