How can I test my home WiFi speed and stability?

Wifi
1

I’ve been having random slowdowns and disconnects on my home WiFi, but I’m not sure if the issue is my router, my ISP, or my devices. What’s the best way to accurately test WiFi speed, signal strength, and stability over time so I can figure out what’s really causing the problem?

2

Short version, you want to test three things separately: ISP speed, WiFi quality, and device issues.

  1. Check your ISP first
    • Plug a laptop into the router with Ethernet.
    • Turn off WiFi on that laptop.
    • Run tests on:
  • speedtest.net
  • fast.com
    • Do 3 to 5 tests at different times: morning, evening peak, late night.
    • Compare results with what you pay for.
    If Ethernet is slow or unstable, the problem is your ISP or modem, not WiFi.

  1. Check WiFi speed only
    • Stand 5 to 10 feet from the router, line of sight.
    • Use the same laptop or phone, on WiFi this time.
    • Run the same speed tests, again multiple times.
    If Ethernet is fine but WiFi is much slower or drops a lot, your WiFi setup is the issue.

  2. Check WiFi in different rooms
    • Walk to each room where you use WiFi.
    • Run a speed test in each spot.
    • Note download, upload, ping, and jitter.

  • Ping under 30 ms is good.
  • Jitter under 10 ms is decent.
    If far rooms are bad but near the router is fine, you have coverage or interference issues.
  1. Check signal strength and noise
    Install a WiFi analyzer app:
    • On Windows or macOS, use something like NetSpot.
    • On Android, search for “WiFi analyzer”.
    Apps like analyzing and improving your WiFi coverage help you see:
    • Signal strength in dBm.
  • Better than −60 dBm is strong.
  • −60 to −70 dBm is okay.
  • Worse than −75 dBm is weak.
    • Channel usage.
    If your network overlaps with many neighbors on the same channel, change your WiFi channel in the router settings.
  1. Check stability over time
    For PC:
    • Open Command Prompt or Terminal.
    • Run:
  • ping 8.8.8.8 -t on Windows
  • ping 8.8.8.8 on macOS or Linux
    Let it run for 5 to 10 minutes while you browse or stream.
    Watch for:
    • Packet loss above 1 to 2 percent.
    • Big spikes in ping, for example 20 ms, then 500 ms, then timeouts.
    If ping to 8.8.8.8 is messy but ping to your router IP is clean, the issue is outside your WiFi, likely ISP.
    If ping to your router IP drops, the WiFi or router is the issue.

  1. Separate router vs WiFi radio
    • Test ping to router IP, usually 192.168.0.1 or 192.168.1.1.
    • Do it over WiFi, then again over Ethernet.
    If Ethernet ping is solid but WiFi ping drops, the wireless radio or interference is the problem.
    If both are bad, the router is not stable.

  2. Common fixes once you have data
    If WiFi is weak in some rooms:
    • Move router higher, away from metal, aquariums, and thick walls.
    • Use 2.4 GHz for range, 5 GHz for speed.
    • If your place is large, think about a mesh system or extra access point.
    If interference shows in NetSpot or other analyzers:
    • Change channel on 2.4 GHz to 1, 6, or 11 and pick the least crowded.
    • On 5 GHz, use a channel with fewer overlapping networks.
    If only one device is slow:
    • Forget the network on that device and reconnect.
    • Update its WiFi drivers or OS.
    • Test it on another network to see if the issue follows the device.

  3. Simple testing routine
    Do this for a week:
    • Morning, evening, late night.
    • Note:

  • Ethernet speed.
  • WiFi speed near router.
  • WiFi speed in your worst room.
  • Ping behavior.
    Write it down. Patterns help. For example, if everything drops at 8 pm daily, that points to ISP congestion, not your gear.

If you want one tool focused on WiFi mapping and signal study, NetSpot is solid. It shows signal heatmaps, channel overlap, and noise levels, so you see exactly where your WiFi dies instead of guessing.

1 Like
3

