Why is my wifi speed suddenly so slow at home

My home wifi speed dropped a lot even though I didn’t change my router, plan, or devices. Streaming buffers, downloads crawl, and speed tests show way lower Mbps than what I pay for. I’ve tried rebooting the router and modem, moving closer, and turning off other devices, but nothing helps. What else can I check to figure out if this is an interference issue, an ISP problem, or a router/settings issue, and how can I fix it quickly

Slow Wi‑Fi out of nowhere usually comes from one of a few things changing around you, even if you did not touch your plan or router. I would go through this checklist step by step.

  1. Check if the issue is Wi‑Fi or the ISP
  • Plug a laptop directly into the modem with Ethernet.
  • Run a speedtest on speedtest.net or fast.com.
  • If wired speeds look normal, your ISP is fine and the problem sits in your Wi‑Fi side.
  • If wired is also slow, contact your ISP and ask if there is congestion, line noise, or a profile limit on your line. Get them to read you your provisioned speed.
  1. Scan for signal strength and interference
  • Wi‑Fi slows down hard when signal is weak or noisy.
  • On your phone or laptop, check Wi‑Fi signal in bars in the rooms where you use it most.
  • If it dropped from full to 1–2 bars since before, something is blocking or interfering. New mirror, metal shelf, fish tank, thick door, neighbor router, etc.
  • Use a Wi‑Fi analyzer to see channel use and signal in dBm. A value around −50 to −65 dBm is ok. Worse than −75 dBm starts to crawl.

For a more detailed picture, try a heatmap tool like Wi‑Fi site survey with NetSpot.
It lets you walk around your home, see dead zones, see overlapping networks, and pick cleaner channels.

  1. Change Wi‑Fi band and channel
  • In your router admin page, check both 2.4 GHz and 5 GHz.
  • 2.4 GHz reaches farther but is slower and crowded. 5 GHz is faster but weaker through walls.
  • On 2.4 GHz, try channels 1, 6, or 11. Pick the one with the fewest neighbors from your analyzer.
  • On 5 GHz, set channel to Auto or pick a less used one from the analyzer results.
  • Turn off “20/40 MHz coexistence” bloat modes if you see them causing issues. Stick to 20 MHz on 2.4 GHz.
  1. Check number of devices and background traffic
  • Log into the router and look at “connected devices”.
  • If you see a lot more devices than you expect, someone might be on your Wi‑Fi.
  • Change your Wi‑Fi password to a long, unique one. WPA2 or WPA3 only. No WEP or open networks.
  • On your own devices, stop big downloads, cloud backups, game updates, or torrents.
  • QoS or “Smart Queue Management” helps. If your router has SQM or QoS, enable it and set your upload and download slightly under your actual max. This keeps one device from hogging everything.
  1. Check for thermal or age issues in the router
  • If the router feels hot to the touch, move it to an open area. Not inside a cabinet, not on carpet, not stacked on other electronics.
  • Dust clogged vents cause throttling and random slowdowns.
  • Update firmware in the router admin page. Old firmware often has Wi‑Fi bugs.
  • If the router is 4–5+ years old and only supports Wi‑Fi 4 (802.11n), it might just be struggling with newer devices and local congestion.
  1. Placement and obstacles
  • Position the router in a central spot, raised, and away from large metal objects, microwaves, cordless phone bases, baby monitors.
  • For multi‑story homes, keep it closer to the center of the house, not in a basement corner.
  • If your home is large or has thick walls, you likely need a mesh system or extra access point instead of one single router.
  1. DNS and device level checks
  • Sometimes web browsing feels slow even when speedtests look ok.
  • Try changing DNS on your router or device to 1.1.1.1 or 8.8.8.8.
  • Test with another device. If one device is slow and others are fine, scan that device for malware, uninstall VPNs, and reset network settings.
  1. Test at different times
  • Run speedtests morning, afternoon, late evening.
  • If speeds drop heavy only in peak hours, your ISP might be congested or shaping traffic.
  • Collect 4 or 5 test screenshots, both wired and Wi‑Fi, and use those when talking to ISP support so they take it more seriously.

If you want a more data driven view than “it feels slow”, a tool like NetSpot helps a lot.
You walk the house, it maps signal, noise, and channel overlap. Then you can say “channel 6 is a mess, I will switch to 1” instead of guessing.

Run through those steps in order. It narrows the cause fast and usually fixes the drop without needing a new plan.

1 Like

This happens to me about twice a year and it drives me nuts, so I’ll throw a few less‑obvious things at you that @waldgeist didn’t cover in detail.

First, one thing to push back on: people always say “if Ethernet is fine, it’s just Wi‑Fi.” That’s usually true, but I’ve had cases where the modem line is borderline, so any extra noise or load makes Wi‑Fi look way worse than Ethernet. So still worth asking your ISP to check the signal levels and error counts on their end, even if your wired test looks “ok-ish.”

