Why Is My Wi-Fi Slow?

A useful diagnosis changes one layer at a time.

Check whether one or every device is affected, repeat beside the router, then compare with a wired connection. One speed test cannot prove ISP throttling or failing hardware.

Use the same server, device, and time window.

Record plan speed, typical speed from the broadband label, wired throughput, Wi-Fi throughput, and latency. Disable VPN only for the controlled comparison if policy permits.

Location and device patterns narrow the class of cause.

Normal wired speed with room-dependent Wi-Fi points toward coverage or interference. A single slow client points toward that device. Weak wired results deserve an upstream check.

The next test should be cheaper than replacement hardware.

Use the symptom tool to choose the next observation. Keep the result as screening evidence and contact the ISP with timestamps and wired measurements when the upstream path remains weak.

Use a small repeatable test, not a screenshot of the worst result.

Illustrative case, not a product test. These inputs are invented to make the reasoning reproducible. Replace them with your own observations; the result is not a typical household or product benchmark.

This fictional household has a 300 Mbps download plan. One laptop runs the same test against the same test service in a short, quiet time window. Each location is tested three times; the middle value is shown below. Upload and latency should be recorded too if the symptom is video calls rather than large downloads.

The useful finding is the pattern, not a promised speed threshold: the distant room differs sharply from the same laptop beside the router. Buying a faster internet plan is not the first experiment suggested by those observations. Try a safer, more open router position or a different location for the client, then repeat the comparison. Keep the starting measurements so you can tell whether the change helped.

These results do not prove which wall material, band or interference source caused the difference. They also do not guarantee that a new mesh kit would solve it. If a second device stays fast in the back room, investigate the first client as well. If wired results are weak too, verify the wired adapter, cable and port capability before concluding the service provider is at fault.

Write down enough context to reproduce the observation.

1. Identify the symptom: one device, one room, one app, a certain time, or the whole network.
2. Record the device, location, connection type, test service and time. Avoid posting network passwords or public IP addresses.
3. For a controlled comparison, pause only nonessential downloads under your control. Follow workplace policy; do not disable security controls to improve a benchmark.
4. Repeat near the router and in the problem location. If you have an appropriate wired connection, test it using the same device.
5. Change one placement or connection variable, repeat, and record whether the actual task improved.

Google’s Nest Wifi troubleshooting guide identifies distance, obstacles, device capability and other traffic as factors in wireless performance. Its app instructions are product-specific; the comparison above is Practical Atlas’s own diagnostic exercise, not a Nest performance test.

Do not factory-reset the router as the first step. That can remove settings and disrupt other users. A site that is slow while other services work normally may have a service-side issue; a whole-network replacement would not follow from that evidence. Use the Wi-Fi diagnosis tool to choose the next observation, then use your equipment’s current official instructions for any settings change.

Give a pattern and the conditions, not an accusation.

A useful support note is: “On the same laptop and test service, Ethernet was 285 Mbps, Wi-Fi near the router 240, and the back room 28. I repeated each location three times during the same quiet period. Moving the router changed the back-room result to 65, but calls still drop.” Those invented figures illustrate a concise report; replace them with your own and describe the actual call or download problem.

If all devices lose service, include the outage time and any relevant status indicators. If a single device is affected, include its connection type and whether another device works in the same location. Keep account identifiers in the provider’s private support channel. Stop changing settings when you cannot recover the previous state or you are not authorized to administer the network.