I’ve already rebooted the router, checked for unknown connected devices, and moved my laptop closer to rule out a weak signal. The router sits on a hallway shelf, and my laptop is usually on the kitchen table. During the day, ordinary browsing and streaming seem normal, but at night pages load slowly and video buffers on both my laptop and phone.
I’ve read that the likely causes could include local Wi-Fi interference, household bandwidth use, or congestion outside the home. Which method do people actually use to narrow this down: scheduled speed tests, router traffic logs, or a Wi-Fi analyzer, and why?
You probably won’t get a clean answer from a single night of testing. The quickest approach is to collect the same measurements during a normal daytime period and again when the slowdown starts.
Run an internet speed test from the same laptop and location each time. If possible, repeat it with the laptop connected to the router by Ethernet. Slow Wi-Fi with a normal wired result points toward interference or the router’s wireless side. If both wired and wireless speeds collapse at night, household usage or ISP congestion becomes much more likely.
Router traffic logs are the next useful check, especially if the router shows bandwidth by device rather than merely listing connected devices. Look for TVs, game consoles, cloud backups, security cameras, phone updates, or large downloads around the problem hours. Some consumer routers keep very poor history, so the absence of anything in the log does not necessarily prove nobody was using bandwidth.
A Wi-Fi analyzer is most useful after you have evidence that the wired connection remains healthy. Check whether neighboring networks crowd your channel at night and whether your laptop is using 2.4 GHz or 5 GHz. The kitchen location matters too. Microwave use can interfere with 2.4 GHz, and nearby Bluetooth devices can add noise, but that usually causes shorter bursts rather than an entire evening of consistently poor service.
So I’d use scheduled speed tests first, including one wired comparison, then traffic logs, then the analyzer. That order separates “internet connection problem” from “Wi-Fi problem” before you spend time adjusting channels that may have nothing to do with it.
If it starts at nearly the same time every night, check the router for scheduled guest networks, parental controls, automatic backups, firmware updates, or “smart” channel optimization. Those can run without showing an unknown device, and some routers briefly wreck performance while rescanning channels. Temporarily disable scheduled features for an evening before changing hardware or Wi-Fi channels.
Don’t blame the router until another device fails the same way.
When the slowdown starts, put a phone beside the laptop and try the same few tasks on both. Use regular websites, a video, and a larger download rather than relying on a single speed number. Then switch the phone to cellular data and connect the laptop to the phone’s hotspot for a few minutes.
That comparison narrows things down quickly:
Both devices are slow on home Wi-Fi, but normal elsewhere: look at the router, household traffic, or ISP.
The phone is fine on home Wi-Fi while the laptop struggles: the laptop is the likely problem.
The laptop works normally through the phone hotspot: its general performance is fine, but its connection to your router is not.
Websites hesitate while streaming and downloads remain normal: DNS or browser behavior may be making the connection feel slower than it is.
A laptop-specific problem can still appear only at night. Battery-saving mode, scheduled antivirus scans, cloud syncing, operating system updates, or an old Wi-Fi driver can all create symptoms that look like bad internet. Check Task Manager while it is happening and compare CPU, disk, and network activity with daytime. A machine with its disk stuck near full activity can make every page feel painfully slow even when the network is behaving.
I agree that a wired comparison is useful, but many people cannot conveniently run Ethernet to a kitchen table. The phone and hotspot comparison is less exact, yet it takes five minutes and may stop you from wasting an evening changing router channels for a problem that exists only on the laptop.
A connection with low download speed is different from one with decent bandwidth but terrible latency. Both feel like “slow Wi-Fi,” especially when pages stall, video calls break up, and apps take forever to respond.
While the problem is happening, open two command windows and run continuous pings. Ping your router’s local address in one window, usually something like 192.168.1.1, and a public IP address such as 1.1.1.1 in the other. On Windows, use ping -t address. Let both run for several minutes while you use the connection normally.
If the router ping becomes erratic or drops packets, the trouble is inside the home: wireless interference, a struggling router, or possibly the laptop’s adapter. If the router ping stays steady while the public ping shoots up, the Wi-Fi link itself is probably fine and the delay is farther upstream. That makes evening ISP congestion or someone saturating the connection more likely. A public server can occasionally ignore ping traffic, so look for a sustained pattern rather than a single timeout.
Upload saturation is easy to miss. A phone photo backup, security camera, file sync, or game console update may use relatively little download bandwidth yet fill the upload side completely. Once that happens, acknowledgments and ordinary requests get stuck in line, making downloads and websites feel broken. Basic connected-device lists often will not make this obvious.
@binaryfox_56’s wired comparison is still the cleaner test, but the two-ping check is useful when running a cable to the kitchen is impractical. If upload saturation turns out to be the trigger, look for SQM, adaptive QoS, or bandwidth-control settings in the router. Set the limits slightly below the speeds the connection can actually sustain. I would test that before buying a new router or randomly changing channels.
Temporarily give the 2.4 GHz and 5 GHz bands different network names, then connect the laptop only to 5 GHz during the problem hours. “Smart connect” or band steering can quietly move a device onto crowded 2.4 GHz even when the signal looks strong. Moving closer does not rule that out.
While it is slow, run netsh wlan show interfaces on the laptop. Check the channel, radio type, signal, and transmit/receive link rates. If the link rate suddenly drops while your router and public pings remain reasonable, the wireless connection is renegotiating badly rather than the ISP simply running out of capacity.
@binaryfox_56 is right that band choice matters, but Wi-Fi analyzer screenshots can be misleading when the laptop keeps switching bands. Force each band separately before changing channels. Do this as a temporary diagnostic, since separate names can make roaming less convenient.
Given the kitchen location, test 5 GHz both with and without the microwave, nearby Bluetooth gear, and any cheap LED lighting in use. Those usually cause bursts, but repeated evening appliance use can make the timing look like ISP congestion.
Careful with reading the nighttime speed number too literally. Popular test servers get hammered in the evening too, so a low result doesn’t automatically mean your line is congested, it can just mean the server you hit is busy. If you’re going to lean on Speedtest by Ookla for the before/after comparison @binaryfox_56 suggested, lock it to the same server every run instead of letting it auto-pick, otherwise you’re comparing two different things. The other bit everyone’s skating past is that ‘slow at night’ often lines up with the whole street coming home and loading the same shared node upstream, which no amount of channel changing or driver updates will fix. The two-ping test @real_owl described is the fastest way to spot that, so I’d run that before touching anything on the router.
The ping test everyone’s leaning on has a blind spot: a bare ping runs on almost no data, so it can look perfectly steady while a saturated line is choking every real transfer. If you’re going to run @real_owl’s two-window check, start a big upload or download at the same time and watch the latency then. A router ping that stays flat idle but spikes to hundreds of ms the moment the line gets busy is classic bufferbloat, and that alone can make a healthy connection feel dead at night.
Agree with @shadowpilot3527 that pinning the same server matters, and Speedtest by Ookla is fine for that quick before/after snapshot. Just don’t read one clean number as proof, since the latency-under-load part is what actually correlates with pages hanging. If it turns out to be bufferbloat, the SQM/QoS settings @real_owl mentioned are the fix, not new hardware.
Moving the laptop closer does not rule out interference right beside the laptop. During the slowdown, unplug any USB 3 hub, external drive, dock, or cheap charger, then run the laptop on battery for five minutes. Those devices can interfere with 2.4 GHz at very short range. If nothing changes, reconnect them and continue with the phone comparison and wired test already suggested.