A speed test on your phone can tell you that the bedroom connection is slow. It can’t tell you why. The same low result could come from your internet provider, a weak signal through two walls, a busy Wi-Fi channel, or the phone itself.
The useful test is a comparison: measure the connection at the router, then measure Wi-Fi close to it and in the places where you actually use it. Keep the device, test site, and time of day as consistent as you can. The pattern matters more than any single number.
Start with a clean baseline
Check the download and upload speeds on your internet plan before testing. If you have a “Broadband Facts” label for the plan, it should show typical download speed, upload speed, and latency. Those figures are a reference point, not a promise that every device will hit them over Wi-Fi.
Pick one test and use it throughout your first round. Cloudflare’s speed test reports download and upload speeds along with latency, jitter, and packet loss. Run it two or three times per location rather than treating one result as definitive. Speed tests measure a path to a particular test service; server choice, congestion, and conditions inside your home can change the result.
Before each test, pause large downloads, cloud backups, game updates, and streaming on other devices. Disconnect a VPN temporarily if you can do so without disrupting work requirements. On a phone, confirm that you’re connected to your home Wi-Fi rather than cellular data.
Write down the results. A note such as “laptop, Ethernet, 8 p.m., 290 Mbps down/18 Mbps up” is far more useful than a screenshot with no context. Repeat a few tests when the slowdown normally happens, especially if it’s confined to evenings.
Test the internet connection without Wi-Fi
Connect a laptop or desktop to a LAN port on the router with an Ethernet cable, turn off that computer’s Wi-Fi, and run your chosen test. This removes the wireless link between the computer and router from the measurement. If the computer lacks an Ethernet port, a USB-to-Ethernet adapter is an option.
If your router offers a built-in internet speed test, you can run that too. On compatible Nest and Google Wifi systems, for example, the router’s test measures download and upload speeds from the primary router or point, not from your phone in the next room. That makes it useful for comparison with device tests. A wired computer test still helps catch a problem in the cable or port between that computer and the router.
If the wired result is close to your plan’s typical speed but Wi-Fi is much slower, focus on the wireless network. If the wired result is poor, don’t buy a Wi-Fi extender yet. First check the router-to-modem cable, restart the modem and router, and test again. If available, try a different cable and a suitable port. A 100 Mbps port or connection anywhere on a path can limit a faster service; a result that repeatedly tops out near 100 Mbps is a reason to check port speeds and connections.
A slow wired test doesn’t prove that the provider is at fault. The router, modem, computer adapter, cables, and activity elsewhere in the home remain possible causes. If the result stays well below your plan’s typical speed after those checks, save several dated wired results and contact your provider. Ask them to check the line, equipment, and any local service issue.
Map the slowdown room by room
Using the same Wi-Fi device, run the test a few feet from the router, then in the problem room. Test from your usual spot—not just the doorway. If you have a mesh system, note which point the device is using, if the app shows it.
This comparison gives you a practical decision tree:
| Test pattern | Most likely place to investigate | First move |
|---|---|---|
| Wired and Wi-Fi tests are both slow | Internet service, modem, router, cables, or shared household traffic | Pause heavy use, check connections, restart equipment, and retest wired |
| Wired speed is good; Wi-Fi is slow even near the router | Wireless settings, interference, or the test device | Try a second device near the router and check its band |
| Wi-Fi is good near the router but poor in one room | Distance, walls, floors, or a weak mesh connection | Move the router or mesh point, then retest |
| One device is slow everywhere; others are fine | That device’s Wi-Fi hardware, software, or background activity | Test it beside a faster device and check its updates and VPN |
| Speed falls mainly when the household is busy | Competing downloads or limited plan capacity | Check router traffic and repeat with heavy use paused |
These patterns narrow the search; they aren’t diagnoses on their own. For example, a weak room can also have interference, and a slow wired test can be affected by a busy computer. Change one thing at a time and rerun the same comparison.
A simple worked example shows why: suppose a 300 Mbps plan tests at 280 Mbps over Ethernet, 240 Mbps on a laptop near the router, and 35 Mbps on that same laptop in an upstairs office. The provider connection looks reasonably healthy during those tests. Paying for a faster plan is unlikely to fix the sharp drop between the router and office; improving coverage is the more direct next step.
Use the pattern to choose a fix
If speed drops with distance, move the signal—not the plan
A router tucked behind a TV, in a cabinet, or at one end of the house has a harder job than one placed out in the open. Try a more central, elevated position and keep it away from large metal objects. Microsoft recommends testing after each placement change, so you can tell whether a move helped rather than relying on the signal icon.
If moving the router isn’t practical, consider an additional access point or mesh point near the area that needs coverage. Don’t put a wireless mesh point in the dead zone: it must also receive a good connection from the main router or another point. On Nest and Google Wifi systems, a mesh test checks the link between points; a weak result calls for moving the point closer or reducing obstructions. Where practical and supported by your equipment, an Ethernet connection to the added access point avoids depending on a weak wireless link between locations. Nest Wifi points do not have Ethernet ports and cannot be hardwired.
If signal looks strong but performance varies, check interference
Neighboring networks, microwaves, and other devices can disrupt Wi-Fi, particularly on 2.4 GHz. A clue is speed that swings widely in the same spot while the wired test remains steady. Another is a slowdown tied to using a nearby appliance.
First, try the 5 GHz band on a device that supports it. Some routers choose a band automatically, so check the router app or device details before assuming you’re on 5 GHz. The 2.4 GHz band may still serve a distant room better, even if its peak speed is lower. If interference remains a problem, Apple recommends trying a different channel or letting the router scan for a less crowded one. Make one change, then compare several tests in the same place.
Don’t blindly set the widest channel available in search of a bigger speed-test number. Apple’s router settings guidance recommends 20 MHz channel width on 2.4 GHz to reduce reliability problems near other networks and devices. Leave channel selection on Auto unless repeat tests give you a reason to adjust it.
If only one device is slow, test the device
Put the slow device beside one that performs well and test both on the same network. If the gap persists near the router, check whether the slow device has joined a different band, is running a backup or update, or improves when its VPN is off. Restart it and install available operating-system and Wi-Fi adapter updates.
The router cannot make an older device support wireless capabilities it doesn’t have. Wi-Fi speed depends on both the router and the connected device. If that one device needs a reliable connection for work or gaming, Ethernet may be a better fix than replacing a router that serves everything else well.
Read more than the download number
Download speed describes data arriving at your device. Upload speed matters when you send video, back up files, or share your screen. Latency is the delay in a round trip to the test service; jitter is how much that delay varies. Packet loss means some test data did not arrive. A connection can post an impressive download result yet still feel poor on calls if its delay or packet loss spikes.
Match the numbers to the task. Netflix recommends a stable 15 Mbps or more for one 4K stream, while Zoom lists separate upload and download requirements for HD group video. These are application needs, not speed targets every room must exceed by a set margin. Several people using the connection at once need shared capacity, and a steady connection matters as much as a high peak result.
If problems begin only when someone uploads a large file, test while that upload is running and again when it stops. A jump in latency during the upload points to contention or a connection that handles load poorly—not necessarily weak Wi-Fi. Likewise, if every speed test looks healthy but one website or app is slow, try another service before changing your home network.
Keep the results that answer a question: wired versus wireless, near versus far, one device versus another, quiet household versus busy household. If you do change router settings while troubleshooting, review the settings that help secure your home Wi-Fi router rather than weakening security to chase speed. Once you know where the drop begins, the next fix is usually much smaller—and cheaper—than replacing everything.