Slow internet does not automatically mean your router needs replacing. A single overloaded website, a weak signal in one room, background downloads or the internet connection itself can produce similar symptoms. A short comparison test is more useful than changing several settings at once.
At Techleez, practical troubleshooting starts with evidence you can collect yourself. You do not need to install an unfamiliar “speed booster” to use this checklist.
Describe the failure in one sentence
Write something specific: “Video calls break up in the bedroom after 8 p.m., but websites load normally beside the router.” That is more actionable than “Wi-Fi is bad.” Include where, when, which device and which activity are affected.
Before testing, pause large downloads and cloud uploads where practical. If other people are using the connection, note that rather than pretending your test was isolated. Keep the same device and service for each comparison.
Build a small test matrix
| Comparison | If only one side fails | Next investigation |
|---|---|---|
| One website versus another | The service may be the issue | Check its status and try later |
| Two devices in the same place | The device or app may be involved | Review that device’s connection and updates |
| Beside the router versus another room | Signal or interference may matter | Test placement and obstacles |
| Wi-Fi versus a supported wired connection | The wireless part may be the bottleneck | Inspect Wi-Fi conditions before changing the internet plan |
| Busy hours versus a quieter time | Congestion or simultaneous use may matter | Compare household activity and provider performance |
These comparisons narrow the problem; they do not prove a component is defective. A phone and laptop can have different wireless capabilities, so treat device-to-device comparisons as clues.
Make one reversible change
Restarting a modem or router can be a reasonable troubleshooting step when the provider’s instructions recommend it. Tell other users first: it interrupts calls and connected services. A restart is different from a factory reset. Do not press a reset button or erase your network configuration as a first response.
For a placement test, move your device closer to the router and away from obvious obstructions. If you reposition equipment, keep it ventilated and follow the manufacturer’s guidance. Record the old position so you can reverse an unhelpful change.
Use measurements carefully
Record the time, location, device and test service alongside any speed or latency result. Repeat a test rather than relying on one unusually good or poor reading. Download speed alone does not explain every interrupted call or slow website; stability and responsiveness also matter.
An example log might say: “Laptop, desk, 7:30 p.m.; call freezes; phone in the same place also struggles; both work beside router.” That gives a technician a useful pattern without claiming that a particular advertised speed will solve it.
Know when to escalate
If several devices and services fail even close to the router, consult the provider’s status information and support. Share your comparison results and ask whether there is a line or service issue. If only one device fails on multiple known-good networks, investigate that device through its manufacturer’s support.
Before buying equipment, write down the specific problem the purchase is meant to solve. A new router cannot fix an outage at the provider or a broken remote website. For resilient work during interruptions, use the app portability and offline checklist.
Sources
Reviewed on 28 October 2026: Microsoft’s Wi-Fi troubleshooting guidance and Apple’s Wi-Fi connection guidance. Device-specific reset or configuration steps should come from your equipment’s official instructions.