First thing: don’t only rely on speedtest sites. They’re useful, but they hide a lot of what’s actually going wrong.

@chasseurdetoiles already covered the classic “ISP vs WiFi vs device” checks pretty well, so I’ll skip repeating those step by step and focus on more “nerdy but practical” tests and some stuff I disagree with a bit.

1. Test inside your network, not just out to the internet

Speedtests hit remote servers. That includes your ISP, their congestion, routing, etc. To really see if your WiFi is the problem:

Set up a local throughput test:

  • Use two devices on your network:
    • One wired to the router with Ethernet
    • One on WiFi (the one you suspect has issues)
  • Install iperf3 on both (Windows/macOS/Linux all support it).

On the wired machine:

iperf3 -s

On the WiFi machine:

iperf3 -c <wired_machine_LAN_IP> -t 30 -i 1

Now you’re measuring pure WiFi performance (no ISP involved):

  • If this is solid (stable Mbps, no crazy dips) but internet speedtests are erratic, blame ISP or modem.
  • If iperf jumps like 200 Mbps, 10 Mbps, 0, 150, then yeah, your WiFi link is a mess.

This is more accurate than just comparing Ethernet vs WiFi speedtests like people usually suggest.

2. Look at WiFi quality over time, not just snapshots

Most folks run a speedtest, see “OK, 150 Mbps” and stop. That tells you nothing about why Netflix stutters every 5 minutes.

Instead, leave a monitor running:

  • On a laptop: run constant ping to your router and to some external host (e.g. 8.8.8.8), like @chasseurdetoiles said.
  • At the same time, run a tool that logs WiFi signal and noise.

This is where NetSpot shines. Yeah, it’s known for heatmaps, but the underrated feature is just watching signal levels and channel overlap as they fluctuate.

Use something like:

  • Walk around and record signal, channel, and noise for 10–20 minutes.
  • Note the time when you feel lag or disconnects.
  • Check the logs: did signal suddenly drop, or did interference spike?

If your random slowdowns match spikes in noise or drops in signal, that’s classic WiFi interference, not ISP throttling.

3. Test for environmental interference

People blame routers for stuff that’s actually caused by their house being a RF dumpster.

Quick checks you won’t get from speedtest.net:

  • Turn off or unplug these temporarily:
    • Microwave
    • Baby monitors
    • Cheap wireless cameras
    • Old cordless phones
    • Bluetooth speaker spam
  • While each one is off, rerun pings and maybe a local iperf3 test.

If your pings suddenly smooth out when some random gadget is off, that’s your culprit.
I disagree slightly with the idea that channel changes alone always fix things. If a neighbor’s AP blasts at max power or you have a super noisy device, no magical channel “1/6/11” choice fully fixes it.

4. Check 2.4 GHz vs 5 GHz the right way

Everyone says “2.4 = range, 5 = speed,” which is true-ish but incomplete.

You want to test like this:

  1. Force your device to 2.4 GHz only.

    • Many routers let you split SSIDs into “MyWiFi_2G” and “MyWiFi_5G”.

  2. Run:

    • A local iperf3 test
    • Continuous ping to router and to 8.8.8.8 for ~5–10 minutes

  3. Then repeat on 5 GHz only in the same room and again in the far room.

If far-room 5 GHz is fast but randomly drops to 0 or disconnects, it’s not just “weak signal,” it’s borderline usable. In that case, a slower but stable 2.4 GHz connection is actually better than a “fast on paper” 5 GHz with constant drops.

So, don’t chase “highest Mbps.” Chase the line that’s the least spiky over time.

5. Don’t forget the router’s CPU and heat

Routers get overloaded, especially cheap ISP ones.

Quick tests:

  • Log in to the router admin page:
    • Look for CPU load and temperature if shown.
  • Start a heavy download or stream on multiple devices.
  • While that runs, keep refreshing the router status.

If CPU usage is pegged at 90–100% during heavy use and that’s when disconnects happen, your WiFi radios might be fine but the router is choking.

