How to Troubleshoot a Slow Internet Connection at Home Fast

Your 1 Gbps fibre line is crawling. Netflix buffers. Your video call freezes mid-sentence. So you reboot the router, wait thirty seconds, and… nothing changes. Sound familiar?

Here's the uncomfortable truth: in most homes, the problem isn't the connection you're paying for. It's what happens to that connection between the wall and the device in your hand. I've been called to fix this exact complaint dozens of times over the past few years, and I can count on one hand the number of times the ISP was genuinely at fault. The rest of the time, it was WiFi placement, a saturated channel, or a device quietly downloading updates in the background.

This guide walks you through how to troubleshoot a slow internet connection at home the way I actually do it: measure first, isolate the bottleneck, then fix only what's broken. No guessing. No buying a new router before you know why the old one is struggling.

Start with a real measurement, not a feeling

"It's slow" is not data. Before touching a single cable, you need a number.

Run a speed test on a wired connection if you possibly can. Plug a laptop directly into the router with an Ethernet cable, disable WiFi on that machine, and test. Then disconnect the cable, reconnect over WiFi, stand in the same spot, and test again. Write both numbers down.

Why does this matter? Because it splits your problem in two. If the wired test gives you 480 Mbps on a 500 Mbps plan, your line is fine and everything downstream is a WiFi or device issue. If the wired test also collapses to 40 Mbps, then yes—call your provider.

What counts as normal?

Expect to lose some speed. No connection delivers exactly what the contract states. Most fibre plans land somewhere between 80% and 95% of the advertised figure on a wired test, depending on time of day and how many neighbours share the same local loop.

But there's a hard rule I apply: if the wired result is under 70% of your plan, something is wrong upstream. That's worth a call. Between 70% and 95%? You're within normal range, and the real culprit is almost certainly your home setup.

One caveat about testing tools. Browser-based tests are fine for a rough reading, but they're affected by whatever else your computer is doing. Close your browser tabs, pause cloud sync, and test twice—once in the morning, once in the evening. Evening results are usually the honest ones.

Why is my internet so slow but I have good internet?

This is the question I hear most, and the answer usually surprises people: you have good internet, and you're still slow, because "internet" and "WiFi" are two different things.

Your provider delivers a signal to the router. That's their job, and it ends at the router's WAN port. Everything after that—the radio, the channel, the walls, the number of devices—is your side of the fence.

The WiFi tax nobody tells you about

A wired connection is a straight pipe. WiFi is a conversation in a crowded room. The router and your laptop must agree on a channel, avoid interference, and re-transmit any packet that arrives corrupted. Every one of those steps costs time.

In practice, I regularly see WiFi deliver 40% to 60% less throughput than a cable in the same room. Move one floor up and it gets worse. Put a concrete wall in between and you can lose it entirely.

So when you ask why your connection feels slow despite a solid plan, the honest answer is often: your device is talking to the router over a weak, congested radio link, and no amount of extra bandwidth from your provider fixes that.

How do I figure out what is slowing down my internet?

Work by elimination. Change one variable at a time, and stop as soon as the number jumps.

1. Test wired. If wired is fast and WiFi is slow, the problem lives in the radio layer—skip to the WiFi section.
2. Test a second device. Fast on your laptop, slow on your phone? The network is fine and the phone is the issue.
3. Test at 7 a.m. If mornings are fast and evenings are terrible, you're sharing a saturated local loop with your neighbourhood.
4. Disconnect everything else. Turn off every other device for five minutes and test again. This catches background traffic you didn't know existed.

That fourth step is where the surprises live.

The invisible bandwidth thieves

Last winter, a client called me convinced their provider had throttled them. Their evening speeds had dropped from 300 Mbps to under 30. I walked in, opened the router's admin page, and found a tablet in the kids' room that had been stuck on a failed cloud backup for three weeks. It was retrying endlessly, saturating the upstream.

We killed that job and the speed came back within minutes. Cost of the fix: zero.

Common culprits I've found on real home networks:

• Cloud backup tools syncing a large folder for the first time
• Game consoles downloading a 60 GB patch in the background
• A smart TV left on a streaming menu, quietly pulling a 4K preview loop
• Someone in the household streaming 4K on three screens at once (each stream can pull 15 to 25 Mbps on its own)
• An old security camera uploading low-quality video continuously to a cloud account

