If your internet suddenly becomes slow, first check what changed and how widely the problem appears. One slow application, one slow device, weak Wi-Fi in one room and a slowdown across wired devices need different investigations. A quick comparison can prevent unnecessary resets or a plan upgrade that does not address the problem.
Start with the symptom, check relevant service status, and change one condition at a time. The guided slow-internet troubleshooter can help choose the next branch; the detail below explains how to interpret what you find.
Start with three low-effort checks
- Check the affected service and your provider’s status. If one application is reporting an incident, changing the whole home network may not help. If the provider reports a local fault, record its reference and expected update rather than repeatedly resetting your equipment.
- Look for active transfers. A game update, backup, camera upload or another device can change the available capacity even if you did not start a new task.
- Check another ordinary activity. Try a different website or application on the same device, then compare a second device on the same home network. Confirm that a phone did not silently switch to mobile data.
Record when the change started, whether it was sudden or gradual, and whether the same task worked earlier. This creates a useful baseline. “Slow today” is less specific than “Both wired computers were slow after 7 pm, while the provider’s status page showed no incident.” That sentence is a template for your observations, not a finding from our testing.
Identify which part of the connection is affected
| Scope | What to compare | What not to assume |
|---|---|---|
| One app or website | Its status, account, upload queue and another service | That the whole internet connection is slow |
| One device | Another device using the same local connection | That the ISP must be the cause |
| One room or Wi-Fi only | The same device near the router and on Ethernet | That a larger plan repairs wireless coverage |
| All devices, including Ethernet | Provider status, shared equipment and quiet-period tests | That every device developed a fault independently |
| Mostly while the network is busy | A paused-transfer comparison and application telemetry | That a high idle speed guarantees responsiveness under load |
If the network actually disconnects rather than merely slowing, use the Wi-Fi disconnect investigation. A connection that drops completely requires different evidence from one that remains connected but transfers data slowly.
Make a small set of comparable tests
Use the device that has the problem and pause nonessential transfers you control. Run a manual internet speed test, keeping the mode and test destination consistent for the comparison. Read its data estimate, particularly on a mobile or capped connection; more repeated tests are not automatically better evidence.
Repeat the same task on Ethernet through the router if practical. If not, move the same device near the router and note the location change. Record download, upload, the symptom and other traffic. Do not compare unrelated devices and declare the router responsible simply because one result is larger.
A router’s built-in result may bypass the device’s Wi-Fi link. Google explains that its Nest and Google Wifi test measures from the router or primary Wifi point. A healthy result there alongside a poor device result makes the local path worth examining; it is not the same measurement as the browser on that device.
Use the room comparison tool for a location pattern. For an upload-only issue, take the narrower route through upload-speed diagnosis. Avoid changing DNS, channel width, drivers and router settings together, because the result will not tell you which change mattered.
Common causes, with evidence to look for
A background job is using the connection
A newly active transfer can make a previously adequate connection feel slow. Pause one nonessential job, repeat the affected activity, and resume it afterward. If that comparison helps, choose a schedule or supported rate control rather than leaving important backups permanently disabled.
For example, Dropbox documents desktop bandwidth controls. Other applications have different settings. A client limit may also explain the opposite pattern: one application remains slow even while the rest of the connection performs normally.
The wireless path changed
A moved device, an access-point problem or a changed radio environment can affect the normal room without reducing the service delivered to the router. Compare location and Ethernet before choosing a hardware purchase. A full signal icon does not certify throughput, and an internet speed test is not a radio-channel scan.
On Windows, begin with the supported steps in Microsoft’s Wi-Fi troubleshooting guidance. On a Mac, Apple’s Wi-Fi internet-access guidance covers recommendations and diagnostic options. Follow the actual device and network context instead of applying every reset listed online.
The device or application is busy
A browser struggling to render pages is not always a slower internet link. Compare another application and another device, and note whether the computer is also handling a demanding local job. Many idle tabs are different from tabs actively streaming, uploading or downloading. Closing a heavy task may improve the device without changing the network’s capacity.
Similarly, a cloud service may be preparing or processing a file rather than transmitting at the displayed rate. Check its progress stage and current incident information before treating the remaining-time estimate as a direct measurement of your internet service.
Usage policy, congestion or a shared access problem
Check your account’s remaining allowance and actual plan rules if the slowdown follows heavy use. Do not infer a fixed throttled speed from a low result. For US services, the FCC’s broadband-label explanation shows where speed and data information fit in a plan comparison.
A recurring busy-hour pattern is worth recording under comparable conditions. It can be consistent with congestion, but does not prove its location or intent. A different result from another speed-test destination or a VPN also changes the route; it is not proof of deliberate throttling. If lag appears mainly under household load, the loaded-latency test addresses a specific part of that question.
Restart once when appropriate, then preserve the evidence
A manufacturer-documented restart can be a reasonable controlled step after saving work and allowing for the interruption. Record whether it helped and for how long. A factory reset is a much larger change and should not be the first response to one slow result. Do not bypass the router or expose a device directly to an unfamiliar connection just to follow a generic checklist.
Contact the provider when a known incident persists, service remains unavailable, or several wired devices repeatedly show an unexplained reduction. Send a concise private record: plan, times, device and connection, comparable results, affected applications and steps already taken. Ask which additional line or equipment checks are appropriate.
Should I upgrade the plan now?
First separate a newly degraded service from an existing capacity limit. If normal performance matches the plan but your activities have grown, a larger upload/download budget may help. If the issue follows one device, room or destination, a higher tier may leave the underlying problem untouched.
Reviewed 27 October 2026. The comparison workflow does not claim a measured outage, a guaranteed cause or a successful hardware fix.