Most people troubleshoot slow internet by guessing. They reboot the router, drag it to a new corner, call the ISP, and hope one of those moves happens to hit the right layer. Sometimes it does — by accident.
Operators don’t guess. When a customer calls in with “my internet is slow,” a technician doesn’t start poking at random settings. They work through a fixed sequence, isolating one layer at a time, until the fault has nowhere left to hide. That sequence is what this checklist is built from.
“Slow” is not one problem. Ask “why is my internet slow?” and you’re really asking about at least six different things at once: a bad line from the ISP, a struggling gateway, weak Wi-Fi coverage, a network choked with active devices, a router that’s overheating, or a plan tier or provisioning limit that has nothing to do with your equipment at all. Fix the wrong layer and nothing changes — you just end up more convinced that “the internet is broken” with no better idea of why.
The reset button is not a diagnostic tool. It is a coin toss.
Why the order matters
Each step below rules something out before you move to the next. Skip a step and you risk fixing a symptom instead of the cause — replacing a router when the real problem was the ISP line, or chasing a placement fix when the real problem was an overloaded network. Work top to bottom. The point isn’t to complete every step — it’s to stop as soon as the pattern becomes clear.
Step 1: Test the wired baseline first
Before blaming Wi-Fi, find out whether the line itself is the ceiling. Connect a laptop directly to the gateway with an Ethernet cable and run a speed test.
For this test, keep it boring: use one laptop, turn Wi-Fi off on that laptop, disable your VPN if you use one, use a known-good cable, and run the test more than once. A wired connection won’t hit your plan number down to the decimal, but it should land reasonably close. A sloppy test setup can send you chasing a problem that isn’t really there.
If the wired result already falls far short of your plan speed, you’ve learned something important: this is not primarily a Wi-Fi problem. The fault sits in the line, in the gateway, or in the way the connection is being delivered to it — so the gateway check in Step 2 and the ISP-side section in Step 7 are where your answer most likely lives, not the Wi-Fi steps in between. If the wired result lands near your plan speed, the ISP line probably isn’t the ceiling, and the problem is somewhere in your local network — coverage, airtime, placement, heat, or the devices using the connection.
Step 2: Check the gateway before blaming Wi-Fi
The box in your home is a small computer, and like any small computer, it can get into a bad state. Before assuming a coverage or congestion problem, rule out the gateway itself:
- Does the gateway’s app or admin page show the WAN/Ethernet link running at the right speed — or has it fallen back to 100 Mbps (or to 1 Gbps on a multi-gig plan) when it should be higher?
- Is the Ethernet cable between the wall and the gateway old, damaged, or the wrong category — enough to drag that link down to a lower speed?
- Has the gateway been running for weeks and started crashing or rebooting on its own?
- Is the firmware current, or has an update been sitting unapplied?
A gateway stuck on a degraded WAN link, fighting a bad cable, or quietly restarting itself can produce symptoms that look exactly like a Wi-Fi problem but have nothing to do with radios at all.
Step 3: Check whether this is really a coverage problem
If the wired baseline is clean and the gateway checks out, the next question is whether the signal is actually reaching where you’re using it. The pattern to look for: does the slowness track a specific room, a specific distance, or one side of a particular wall? If speed is fine near the router and falls off the further you get, that’s a coverage problem — not a capacity or ISP one. It’s also worth remembering that the number printed on a router’s box assumes ideal, close-range conditions most homes never actually have, so some gap between the label and real-world speed is normal even before coverage enters the picture.
Step 4: Check airtime and active device load
This isn’t about how many devices are connected — a phone asleep in another room isn’t costing you anything. What matters is how many devices are actively transmitting or receiving at the same moment. Wi-Fi is shared airtime. Newer features can help multiple devices share the channel more efficiently, but the basic constraint holds: active devices still compete for time on the air.
A house with twenty idle devices and two people streaming video is in a very different position than a house where six devices are all actively pulling data at once. If slowness only shows up during specific hours — everyone home, everyone streaming — this is often the layer responsible, and it’s a capacity problem rather than a coverage one.
Step 5: Check placement before buying anything
Placement is the physical cause behind many coverage problems. Where the router sits does a surprising amount of the work. A gateway tucked inside a media cabinet, sitting on the floor, boxed in by metal, or pushed into a back corner of the house is fighting its physical environment before the RF layer ever gets a fair chance. This is worth checking before spending money on a mesh system or a new router, because a placement fix is free and a hardware fix isn’t.
Step 6: Check heat and aging hardware
Routers normally run warm — that alone means nothing. But if the slowness gets worse the longer the router has been running, shows up more on hot days, or the chassis feels unusually hot, heat is worth a look. Heat can make a router protect itself by reducing performance. In technical terms that’s thermal throttling, but the symptom is simple: the network feels fine at first and gets worse after the box has been working for a while. Consumer routers rarely have active cooling, and aging hardware or a tired power adapter can produce the same slow, creeping decline over weeks or months rather than a sudden drop.
Step 7: Only then look at ISP-side limits
If every layer above checks out — clean wired baseline, healthy gateway, full coverage, no congestion, no heat issue, sensible placement — what’s left is the ISP side: the plan’s actual speed tier, how the connection was provisioned, congestion on the ISP’s shared local infrastructure, policy limits, and, in some cases, active throttling. This is the layer people tend to suspect first and should actually check last, because it’s the hardest to fix yourself and the easiest to rule everything else out before assuming.
The checklist, at a glance
| Symptom pattern | Likely layer | What to test next |
|---|---|---|
| Wired speed test also falls short | ISP line / gateway | Confirm plan with ISP, check WAN link speed |
| Gateway crashes, old firmware, or bad cable | Gateway health | Update firmware, check link speed and cable |
| Fine up close, worse with distance or walls | Wi-Fi coverage | Map where the signal drops off |
| Slow only when many devices are active | Airtime / device load | Check usage during peak hours |
| Router boxed in, on the floor, in a corner | Placement | Relocate before buying new gear |
| Worse over time, hot to the touch | Heat / aging hardware | Check ventilation, consider the age |
| Everything above checks out | ISP-side limits | Confirm plan tier and provisioning with ISP |
Before you call the ISP
If you do reach the point of calling, don’t call with only “it’s slow.” Call with the wired speed result, the time of day it happens, whether Ethernet is affected too or only Wi-Fi, and whether the problem is everywhere or only in certain rooms. That turns a complaint into a diagnosis — and it’s the difference between a script-driven reset and an actual fix.
The point isn’t to fix everything at once
It’s to stop guessing. Most slow-internet fixes fail because they start with a guess. This checklist starts with a baseline. Work the list in order, and most people will find their answer in the first two or three steps — long before they need to change a setting, buy a mesh kit, or wait on hold.
FAQ
“Slow” is a symptom with several possible causes, not one problem. Work from the outside in: test a wired connection first to see whether the ISP line itself is the ceiling, then check the gateway, Wi-Fi coverage, how many devices are active, router placement, and heat — and only then look at ISP-side limits. Most sudden slowdowns trace back to the first few checks.
That split is useful information: it means the ISP line is fine and the problem is in your local Wi-Fi, not upstream. The usual causes are coverage (distance and walls), too many active devices competing for airtime, or poor router placement. It points you at the Wi-Fi-side checks rather than a call to your provider.
Sometimes — but as a diagnosis it’s a coin toss. A restart can clear a gateway that’s gotten into a bad state, which is a real cause, but it won’t touch coverage, device load, heat, or an ISP-side limit. If a reboot only helps for a while, that’s a clue the real problem is one of the other layers.
Rule everything else out first. Confirm a wired test falls short of your plan, that the gateway is healthy, and that the slowdown isn’t tied to Wi-Fi coverage, device load, or peak-hour congestion. Throttling is the layer to suspect last, not first, because it’s the hardest to fix yourself and the easiest to mistake for a local problem you could actually solve.