Stuff that often changes without you changing your gear:

  1. Neighbor upgrades & hidden interference

    • New neighbor got a giant mesh system or “gaming router” and it’s blasting on wide 80 MHz channels right on top of yours.
    • Cheap smart bulbs, baby monitors, cordless phones, Bluetooth speakers and even some microwaves spamming the 2.4 GHz band.
    • Try temporarily turning off smart plugs, bulbs, cameras etc. for 10–15 minutes and see if your Wi‑Fi magically speeds up. It’s annoying, but it’s caught a few “mystery slowdowns” for me.
  2. Automatic router “smart” features going dumb
    Some routers silently flip settings after firmware auto‑updates:

    • “Smart connect” forcing everything to 2.4 GHz even when 5 GHz is way better.
    • Channel width changed to 40 MHz on 2.4 GHz, creating more interference and actually reducing stability.
    • Band steering bugs that keep shoving you between bands mid‑stream.
      Try:
    • Turn off “smart connect” / band steering and give 2.4 and 5 GHz different SSIDs (like MyWifi-2G and MyWifi-5G).
    • Manually connect your streaming devices and laptop to the 5 GHz network only.
    • Lock 2.4 GHz to 20 MHz width.
  3. Hidden “max speed” killers on your devices
    Router might be fine, but your devices are sabotaging you:

    • Old VPN client or antivirus firewall intercepting traffic.
    • “Power saving” Wi‑Fi mode in Windows or on laptops that cuts throughput.
    • Random vendor Wi‑Fi utilities (Killer, Intel “advanced” stuff) misconfigured.
      Quick test:
    • Boot one device in Safe Mode with networking and run a speed test.
    • Try a speed test in a private browser window with all extensions off.
      If it jumps back to normal, the problem is software, not the router.
  4. Channel + placement, but do it with data, not guessing
    Instead of just “try a different channel,” actually map what’s going on. This is where NetSpot is genuinely useful.

    • Install it on a laptop.
    • Do a quick survey walk of your home.
    • You’ll see which rooms are now weak, which channels are overloaded, and if a neighbor AP popped up on your channel.
      Having a visual map of signal and noise makes changing channels a lot less random.
      The walkthrough tools on exploring your home Wi-Fi coverage help you see dead zones and overlapping networks clearly.
  5. ISP “silent nerfs”
    They say nothing changed, but:

    • They moved you to a different CMTS / segment.
    • They started traffic shaping or “optimizing” video.
    • Your modem got reprovisioned to a lower profile during a line issue.
      You already rebooted the router; also try:
    • Power cycle the modem for 10–15 minutes off.
    • Ask ISP support to read out your provisioned speed profile and check error rates and signal levels.
    • Run multiple speed tests from different servers and at different times and take screenshots; use that as ammo when calling.
  6. Your router might be “fine” but actually overloaded
    Even if it’s not ancient, a lot of cheaper routers fall over once you have:

    • Several streaming services running.
    • Cloud backup or game updates.
    • Smart home junk constantly polling.
      Signs:
    • Web UI is slow or hangs.
    • Pings inside your LAN spike like crazy when you do a download.
      Try:
    • Continuous ping from one device to the router IP while you start a speed test. If ping jumps from 1–3 ms to 100+ ms, the router CPU is choking.
    • Temporarily disable QoS or weird “game acceleration” features to see if performance improves or gets more stable.

If you want a clean, actionable next step:

  1. Run a wired speed test at least 3 different times of day.
  2. While Wi‑Fi feels slow, ping your router and your modem’s IP, see where the latency explodes.
  3. Use NetSpot to map your apartment/house and check if your usual spot suddenly has weak or noisy signal.
  4. Split 2.4 / 5 GHz into two SSIDs and force your main devices onto 5 GHz.

That combo usually exposes whether this is:

  • ISP congestion,
  • local RF interference,
  • router firmware / CPU issues, or
  • some misbehaving device or software on your network.

Last note: if your router is older and only does Wi‑Fi 4 and you now have a bunch of newer phones, TVs, consoles etc., sometimes the “sudden” slowdown is actually it hitting the practical limit of how much it can juggle. In that case no amount of channel tweaking fixes the underlying problem, it just delays the inevitable upgrade.

Couple of angles that @viaggiatoresolare and @waldgeist did not lean on heavily:

1. Check latency and packet loss, not just Mbps

