Why Does My WiFi Disconnect When I Use the Microwave?
By Ken Hollow, a man who once had to explain to a fox spirit that the microwave was not, in fact, “attacking the router out…
WiFi & Home Network
My WiFi Is Fast on Speed Tests But Slow on Everything Else
By Ken Hollow, who was shown a speed test result as evidence in an argument he had not agreed to participate in
“Ken. Three hundred megabits.”
“Okay.”
“THREE HUNDRED. And the page won’t load.”
“Those two things are less related than you’d think.”
“Then what am I paying for?”
“Bandwidth. You’re complaining about latency.”
The Short Answer
A speed test measures how much data you can move in bulk. Almost nothing you do day to day is limited by that. Browsing, video calls, and gaming are limited by latency — how quickly the first response arrives — and by consistency. A connection can post 300 Mbps and still feel broken if latency is high, DNS is slow, or the connection is unstable under load. The number isn’t lying; it’s measuring the wrong thing for the problem you have.
Bandwidth Versus Latency, Briefly
The useful analogy is a road. Bandwidth is how many lanes it has. Latency is how long it takes a single car to make the trip.
Downloading a large file uses all the lanes at once — that’s bandwidth, and that’s what speed tests measure. Loading a web page is different: your browser makes dozens of small requests, many of which have to wait for earlier ones to finish. What matters there is round-trip time, repeated dozens of times.
Which is why a 300 Mbps connection with poor latency feels worse than a 50 Mbps connection with good latency, for the things people actually do most.
Most speed tests do report latency, usually as “ping” or “latency” in milliseconds, in smaller text next to the big number nobody looks at. Look at it. Under about 30 ms is good, 30–70 ms is fine, and consistently over 100 ms is where things start to feel sluggish regardless of your bandwidth.
Cause One: Bufferbloat (The Big One)
This is the single most common explanation for “fast test, slow feel,” and almost nobody has heard of it.
Bufferbloat happens when your router holds too much data in memory during heavy traffic. A large download fills the buffer, and every other request — your click, your video call audio, your game — has to queue behind it. Latency that was 20 ms at idle balloons to several hundred milliseconds under load.
The tell: your internet feels fine when nothing else is happening, and becomes unusable the moment someone starts a download or a backup runs. A normal speed test won’t reveal it, because it measures peak throughput rather than latency under load.
How to test it: use a speed test that specifically measures latency under load — Waveform’s bufferbloat test and Cloudflare’s speed test both do this, and both report a grade. If you get a poor rating, you’ve found your answer.
How to fix it: enable Smart Queue Management (also called SQM, or sometimes just QoS) in your router settings if it has it. This is the specific feature that fixes bufferbloat, and it’s one of the better reasons to own a capable router rather than a basic ISP unit.
Cause Two: DNS Lag
Before your browser can load anything, it has to translate the site name into an address. If that lookup is slow, every new site you visit stalls before a single byte of the page arrives.
The symptom is distinctive: pages take a noticeable moment to start loading, then load quickly once they begin. Sites you visit often feel faster than new ones, because the lookup is cached.
The fix is switching to a fast public DNS provider — Cloudflare’s 1.1.1.1 or Google’s 8.8.8.8 — rather than using whatever your ISP assigned. Set it on your router so every device benefits, or on individual devices. It’s a five-minute change and it’s the one on this list most likely to produce an immediate, noticeable improvement.
Nana’s Take:
“So the page is slow before it’s even started being a page.” — Yes. It’s waiting for directions. “The internet has to ask where things are, every time?” Roughly, yes. “That seems like something you’d only need to do once.” Which is why it caches. “Then why is it still slow, Ken.” Different cause. Keep reading.
Cause Three: Wireless Instability, Not Wireless Speed
Speed tests run for a few seconds and report the best sustained throughput they saw. A connection that briefly peaks high and then drops packets constantly can score well and behave terribly.
Packet loss is the specific villain. Lost packets get retransmitted, which causes stalls, video call artefacts, and the sensation of things freezing momentarily. A connection with 2% packet loss can post an excellent speed test and be genuinely unpleasant to use.
How to check: on Windows or Mac, open a terminal and run a continuous ping to a reliable address (ping -t 1.1.1.1 on Windows, ping 1.1.1.1 on Mac) and let it run for a minute while you use the connection normally. Watch for timeouts, dropped replies, or times that swing wildly. Steady numbers are healthy. Erratic ones explain everything.
The usual causes are interference and marginal signal — covered in why your WiFi is slow. A quick diagnostic: run the same test on an ethernet cable. If wired is rock steady and wireless is erratic, it’s your WiFi rather than your connection.
Cause Four: It Isn’t Your Internet At All
Sometimes the connection is fine and something else is slow. Worth ruling out before buying hardware.
The device is the bottleneck. An old laptop with too little memory, a nearly full drive, or too many browser tabs will feel slow on any connection. If one device is slow and others on the same network are fine, it’s the device.
The browser is clogged. Extensions, a bloated profile, or an enormous cache can add noticeable delay. Worth testing in a private window with extensions disabled, and see our guide on what clearing your cache does.
The website is slow. Genuinely common and entirely outside your control. If one site crawls while others are instant, it’s them.
A VPN is adding a detour. Routing through a distant server adds latency by design. Try disabling it briefly to compare.
The Diagnostic Order
Fastest path to the actual cause:
1. Look at the latency number on your speed test, not the bandwidth. Over 100 ms at idle is a problem in itself.
2. Run a bufferbloat test. If it grades poorly, enable SQM on your router. This is the most likely single answer.
3. Switch DNS to 1.1.1.1. Five minutes, frequently noticeable.
4. Run a continuous ping for a minute. Erratic times or timeouts mean instability, not slowness.
5. Test the same thing on ethernet. Separates WiFi problems from connection problems.
6. Test a second device. If only one is slow, stop troubleshooting the network.
If the specific symptom is video stalling rather than general sluggishness, streaming buffering has its own causes worth reading separately.
Nana’s Take:
“It was the buffer thing.” — Bufferbloat. “It was the buffer thing, and the fix was a setting that was already in the router, switched off.” Yes. “I bought nothing and it’s fixed and I feel strangely cheated.” That’s the most common outcome in this entire field.
TL;DR
Speed tests measure bulk throughput, which is not what browsing, calls, or gaming depend on — those depend on latency and consistency. Look at the latency figure rather than the big number. The most likely culprit is bufferbloat: your router queues too much data under load, so latency spikes whenever anything downloads. Test it with a bufferbloat-specific test and fix it by enabling Smart Queue Management or QoS on your router. Next most likely is slow DNS, fixed by switching to 1.1.1.1 or 8.8.8.8. Then check for packet loss with a continuous ping, and compare against an ethernet cable to separate WiFi problems from connection problems. If only one device is slow, the problem is that device, not your internet.
Hi. I’m Ken. I run Two Second Solutions, a one-man agency that somehow landed a fox spirit influencer as a client. I drink too much coffee, blog when I need to vent, and regularly update my résumé just in case she sets the office on fire again. I’m not crying — it’s just spell residue.
