Start with measurable causes
Do not infer the source from one speed number. Compare the same device, destination and time under controlled conditions.
Evening slowdowns often point to congestion on the home network or the provider network. Repeat comparable wired tests during quiet and busy hours to distinguish a recurring pattern from one bad result.
Do not infer the source from one speed number. Compare the same device, destination and time under controlled conditions.
Run tests at the same times for several days. 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.
Evening slowdowns often point to congestion on the home network or the provider network. Repeat comparable wired tests during quiet and busy hours to distinguish a recurring pattern from one bad result.
Run tests at the same times for several days. A repeatable fall in throughput or rise in latency at busy hours is stronger evidence than one test.
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.