Your “speed” can look fine on paper while gaming/streaming feels awful.

  • Open a terminal / cmd and run a continuous ping to your router (usually 192.168.0.1 or 192.168.1.1).
  • In another window, ping something public like 8.8.8.8.
  • Start a download or a speed test and watch:
    • If ping to the router jumps from 1–3 ms to 100+ ms or shows timeouts, the router or Wi Fi segment is choking.
    • If router ping is stable but 8.8.8.8 explodes, problem is upstream (modem / ISP / line).

This fills a gap: they focused mostly on throughput; latency + loss is often what “suddenly slow” actually feels like.

2. Look at “bufferbloat” specifically

Even with the right Mbps, uploads can saturate the line and ruin everything.

  • Use a bufferbloat test (search “DSLReports bufferbloat test” or similar).
  • If your grade is terrible, any small upload (cloud backup, camera, phone photos syncing) will make Netflix buffer.

If that is the case, QoS / SQM on your router is not optional. Here I slightly disagree with treating QoS as just a “nice to have”; in congested lines it is the main fix.

3. Check for half duplex or bad Ethernet links

If your modem and router are linked with a short Ethernet cable that went bad or is kinked:

  • Log into the router and check WAN port status.
  • If it shows 10 Mbps or 100 Mbps half duplex instead of 1000 full, that is an instant bottleneck.
  • Swap the cable with a known good Cat5e/6 and recheck.

This is a classic “nothing changed” problem that is actually a physical layer issue.

4. Wi Fi drivers & OS bugs

The others talked about device software in general, but be very literal:

  • On Windows, update your Wi Fi driver directly from Intel/Qualcomm, not only via Windows Update.
  • On macOS / iOS / Android, check if the slowdown started right after a major update. Sometimes specific versions hate certain AP chipsets.

Test: if one old laptop is fast and your newer one is slow on the same spot and SSID, suspect driver/OS rather than the router.

5. NetSpot and similar tools in a more critical light

NetSpot is great to visualize what your network is doing instead of guessing, but it is not magic.

Pros of NetSpot:

  • Clear heatmaps so you see where signal really drops.
  • Shows which channels neighbors occupy, so you stop random channel hopping.
  • Good for spotting that your usual couch spot is now in a noisy RF pocket.

Cons of NetSpot:

  • It diagnoses coverage and interference, not ISP problems or bad cabling.
  • Can encourage over-tweaking: people obsess over tiny dBm shifts that do not matter in real life.
  • Requires a laptop walkaround; not everyone wants to survey their place for a simple fix.

Used together with the ping tests above, NetSpot actually becomes much more useful because you can correlate “red area on map” with “ping spikes here.”

If you want alternatives to NetSpot, basic Wi Fi analyzers on phones show similar channel info, but they usually lack the survey / heatmap view. That is where NetSpot still wins.

6. Background “chatty” devices & IoT storms

I agree with the others that device count matters, but there is a twist: even low bandwidth devices can cause trouble if they misbehave.

  • Smart cameras stuck in a reconnect loop.
  • A NAS doing ARP spam or broadcast storms.
  • Powerline adapters generating a lot of noisy traffic.

Quick approach:

  • Temporarily unplug non-essential gear: NAS, cameras, smart hubs, powerline links.
  • Re-test with only your router, modem and one client.
  • Add devices back in batches and note when performance tanks.

This method catches things that simple “how many devices are connected” views in the router do not expose.

7. CPU / memory starvation on the router

Rather than just touching the router and guessing from temperature:

  • Log into the router and look for CPU / memory stats, or system logs that mention overload, restarts or watchdog timeouts.
  • If your router has extra services (VPN server, ad blocking, traffic logging, parental control with heavy inspection), try turning those off.
  • Retest Wi Fi speed after disabling extras.

I am slightly more aggressive here than @viaggiatoresolare: fancy “security” and “optimization” add-ons on consumer routers often hurt more than they help.

8. When to actually replace the router

Not every slowdown needs new hardware, but there are clear “stop wasting time” signals:

  • Router reboots on its own under heavy load.
  • Web interface is painfully slow even when traffic is idle.
  • Only supports 2.4 GHz or very limited 5 GHz channels.
  • Clients randomly drop and reconnect even with strong signal.

If multiple of those are true and your wired modem tests are solid, an upgrade will usually do more than endless tweaking.

Putting it all together, a practical order that complements what’s already been said:

  1. Continuous ping to router and to internet host while you do a speed test.
  2. Check WAN link speed/duplex and swap the modem router cable.
  3. Run a bufferbloat test and, if bad, set up SQM/QoS correctly.
  4. Use NetSpot or a similar survey to confirm if your main area is now noisy or weak.
  5. Update Wi Fi drivers on at least one test device, try again.
  6. Strip the network to modem + router + one client, then add devices back to find any “noisy” culprit.

If you walk through that, you will know whether you are dealing with RF interference, local hardware/software issues, or a line/ISP limitation, instead of just seeing “slow” and guessing.