None of these show up as "slow internet." They show up as everything getting slower at once.

Why is my internet slow even though I have 1000 Mbps?

Two things are happening, and neither is a scam.

First, 1000 Mbps is a theoretical maximum, not a guarantee. It assumes ideal conditions, a wired device with a gigabit network card, and no contention on the shared segment of the network. Real-world gigabit plans typically deliver somewhere in the 700 to 950 Mbps range on a good day.

Second, and more importantly: almost no device in your home can actually use 1000 Mbps. A phone on WiFi 5 tops out well below that. A streaming stick doesn't need more than 25 Mbps for 4K. The bottleneck is rarely the pipe—it's the tap at the end of it.

Here's a comparison that clears this up fast:

Connection type	Realistic throughput	What it's good for
Ethernet (Cat 5e/6)	850–950 Mbps on a gigabit plan	Gaming, large downloads, video calls
WiFi 6, same room, 5 GHz	400–700 Mbps	Everything except latency-critical work
WiFi 5, one floor away	80–200 Mbps	Streaming, browsing
WiFi, two floors away, 2.4 GHz	15–50 Mbps	Barely enough for HD video

Notice the pattern. The plan didn't change. The path did.

Fixing WiFi before you buy anything

Before you spend a cent on new hardware, try these in order. I've fixed more homes with the first three than with any router upgrade.

Move the router—really

The worst place for a router is a cupboard, a metal shelf, or the floor behind the TV. Radio waves don't like metal, water, or concrete. Put it high, central, and out in the open. I've seen this single change double a bedroom's throughput.

Switch to 5 GHz on devices that stay put

2.4 GHz has better range, but it's crowded—every neighbour's router, every microwave, every baby monitor is fighting for the same air. 5 GHz is cleaner and faster, just with less reach. For a laptop in the same room as the router, 5 GHz is almost always the right call.

Many routers broadcast both bands under one name and let the device choose. In my experience, devices choose badly. Split the two networks with separate names and assign them manually. Tedious, yes. Effective, also yes.

Change the channel

On 2.4 GHz, you only have three non-overlapping channels: 1, 6, and 11. If your router is sitting on the same one as five neighbours, everyone suffers. Log in to the router, switch to a different channel, and re-test. If you have a scanner app on your phone, use it—otherwise just try each one and measure.

Count your devices honestly

Modern homes routinely run 20 to 40 connected devices. Cheap routers buckle under that load even when nobody's doing anything heavy. If your router is more than five years old and you're running a full smart home, that's your answer.

When it's only your phone that's slow

If every other device is fine and your phone crawls, stop troubleshooting the internet. The problem is the phone.

Common causes, in the order I usually find them: a WiFi assist feature that flips to mobile data mid-download, a VPN left running, a battery-saver mode that throttles background networking, or a stale network profile that needs to be forgotten and re-added. I had a two-month-old phone that dropped to 3 Mbps on WiFi; forgetting the network and rejoining fixed it permanently.

Test with mobile data on, then WiFi off, then both. The pattern tells you which radio is failing.

When to call your provider

Call once you have evidence, not frustration. Bring the wired speed test result, the time of day, and the fact that you've already isolated your own equipment.

What you're looking for: a wired result consistently below 70% of your plan, especially during off-peak hours. That points to a line, modem, or provisioning issue on their side. Evening-only slowdowns usually mean local congestion, which they can sometimes fix and sometimes can't—but it's worth the call either way.

What you shouldn't do is call them about WiFi. They'll reset the modem, tell you to reboot, and you'll be back where you started.

The honest summary

Slow internet at home is almost never one problem. It's a stack: the plan, the line, the router, the channel, the wall, the device. Your job is to peel the stack one layer at a time until the number moves.

And here's the thing I keep coming back to after years of these calls—the fix is usually cheaper and less dramatic than people expect. A cable, a router moved six feet, a background job cancelled. Not a new provider. Not a bigger plan.

Next time your connection drops, run the wired test before you run to the phone. You might be surprised how often the answer was sitting in your own living room the whole time.