Can someone help me run a wifi health check on my home network?

Wifi
1

My home wifi has been randomly slowing down and dropping devices, even after rebooting the router and modem. I’m not sure if it’s interference, bad hardware, or a provider issue. What steps or tools should I use to do a proper wifi health check, diagnose the problem, and figure out whether I need to change settings, upgrade equipment, or call my ISP?

2

First thing, treat this like a checklist. You want to figure out if the problem is WiFi signal, router load, or ISP.

  1. Basic sanity tests
    • Plug a laptop directly into the modem with Ethernet.
    • Run speed tests at different times of day, use fast.com and speedtest.net.
    • If wired is stable but WiFi is bad, focus on WiFi. If wired is bad, call your ISP with screenshots.

  2. Check your router and firmware
    • Log into the router web UI, usually 192.168.0.1 or 192.168.1.1.
    • Update firmware. Old firmware often causes drops.
    • Make sure you use WPA2 or WPA3, not WEP or “open”.
    • Turn off WPS.
    • Reboot once, then avoid constant power cycling, that hides symptoms.

  3. WiFi channel and band fixes
    • Use 5 GHz for anything important if the router supports it. Less interference, shorter range.
    • Use 2.4 GHz for long range or smart home stuff.
    • Change 2.4 GHz to channel 1, 6, or 11 only. Test all three.
    • Use 20 MHz channel width on 2.4 GHz, not 40 MHz.
    • On 5 GHz, try 40 or 80 MHz, auto channel is usually fine.

  4. Use a WiFi analyzer
    Install a WiFi scanner on your laptop or phone. This helps a lot with “health check” type work.
    For more serious work on a laptop, use NetSpot. It gives you signal strength per room, channel overlap, noise, and lets you do a heatmap.
    Example workflow with NetSpot:
    • Walk around your home with your laptop.
    • Mark rooms on the map.
    • Check where signal drops under about −70 dBm. Those are weak zones.
    • Look for high overlap on your channel with neighbors. If you see that, change channels.
    Link for it here if you want more detail:
    analyzing and improving your WiFi coverage

  5. Placement and interference
    • Put the router high, in the open, near the center of the area you use most.
    • Avoid closets, metal racks, next to big TVs, or next to the microwave.
    • Move cordless phone bases and baby monitors away from the router.
    • If you have thick walls, expect big drops. That is normal physics, not your ISP.

  6. Load and device issues
    • Check how many devices use WiFi. Old routers choke with many phones, TVs, cameras.
    • In the router UI, see if CPU or RAM looks pegged, some routers show that.
    • Disable any “QoS” or “traffic shaping” features as a test. Bad QoS configs often wreck speeds.
    • Test with one device at a time. Turn WiFi off on others for 10 minutes and see if it stabilizes.

  7. Latency and packet loss test
    On a PC, open Command Prompt and run:
    • ping 8.8.8.8 -n 50
    • If you see packet loss or big spikes while on WiFi but not on Ethernet, that points to WiFi.
    Also run:
    • ping your.router.ip -n 50
    If that already drops, the issue is local WiFi or router, not ISP.

  8. Separate SSIDs and features
    • Give 2.4 GHz and 5 GHz different names like “Home_2G” and “Home_5G”.
    • Turn off “smart connect” or band steering as a test. Many routers switch devices at bad times and cause drops.
    • Turn off guest network if you do not use it.

  9. When to suspect hardware
    Signs the router is dying:
    • Needs reboots every day.
    • WiFi disappears randomly for all devices.
    • Wired is fine but WiFi dies, even next to the router.
    Try a different router if you can borrow one for a day. That is the fastest A/B test.

  10. When to call ISP
    Call them with:
    • Screenshots of wired speed tests.
    • Logs of packet loss or outages.
    • Exact times when it drops.
    Ask them to check signal levels on their side and look for errors on your line.

If you run through this list and collect data from NetSpot, pings, and wired tests, you will know if you are dealing with interference, bad placement, overloaded router, or ISP issues. Once you have that, fixing it turns into a pretty simple next step like new router, mesh system, or yelling at your provider.

3 Likes
3

If your home WiFi keeps slowing down and randomly dropping devices, even after you restart the router and modem, you’re probably dealing with one of three culprits: wireless interference, failing hardware, or your internet provider. To run a proper WiFi health check, you’ll want to test your connection quality room by room, identify any dead zones, and see where signal strength or congestion is causing problems. A dedicated WiFi analysis tool like NetSpot can really help here, especially for visualizing coverage and spotting interference from neighboring networks. For a deeper dive into scanning your network, mapping signal strength, and fine-tuning your setup, check out this guide to analyzing and improving your WiFi coverage.

