Most slow internet problems are not what people think they are. The plan is not too slow. The router is not broken. The ISP is not throttling you. Something specific is happening at a specific layer between your laptop and the website, and that something has a name once you measure it. I learned this the hard way, after months of rebooting the modem at midnight and swearing at a router that did nothing wrong. Then a friend who runs networks for a living handed me a four-step checklist, and the entire dynamic changed. The diagnosis went from “I think it is the ISP” to “the DNS resolver is the problem, here is the proof.” Below is the version of that checklist I now keep handy, in the order the steps actually pay off.
The four tools, in the order I run them
The checklist is short on purpose. Four tools, four questions, four answers that usually nail the problem on the first pass.
- Ookla Speedtest: what is the connection actually delivering right now
- Traceroute or Pingplotter: which hop between you and the destination is slow
- DNS leak test plus a public resolver swap: are name lookups the bottleneck
- Wi-Fi analyzer or router admin page: is the wireless part the issue
That is the whole framework. Each tool answers a different question, and most internet problems fall into one of those four buckets. The order matters. Speed first, because if the wired speed is fine, you can rule out a third of the possible causes immediately and skip ahead.
Step one: a speed test you can actually trust
The reason speed tests mislead people is variability. A single test at noon tells you nothing about your evening experience, and a single bad test tells you nothing about your connection. The first habit to build is running the test three or four times across an hour, on both wired and wireless if you can. The pattern is the answer.
Three numbers matter on the Ookla Speedtest page. Download, which is what determines how fast streaming and downloads feel. Upload, which is what determines video call quality and cloud backup speed. Ping, measured in milliseconds, which is the round trip time to the test server and the number that spikes hardest when something is wrong. A fiber plan that delivers 290 Mbps at noon and 22 Mbps at 7 PM is congested, full stop, and the test gives you the proof in writing.
If the wired test is consistent across the hour and the wireless test is half the speed, the problem is not the connection. The problem is the wireless hop. If both are bad in the same way, the problem is upstream. If both are fine and the browser still will not load pages, the problem is downstream of the speed test, which is where the next tool comes in.
- Download, upload, and ping are the only numbers that matter
- Pattern across an hour matters more than any single test
- Compare wired versus wireless to localize the problem
Step two: traceroute when the speed is fine but the experience is bad
Traceroute is a network diagnostic tool that sends packets toward a destination with an increasing hop limit. Each router along the path replies, telling you how long it took and what its name and IP address are. The output is a numbered list of hops, and the latency column is the diagnostic.
The interesting line is the one where the latency jumps. If hops 1 through 4 are at 15 ms and hop 5 is at 180 ms, hop 5 is where the problem lives. If that hop belongs to your ISP, you have a real argument for a support call. If it is some middle-mile router between two providers, there is not much you can do but wait it out.
On Windows the command is tracert example.com. On macOS and Linux it is traceroute example.com. Both work. The graphical version is Pingplotter, which is worth installing if you are debugging an intermittent problem. Pingplotter runs continuously and graphs the latency per hop, so a single bad minute that traceroute would have missed becomes obvious. The free version handles one destination at a time, which is enough for most troubleshooting.
- Run traceroute to one popular site, like your bank’s domain
- Find the hop where the latency jumps
- Inside your ISP = support call. Middle of the internet = wait it out
Step three: DNS, the silent cause of “the internet is broken”
The pattern here is recognizable. Speed test is fine. Traceroute completes. Browser still will not load any website. Chat apps work fine. Email works fine. The websites themselves are unreachable. That is almost always DNS, the system that translates human-readable names like example.com into the IP addresses computers actually use to talk to each other.
The diagnostic is a DNS leak test. The website dnsleaktest.com runs in any browser and tells you which DNS server your computer is currently using. If the answer is your ISP’s server and your ISP’s DNS is slow or unreliable, you have a fix that takes about a minute. Cloudflare runs a public resolver at 1.1.1.1 and Google runs one at 8.8.8.8. Either is faster and more reliable than the average ISP default. You change the setting in your router’s WAN or internet settings, save, and the next DNS lookup goes to the new server. The improvement on name resolution can be dramatic, especially at peak hours.
- “Internet is broken” but speed test is fine? Check DNS
- dnsleaktest.com shows which resolver your device is using
- Switch to 1.1.1.1 or 8.8.8.8 for a free upgrade
Step four: Wi-Fi analysis when only the wireless is slow
If the wired speed is the full plan and the wireless speed is half, the wireless hop is the problem. Two free tools tell you what is happening. The first is your router’s own admin page, usually reachable at 192.168.1.1 or 192.168.0.1. The wireless section shows you which channel your router is on, how many devices are connected, and the signal strength each device reports back. If you are on channel 6 and six of your neighbors are also on channel 6, the channel is the problem.
The second tool is a Wi-Fi analyzer app. NetSpot Free is the standard on Windows. On macOS, hold Option and click the Wi-Fi icon in the menu bar, then pick “Open Wireless Diagnostics” for the same data without installing anything. Phones have free analyzer apps on both stores. These apps show you the channel landscape of every nearby network. The fix when channels are crowded is to pick a less crowded one, either by hand in the router settings or, on modern routers, by turning on the auto-channel feature.
- Wi-Fi slow, wired fine? Look at the channel
- Router admin page shows what channel you are on
- Wi-Fi analyzer apps show you which channels are crowded nearby
Trade-offs
The honest list of things these tools do not solve:
- A baseline speed test confirms the speed is bad but does not explain why. You still need traceroute or the ISP’s diagnostic tools to find the cause.
- Traceroute depends on the destination. If you trace to a site hosted on a CDN (a Content Delivery Network, which serves your request from a nearby data center instead of the site’s home server), you might hit a different path than you would for an unhosted destination.
- A DNS leak test only shows which resolver you are using, not whether it is fast. A slow resolver still resolves; it is just slow. Benchmark if you suspect the resolver.
- In a dense apartment building, every Wi-Fi channel is crowded. Sometimes the only fix is to move the router, run an ethernet drop, or accept the wireless limit.
What I would tell past me
If I were talking to the version of me who rebooted the router every evening and blamed the ISP for everything, I would say: run the four tools in order before calling anyone. Speed test, traceroute, DNS leak test, Wi-Fi analyzer. That is fifteen minutes of work, and you will know which of the four common buckets your problem lives in. Most evenings it is one of those four, and each has a different fix you can apply yourself in under five minutes. The remaining ten percent of problems are upstream of your house, and the call to your ISP gets shorter and more useful when you can point at the specific hop that is misbehaving.