How to Run a Full Home Network Speed Audit: Testing Every Device, Room, and Connection Point to Find Your Real Bottleneck

Running a speed test at your desk and calling it done only tells you one number: how fast the internet arrives at that one device, at that one moment. A real home network audit maps your connection from the street to every device in every room, isolating exactly where speed gets lost. Here is how to do it methodically.

Step 1: Establish Your Baseline at the Modem

Before testing anything inside your home, you need a reference point for what your ISP is actually delivering. Plug a laptop directly into the modem’s output port with an Ethernet cable — bypassing your router entirely — and run a speed test at wifispeed.com. Record the download speed, upload speed, and ping. This is your ceiling: no device anywhere in your home can legitimately exceed it.

If the modem result is consistently 15–20% or more below your plan speed, the bottleneck is upstream of everything else: the modem itself, the coax or fiber drop, or ISP-side congestion. Our guide on how to check if your ISP is throttling your connection covers what to do next in that scenario.

Step 2: Test the Router’s Wired Output

Reconnect the modem to your router, then plug the same laptop into a LAN port on the router. Run the speed test again. The result should be within 5% of your modem baseline. A significant drop here points to one of three things: the router’s CPU is the bottleneck (common on budget routers at gigabit speeds), there is a bad Ethernet cable between the modem and router, or your router’s WAN port is limited to 1 Gbps while you are on a multi-gig plan. Identifying this early tells you whether any WiFi problems downstream are really router problems in disguise.

Step 3: Walk Every Room With a Laptop

This is the most time-consuming step and the most revealing. Carry a laptop to each room, connect to WiFi, and run a speed test. Record the download speed, the WiFi band you connected to (2.4 GHz, 5 GHz, or 6 GHz), and the signal strength shown by your OS network indicator or a WiFi analyzer app.

What to Look For Room by Room

• Speed drops of more than 50% from the wired baseline in any room indicate a coverage gap. An additional access point or mesh node near that room is the fix. Our guide on extending WiFi to hard-to-reach spaces walks through the options.
• Speed is adequate but latency is high — above 20 ms to a nearby server — suggests channel congestion or interference rather than a signal-strength problem. See our guide to common WiFi interference sources for the most frequent culprits.
• 5 GHz speeds are dramatically worse than 2.4 GHz in a specific room: the router is too far away or there is a wall type blocking the shorter-range 5 GHz signal. 2.4 GHz travels farther and penetrates walls better, but tops out at a fraction of 5 GHz throughput in close range.

Signal Strength Numbers That Matter

WiFi Analyzer (Android, free) and NetSpot (Windows and macOS, free tier available) display signal strength in dBm, which is more precise than the bar indicators built into your OS. A reading of –50 dBm is excellent; –70 dBm is workable for browsing but marginal for 4K streaming; anything below –80 dBm will produce dropped packets and inconsistent speeds. If you see –75 dBm or worse in a room you use regularly, that room needs a coverage fix before any other optimization will matter.

Step 4: Test Internal LAN Throughput with iperf3

Internet speed tests measure your connection to an external server, which can be affected by server load and routing outside your control. To measure your actual home network throughput — how fast devices talk to each other and how fast a device talks to your router — use iperf3. It is free, open-source, and available for Windows, macOS, Linux, and Android.

Install iperf3 on two devices: a desktop or laptop connected via Ethernet acts as the server, and the device under test is the client. On the server, run iperf3 -s. On the client, run iperf3 -c [server-ip-address] -t 30. The 30-second window smooths out short-term fluctuations. Healthy results to expect:

• Wired Gigabit Ethernet to Ethernet: 940–960 Mbps
• WiFi 6 or WiFi 7 in the same room as the router: 800–1,800 Mbps depending on channel width and link rate
• WiFi 5 (802.11ac) in the same room: 300–600 Mbps
• 5 GHz WiFi across the house: 100–400 Mbps depending on distance and walls

Results below 100 Mbps on any 5 GHz connection within line of sight of the router suggest a configuration issue, driver problem, or interference worth investigating. Results below 50 Mbps on 2.4 GHz in a room near the router indicate channel saturation — check what your neighbors are broadcasting on with a WiFi analyzer.

Step 5: Test Every Device Individually

Slow speeds on a specific device are often a device problem rather than a network problem. Run a speed test directly on each device that feels sluggish, not just your laptop. A smart TV that streams at 20 Mbps from across the room may have a single-antenna 2.4 GHz WiFi chip that physically cannot do better — adding a mesh node will not help if the TV’s radio is the limiting factor. A desktop PC showing 200 Mbps on WiFi but 940 Mbps on Ethernet has a working network but a WiFi chip that is underperforming; an Ethernet cable or a USB WiFi adapter upgrade solves it without touching the router. Knowing this distinction prevents unnecessary hardware purchases.

Step 6: Run Tests at Peak and Off-Peak Hours

Repeat the full audit twice: once during quiet hours (early morning or late night) and once during peak hours (7–10 PM on weeknights). If modem baseline speeds are consistent across both periods, your ISP is delivering what you pay for and any slowdowns are an internal home network problem. If modem speeds drop significantly during peak hours, your ISP’s neighborhood node is oversubscribed — no amount of internal optimization will fix that, but the data gives you clear evidence to present when contacting your provider.

Reading Your Results: Locating the Real Bottleneck

With audit data from every step, the bottleneck location becomes clear by process of elimination:

• Modem baseline is low → ISP delivery or modem issue. On a DOCSIS cable connection, log into the modem admin page and check downstream power levels; values outside –7 to +7 dBmV or high uncorrectable errors indicate a signal problem on the coax drop.
• Router wired output is low relative to modem → Router CPU, WAN port speed cap, or the cable between modem and router. Swap the cable first; it costs nothing.
• WiFi speeds drop sharply in specific rooms → Coverage gap. The fix is placement, an additional wired access point, or a mesh node. See our mesh systems vs access points comparison for the best approach for your home.
• One device is slow everywhere on the network → Device hardware, driver, or software issue, not the network infrastructure.
• All devices slow at peak hours only → ISP congestion. Document the results and escalate with your provider.

The Bottom Line

A complete home network speed audit requires no specialist tools beyond a free speed test, iperf3, and a WiFi analyzer app. The payoff is a clear, location-specific map of where your connection degrades and why — so you invest in the right fix rather than guessing. Run a speed test now to capture your first baseline reading and start the audit from the most important number: what your ISP is actually delivering at the modem.