@sternenwanderer already hit most of the “classic” debugging steps, so I’ll try not to repeat all of that. A few extra angles to run a real “health check”:

  1. Look for patterns in the drops

    • Note times of day when things die: evening only often means congestion or router overload.
    • See if it is specific to certain devices (only phones, only smart TV, only 2.4 GHz stuff). That screams compatibility or band‑specific issues rather than ISP.

  2. Test with a completely different WiFi environment

    • Create a temporary hotspot on your phone and connect a couple of your “problem” devices to it for an hour.
    • If they behave fine on the hotspot but flaky on your home WiFi, your ISP is probably not the main issue. It’s either router config, interference, or dying hardware.

  3. Check for “smart” router features that actually suck
    I slightly disagree with the idea that “auto” is usually fine for everything. Auto channel and auto band steering are frequent culprits.

    • Turn off band steering / “Smart Connect” for a full day. Let devices stay locked on either 2.4 or 5 instead of bouncing around.
    • Disable “Airtime Fairness,” “WMM power save,” or weird vendor features if those exist. Some chipsets + some phones = random drops.
    • If you have any parental control / filtering stuff, disable it temporarily. Those services can spike CPU usage on cheaper routers.

  4. Run a structured WiFi survey
    This is where NetSpot shines and why people keep bringin it up.

    • Install NetSpot on a laptop.
    • Walk around your home, pausing in each room so it can measure signal strength, noise, and neighboring networks.
    • Pay attention to:
      • Signal less than about −67 dBm in “important” rooms is where video calls and streaming start to suffer.
      • If your network overlaps heavily with neighbors on the same channel, change your channel and retest.
      This turns your “I think it’s bad in the bedroom?” into actual numbers.

  5. Check for power or thermal issues

    • Feel the router. If it’s hot to the touch, that can cause instability. Try standing it vertically so it vents better, or move it away from other warm electronics.
    • Try a different power outlet and, if possible, a different power brick with the same specs. Failing adapters cause weird intermittent failures that look like WiFi problems.

  6. Try a “known good” alternate access point

    • If you have an old router lying around, set it up as a temporary AP with a different SSID and connect only a couple devices to it.
    • Put it near your main router and plug it into the same modem or backhaul.
    • If the old router is stable while the current one still flakes, your main router is probably toast.
      This A/B test is more decisive than just guessing “maybe the router is dying”.

  7. Check for firmware quirks with specific devices

    • Notice if certain brands (e.g. some smart plugs or cameras) drop first.
    • Look up your router model + “disconnects” online. Some models have notorious firmware bugs that only show up with lots of IoT devices.
    • If there’s a beta or alternative firmware that fixes stability (sometimes noted in release notes), that’s a strong clue.

  8. Continuous monitoring instead of one‑off tests
    If you are a bit more techy and want a real “health report”:

    • Set a laptop or Raspberry Pi to continuously ping:
      • Your router
      • Your ISP gateway or 8.8.8.8
    • Log that to a file and look for when latency spikes or packets are lost.
    • Compare the times with when you noticed your WiFi “feels bad.”
      If local pings to the router are already awful while WAN pings are fine when on Ethernet, you’ve nailed it: local WiFi / router issue, not ISP.

  9. Mesh vs single router decision
    After your health check, if you find big weak areas:

    • Instead of cranking transmit power to max (which can actually worsen performance), consider a proper mesh system or a wired access point.
    • Too much power on 2.4 GHz can make far devices “hear” the router but not transmit back properly, leading to drops and retries.

  10. When to push the ISP harder
    Slight difference from @sternenwanderer: don’t just send them speed test screenshots. Also:

  • Ask them specifically to check signal levels (SNR, power levels) on your line and error counts.
  • If you have a DOCSIS modem, log into it and check for lots of “uncorrectable codewords” or T3/T4 errors in the logs. That’s evidence you can quote.
  • Mention that wired is OK but your modem logs show errors, or that wired is also bad and you’ve tested multiple times of day.

If you want to treat this like a “WiFi health audit,” I’d do:

  1. quick phone hotspot test to rule out devices,
  2. wired vs WiFi comparison,
  3. full NetSpot scan of your place,
  4. log pings for 24 hours,
  5. temporary second router or AP test.

By the time you’ve done those, you won’t be guessing “interference vs hardware vs ISP” anymore, you’ll have a pretty clear villain to blame.