Troubleshooting

Why Is My Internet Slow?

Find where slow Internet use begins with controlled device, Wi-Fi, Ethernet and service comparisons, then choose a suitable next step.

Slow Internet can mean a file arriving slowly, an upload taking too long, a page waiting to open or video repeatedly buffering. These symptoms need different comparisons. A Wi-Fi and Ethernet test can narrow the investigation, but it cannot by itself separate every home-network problem from every Internet-path problem.

Record the problem before restarting

Write down the task, affected service, start time and whether it is slow continuously or intermittently. Distinguish slowness from a complete loss of connectivity.
Note the device, location and connection type. Check whether another device has the same symptom, remembering that its adapter, software and capabilities may differ.
Save relevant errors and the router's connection status before restarting. Note your own cloud backups, updates and large transfers that overlap the problem.
Check the provider's and affected service's official status information. A matching incident is a useful clue; the absence of a published incident does not prove that every connection is healthy.

Make a comparable baseline measurement

Use the same device, test method and target, and record the time, location, Wi-Fi band or access point if visible, VPN state and other traffic. Keep required security and managed settings in place. NDT measures a TCP transfer over the path to an Internet server, not just your access line or the performance of every app. Record download, upload and latency with their units. A rate of 1 MB/s corresponds to 8 Mbps; latency from a test is not the entire time an app takes to respond.

Change one condition at a time

If the equipment supports it, compare the same device on a suitable router LAN port with its usual Wi-Fi location, then with a closer Wi-Fi location. Cable, port and adapter limits can also affect an Ethernet result.
Repeat the affected task on another device using the same service and comparable conditions. Run speed tests separately so the tests do not compete with each other.
If one service is slow, compare another relevant service or a supported app or browser for the same task. A fast test server does not clear the route to the slow service.
If evenings are worse, repeat comparable observations during the problem and at another time. Record other traffic. A time pattern can involve local use, the provider path or the service; it is not proof of one cause.

Better Ethernet results suggest investigating the Wi-Fi path and device conditions, not automatically replacing the router. Poor results on both connections can still involve the device, local equipment or the outside path. Repeated comparable observations are more useful than a single best result or a fixed rule about how many tests are enough.

Choose an action that fits the evidence

Temporarily pause your own large transfers and repeat the task, then resume them. Improvement suggests investigating shared load; it does not automatically justify buying a faster plan.
In Windows 11, use the Network and Internet troubleshooter in Get Help and review proposed changes. On a Mac, hold Option while opening the Wi-Fi menu and select Wireless Diagnostics; that tool does not change network settings.
Use official instructions for the actual device or router model. Apply a relevant update or setting change individually, retest and retain a way to undo it. Do not treat a factory reset or disabling protection as a general speed fix.
If a restart is appropriate, save observations and finish important work first. It also disconnects other users. Follow the model's instructions and wait for actual readiness; improvement after restarting does not establish the original cause.

Contact the relevant provider, service or device support with the affected task, times, connection types and comparison results. Compare line measurements with the plan's stated measurement conditions, not just an advertised maximum. Describe observations and actions rather than claiming causes have been ruled out. Check diagnostic files and screenshots for passwords, identifiers and personal data before sharing them privately.