Start with measurable causes
Do not infer the source from one speed number. Compare the same device, destination and time under controlled conditions.
A high throughput result does not rule out packet loss. Loss can be intermittent and may come from weak Wi-Fi, congestion, faulty equipment or an upstream route.
Do not infer the source from one speed number. Compare the same device, destination and time under controlled conditions.
Repeat the loss test over Ethernet. 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.
A high throughput result does not rule out packet loss. Loss can be intermittent and may come from weak Wi-Fi, congestion, faulty equipment or an upstream route.
Repeat the loss test over Ethernet. Zero observed loss is ideal; sustained or bursty loss can harm calls and games.
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.