How to debug slow internet

Debugging slow internet is a process of isolation. Change one variable, run a speed test, write the three numbers down. Most home problems fall out in under fifteen minutes if you do not skip the first measurements. The temptation is to skip them anyway: reboot everything, buy a new extender, shout at the provider, then measure nothing. That sequence creates folklore. This sequence creates a cause.

You do not need special software. You need a notepad, the same tester each time, and a willingness to walk toward the router. If ping is the complaint and megabits look fine, you will branch into delay. If megabits are the complaint, you will branch into Wi-Fi versus the last mile. Either way, the baseline comes first.

1. Take a baseline where you sit

Close extra streams. Test in the chair or the desk that feels slow. Record download, upload, ping, the time, and the room. If ping is high and Mbps is fine, skip straight to lag, jitter and packet loss. Games and calls can feel broken on a fat pipe. If Mbps is the complaint, continue. One run is a snapshot. You will add more, but you need a starting line so later changes mean something.

2. Move closer to the router

Test again within a couple of metres, line of sight if you can. A large improvement means the issue is the Wi-Fi hop, not the fibre or cable in the street. That is the most common outcome in apartments and houses where the access point lives in a cupboard, a garage, or the opposite end of a long hallway. Improving home internet speed starts with placement, a clearer band, Ethernet for the heavy device, or a mesh node — not a new contract.

If the near-router test is still poor, you have not wasted the walk. You have ruled out “only this armchair,” which is already progress. Continue. Do not change three settings at once because the first comparison was disappointing.

3. Other devices and software

Pause updates and cloud backups. Ask who is streaming. Disable the VPN and test once more. One laptop uploading a camera roll can flatten everyone else’s calls, especially on an asymmetric plan with a small upload. See whether a VPN is slowing the path. If the VPN gap is huge, you measured two routes. Keep the VPN off for the ISP conversation; keep it on for the “this is how I work” conversation.

Test a second device if you have one. A single old phone with a weak radio can look like a failing provider. If the laptop next to it is fine, the phone is the project. If both are weak in the same spot, the network is the project.

4. Restart, then compare with a cable

Power-cycle the router and the modem — they are sometimes one box — wait two minutes, and test near the router again. A reboot that restores speed for an hour and then fades is a clue: stuck radio, tired hardware, or a WAN session that needs a longer look from the ISP. A reboot that changes nothing is also a result. You can stop treating reboots as a personality.

If you can plug in Ethernet, do it. The cable is the cleanest picture of the last mile. If you are still far below the advertised Mbps on a wired or near-router test at several hours of the day, you have a case for the ISP. Read speed test versus the plan so you know what “far below” usually means, then bring timestamps. Support scripts melt when you only have a feeling.

5. Decide what you are going to change

The debug path should end in a decision, not in another dozen tests. If the far room is the only weak cell, move the router, add a node, or run a cable. If the house is busy, schedule backups or stop stacking 4K on a small plan. If the wire saturates a 50 Mbps product and the household now works from home, look at typical speeds by activity and consider more megabits. If the wire is chronically short of the plan, the ticket is for the provider, not for a new Wi-Fi gadget.

Resist the “optimizer” app, the random QoS checkbox, and the factory reset as first moves. They hide the evidence you just gathered. Measure, isolate, then change one thing. That is the whole craft of answering why the internet feels slow.

Keep the notes even after the problem is gone. Next time the house feels slow, you already know what “normal” looked like on Ethernet at 8 p.m. Without that baseline, every dip feels like a crisis. With it, you can see whether tonight is a radio night, a busy-house night, or a last-mile night — and you can skip the steps you already proved last month.

Common questions