Also check:

  • Is it hot to the touch?
  • Is it crammed in a cabinet, behind a TV, or on top of another hot box like a cable modem?

Test this by temporarily:

  • Putting it in open air
  • Removing clutter around it
  • Retesting during your usual “bad” time

If stability improves, you just diagnosed thermal throttling or overload, not ISP or pure WiFi signal issues.

6. Per-device testing, but more systematic

“Only one device is slow, so that device is the issue” is mostly true but not always. Sometimes one device simply has the weakest antenna and shows the problem first.

Try this:

  • In the same location, same time, same WiFi band:
    • Run speedtests on 2–3 different devices.
    • Run ping to router on each for 5 minutes.
  • Compare:
    • If all devices show similar spikes at exactly the same moments, that’s WiFi or router or ISP.
    • If only one is constantly bad while others are fine, then yeah, that device’s radio/driver is suspect.

Bonus: take that “problem” device to another house or public WiFi and test there. If it’s still garbage, mystery solved.

7. Use mapping, not just numbers

Since you asked about signal strength and stability, visualizing it beats reading dBm lines in a table.

NetSpot is actually very solid for this, especially if you care about SEO stuff like “how to improve WiFi coverage and stability” and “optimize home WiFi networks” because it does:

  • Signal heatmaps
  • Channel overlap visualization
  • Per-room signal quality

Instead of guessing, you literally see: “This corner of the bedroom is where the WiFi goes to die.”

If you’re curious about getting serious with it, check out in depth tools to boost your WiFi performance so you can actually map dead zones, pick better channels, and validate changes instead of changing settings blindly.

8. Simple data-driven routine

In practice, a minimal but solid testing plan for a few days:

  • Morning, evening, late night:
    1. Local iperf3 WiFi test (WiFi device to wired device)
    2. ISP speedtest (Ethernet only)
    3. 5–10 minute ping logs:
      • To router
      • To 8.8.8.8
    4. Log where you were and which band (2.4 or 5 GHz)

You don’t need to obsess, just grab enough samples to see patterns.
If:

  • ISP speed dips only at busy hours, WiFi is probably fine.
  • Local WiFi throughput and ping are trash even when ISP Ethernet is good, WiFi is the villain.
  • Only one room is consistently bad, that’s placement and coverage.

It’s a bit of work, but you end up with real evidence instead of “it feels slow sometimes,” which is how ISPs and bad routers get away with everything.

4

You already have the “how to test” playbook from @stellacadente and @chasseurdetoiles. I’ll zoom out and focus on interpreting what you see and what to actually change, plus some nuance on tools like NetSpot.

1. How to read your results so you know who to blame

Instead of more tests, use a simple decision tree based on what you already measured:

  1. Ethernet bad, WiFi bad, all times of day:

    • Likely ISP, bad modem, or bad line to your home.
    • Action: collect screenshots of speedtests and ping to share with ISP support. Ask them to test line quality and error counts, not just “speed.”

  2. Ethernet good, WiFi near router bad, all rooms bad:

    • Router’s wireless radio, firmware, or serious interference.
    • Action:
      • Update router firmware.
      • Test briefly with a different router or AP if you can borrow one.
      • If a cheap ISP combo box is doing routing + WiFi + modem, consider using it in “bridge” mode and adding your own decent router.

  3. Ethernet good, WiFi good near router, bad only in some rooms:

    • Coverage and building materials are your enemy, not your ISP.
    • Action:
      • Reposition router vertically and centrally.
      • Rotate antennas 90 degrees relative to each other if you have them.
      • If you have more than ~70 m² or multiple floors, accept that you probably need a mesh or extra access point.

  4. Ping to router clean, ping to internet messy:

    • Local WiFi is fine. Problem is upstream (ISP or their routing).
    • Action: log times, servers affected, and contact ISP. Use that log as “evidence” so they skip the basic script.

  5. Ping to router itself spikes or drops:

    • That is WiFi quality or router overload.
    • Action: change channels, change placement, or replace router. No ISP call will fix it.

