Start with measurable causes
Do not infer the source from one speed number. Compare the same device, destination and time under controlled conditions.
If your internet suddenly slows down, first pause large transfers and compare the same device over Wi-Fi and Ethernet. Then check a second device and repeat with the network idle and busy. The pattern helps separate local Wi-Fi, competing traffic, device and provider-path problems.
Do not infer the source from one speed number. Compare the same device, destination and time under controlled conditions.
Pause large transfers and record an idle baseline. 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.
Record the device, connection type, time, download, upload and response timing. Change one condition at a time. These patterns suggest the next check; they do not prove which component is faulty.
| What you observe | What to investigate | Next step |
|---|---|---|
| Ethernet is consistently faster than Wi-Fi on the same device | Wireless signal, interference, band or local contention | Compare Wi-Fi near the router and in the affected room |
| Only one device is slow in the same location | Device load, software or its connection | Compare another device and browser |
| Multiple wired devices slow down at similar times | Shared traffic, router load or the provider path | Record quiet-hour and busy-hour tests |
| Speed looks normal but calls or games lag | Upload demand, variable timing or latency under load | Check the signals beyond download speed |
| Timing worsens during an upload or download, then recovers when it stops | Queueing, traffic competition or Wi-Fi airtime contention | Compare idle and loaded timing; repeat wired before attributing the cause |
| One website is slow but other destinations and tests are normal | The destination, its route or browser/device behavior | Check website availability; a server-side check measures a different path |
If multiple wired devices are slow at comparable times, check provider outage notices and collect repeatable download, upload and timing results. Include your advertised plan and when the problem began. A router, modem, cable or upstream path may still be involved; one low result does not prove throttling. Restart equipment once if appropriate, after saving useful logs. Do not factory-reset equipment as a first diagnostic step.
If your internet became slow all of a sudden, compare the same device and endpoint before and after each change. The homepage connection check can compare the previous and current result in the same tab. Keep the tab open when you change connection type. A local Docker preview measures the local endpoint, so use the public site to investigate an internet connection.
If comparable wired results degrade across several apartments, review the MDU broadband guide for multi-dwelling units before escalating the shared building connection.
Full home-testing guide · How to interpret browser measurements
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 your internet suddenly slows down, first pause large transfers and compare the same device over Wi-Fi and Ethernet. Then check a second device and repeat with the network idle and busy. The pattern helps separate local Wi-Fi, competing traffic, device and provider-path problems.
Pause large transfers and record an idle baseline. Compare download, upload, latency, jitter and observed loss under the same conditions—not download alone.
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.