2. 5 GHz vs 2.4 GHz without chasing meaningless “top speed”

I slightly disagree with the common “always use 5 GHz if you can” story.

Use this mental model:

  • Near router:

    • Prefer 5 GHz for speed and less interference.
    • If you see random drops or disconnects in the same room, that is more likely router quality or interference from neighbors than band choice.

  • Far room, 1 or 2 walls away:

    • Try both bands. Trust whichever gives the smoothest ping graph and video calls, not the one with the highest single speedtest.
    • If 5 GHz swings from “fast” to “dead” whenever you move, lock that device to 2.4 GHz in that room.

If your router has one SSID for both bands and keeps flipping you between them, that can cause weird slowdowns. Splitting names like “Home_2G” and “Home_5G” and choosing manually is sometimes more stable than “smart connect.”

3. Smart use of NetSpot instead of just running it once

NetSpot is really useful, but only if you go beyond “one scan and a pretty picture.”

Pros:

  • Shows you signal strength in each room in a way that is easy to understand.
  • Lets you see which channels your neighbors are using, so channel changes are based on data instead of guessing.
  • Heatmaps help answer “do I need mesh?” instead of buying extra hardware blindly.

Cons:

  • It can be overkill if all you need is “does my router suck.”
  • The free version has limitations, and some people never touch the advanced features they paid for.
  • It still does not fix anything by itself; you need to act on what it shows.

How to use it effectively once:

  1. Walk your home with a laptop, mark rooms, collect data.
  2. Identify 2 or 3 worst zones and see:
    • Is the signal simply weak (less than about -70 dBm)?
    • Or is the channel totally crowded while signal looks fine?
  3. Change router position or channel, then run NetSpot again to confirm that the problem spots actually improved.

That second run is the important part most people skip.

If NetSpot shows that even in the best possible router location your far rooms stay at terrible signal, the honest answer is: you need another access point or mesh node, not more tuning.

4. Router quality and “hidden” bottlenecks

Where I differ a bit from the others: people underestimate how often the router itself is the villain.

Red flags that point at the router:

  • Everything gets weird when a few people stream or game at once.
  • Web interface becomes slow or unresponsive at the same time.
  • Rebooting the router temporarily fixes everything for hours.

If this sounds like your place:

  • Try turning off any heavy extras temporarily:
    • Built in VPN server
    • Traffic shaping/QoS rules
    • Built in parental filtering
  • Then retest stability. If things suddenly calm down, the router is underpowered for what you enabled.

Long term, you might be better off with a mid range consumer router or proper mesh rather than living in “reboot once a day” land.

5. Turning your data into a simple conclusion

Using what you already tested plus a short extra check, you can reduce it to one of these:

  1. “My ISP or modem is bad.”

    • Ethernet slow or unstable.
    • WiFi and Ethernet both show high ping to outside but stable ping to router.
    • Action: call ISP with your logs, ask them to check line noise / error counts, not just speed. Try another modem if possible.

  2. “My WiFi setup is bad, but ISP is fine.”

    • Ethernet is consistent and near your paid speed.
    • WiFi has packet loss or big spikes, especially when multiple devices use it.
    • Action: adjust channels and placement first; if that fails, upgrade router or add AP/mesh.

  3. “Only some rooms are hopeless.”

    • Near router is good, far rooms are consistently bad even with better channels.
    • Action: accept that coverage is the issue. Extra AP or mesh is the right fix, not more arguing with ISP.

  4. “Only one or two devices are cursed.”

    • Other devices in the same spot are fine.
    • Problem devices are also bad on other networks.
    • Action: update drivers/OS, forget and rejoin WiFi, or use Ethernet/USB adapter if the radio is just weak.

@stellacadente and @chasseurdetoiles gave you a solid testing toolkit. If you use those tests, then interpret them with the decision paths above and validate your layout with a quick NetSpot survey, you can usually pin the blame on one of three things in a day or two: ISP, router, or coverage. Then you spend money or energy only where it actually fixes something.