Key Takeaways
- Bandwidth and lag are two different things. 500 Mbps with a 150 ms ping still feels broken in a game.
- Test with a cable first, then over WiFi. The gap between the two numbers tells you where the problem actually lives.
- Most "boosters" don't add speed. They repeat a weak signal, which is why your speed test looks better but your video call still stutters.
- 40 Mbps is plenty for two people streaming in HD. It is not enough for four 4K streams at once.
- Latency, jitter and packet loss are what you feel. Throughput is what you measure.
- One change at a time. If you change the channel, the router position and the DNS in the same evening, you learn nothing.
A friend called me last winter, furious. He had just paid for a 500 Mbps fiber plan and his son was still losing every match in an online shooter. "The speed test says 480," he kept repeating. "480! And the game is unplayable." He was measuring one thing and feeling another, which is the single most common mistake in this whole subject. Bandwidth is how much water fits through the pipe. Latency is how long a drop takes to reach the other end. You can have a firehose and still be the last one to the party.
If you want to boost your home internet speed and reduce lag, the first step is not buying hardware. It is understanding which of the two you are actually short on, because the fixes have almost nothing in common. I'll walk you through how I diagnose this, in what order, and where people waste money.
Why am I so laggy even with good internet?
Because your speed test and your lag are measuring different things, and only one of them shows up on Ookla.
When you run a speed test, you get three or four numbers. Most people read the first one and close the tab. The interesting ones are the small ones underneath: ping, jitter and sometimes packet loss.
- Ping (latency) — the round-trip time in milliseconds for a packet to leave your device and come back. Under 20 ms feels instant in a game. Above 100 ms and you start shooting at people who have already moved.
- Jitter — how much that ping wobbles from one moment to the next. A steady 60 ms is far more usable than a ping bouncing between 20 and 200. Voice and video calls care about jitter more than they care about raw speed.
- Packet loss — data that simply never arrives. Even 1% loss is enough to make a video call sound like a walkie-talkie in a tunnel.
So when someone tells me they have 500 Mbps and terrible lag, I already know the answer is probably not their plan. It is somewhere between their device and the router, or between the router and the ISP's first hop.
Test with a cable before you blame anything else
Plug a laptop directly into the router with an Ethernet cable and run a test. Then run the same test on WiFi, standing right next to the router. Note both numbers.
If the wired test is clean and the wireless one is a mess, your problem is local — channel congestion, distance, or an old adapter. If the wired test is also bad, the issue is upstream and no amount of router repositioning will save you. That one comparison has saved me more time than every forum thread I've ever read combined. I spent an entire weekend three years ago swapping WiFi channels before I bothered to check the cable. The cable was the problem.
Is 40 Mbps slow or fast?
It depends entirely on how many people are doing what, at the same time, in the same house.
40 Mbps is genuinely fine for a couple who stream in HD, browse, and take the occasional video call. It falls apart the moment you stack four or five demanding streams on top of each other. Here are the figures I use when I'm sizing a connection, and they've held up well in practice:
| Activity | Comfortable bandwidth | Ping that matters |
|---|---|---|
| Browsing, email, messaging | 2–5 Mbps | Irrelevant |
| HD streaming (1080p) | 5–8 Mbps per stream | Buffer time only |
| 4K streaming | Around 25 Mbps per stream | Buffer time only |
| HD video call | 3–5 Mbps up and down | Under 150 ms, stable |
| Competitive gaming | Under 10 Mbps — bandwidth is almost never the bottleneck | Under 30 ms, ideally under 20 |
| Cloud gaming (streamed) | 15–35 Mbps | Under 40 ms |
Notice the last two rows. A competitive gamer uses less bandwidth than a Netflix viewer, but is far more sensitive to ping. This is why the "get more Mbps" reflex is so often wrong. For gaming, the upload figure and the ping matter more than the download headline number.
One caveat I'd add: these are per-device, per-activity figures. Backups, cloud photo sync, and game downloads will happily eat everything you have and then ask for seconds. If a console is downloading a 90 GB update while you're trying to raid, no plan on earth will save your evening.
Do home WiFi boosters really work?
Partly, and almost never in the way the packaging implies.
A booster — extender, repeater, whatever the box calls it — receives your existing signal and re-broadcasts it. It does not create bandwidth. It cannot improve a line that is already saturated. What it does is extend coverage into a room your router can't reach.
Here's the part the marketing skips: a repeater typically halves the throughput on the extended network, because it has to receive and transmit on the same radio. So you get a bar of signal in the garage, and the speed there might be a quarter of what you get next to the router. For reading email on a tablet, that's a win. For a 4K TV or a gaming PC, it's worse than useless — it takes a bad situation and makes it look better on the device icon while feeling worse in practice.
What actually works, in rough order of how much I'd recommend it:
- A mesh system with a dedicated backhaul band (a separate radio just for talking between nodes). This is the real fix for a large or awkwardly shaped home.
- MoCA adapters — running network over your existing coaxial TV cabling. Genuinely excellent if you have coax in the walls, and criminally underused.
- Powerline adapters, with the caveat that performance depends heavily on your home's electrical wiring and can range from great to awful in the same house.
- A repeater, for low-demand devices only.
I'll be blunt: if you're going to spend money, spend it on the first option. I've watched people buy three different extenders over two years, spending more than a decent mesh kit costs, and still complaining. It's the same mistake in a new box.
Why am I lagging with 500 mbps internet?
Because the bottleneck is somewhere the speed test never looks.
Here's my short list, roughly in the order I check them:
WiFi band and channel congestion
2.4 GHz travels far and carries a lot of interference. In an apartment building, that band is a traffic jam. The 5 GHz band is faster and less crowded but doesn't pass through walls as well. Modern routers often merge both into one network name and let the device choose — which sometimes means your laptop sticks to the slower band and refuses to move. Splitting them into two named networks gives you control, at the cost of having to pick manually.
DNS resolution
This one surprises people. DNS is the lookup that turns a website name into an address. A slow resolver adds a delay before anything starts loading, even when your connection is fast. Swapping to a public resolver is a two-minute change and, on some ISPs, the difference is immediately noticeable.
On Windows, you change it in the adapter settings under IPv4. On Android, most phones let you set a private DNS hostname instead of an IP address. On a router, it's under WAN or Internet settings, and it applies to everything in the house at once.
Background traffic you forgot about
Cloud backup, photo sync, software updates, a smart TV quietly pre-loading something, someone's phone uploading a video. Bandwidth is shared, and something is always hungry. Most routers will show you a list of connected devices. Open it once and count. I found a forgotten tablet in mine that had been syncing photos for weeks.
What actually reduces lag, in order
Start with the free things, because they solve more cases than the paid ones.
- Move the router off the floor and out of a cupboard. Central, elevated, in the open. Not behind the TV.
- Use a cable for anything stationary and demanding — desktop, console, TV. Cables are boring and they win.
- Separate the 2.4 and 5 GHz networks. Put demanding devices on 5 GHz.
- Change the WiFi channel if your router's app shows a congested one.
- Turn off the router's "smart" auto-optimisation features if they keep reshuffling things. Sometimes the setting that promises to help is the one causing the jitter.
- Check for a router firmware update. Occasionally one fixes a genuine bug, and it costs nothing to look.
If you do all of that and your wired ping is still over 100 ms, the problem is outside your house. Call your provider and ask specifically about latency and packet loss, not speed. You'll get a different conversation.
How to increase internet speed in your device settings
Your phone or PC can be the bottleneck even on a perfect network.
On Windows, the biggest culprit is metered connection being off and something in the background downloading. Check Task Manager's network column while you're idle. If something is steadily pulling data, find out what it is. On older machines, an outdated WiFi adapter driver is a real limit — a laptop with a 2.4 GHz-only card simply cannot use your 5 GHz band, no matter what the router does.
On Android, the useful switches are: private DNS (for the resolution issue above), turning off WiFi scanning in location settings (it keeps the radio busy), and disabling battery optimisation for apps you need to stay connected. On iOS, "Low Data Mode" being off and a fresh network reset solve more oddities than people expect.
None of these will turn a 40 Mbps line into a 500 Mbps one. They remove friction, which is usually what lag actually is.
What I would do in your position
Run the cable test. Note the ping, not just the megabytes. Then decide whether you're fighting a bandwidth problem or a latency problem, because everything downstream of that decision is different.
And if you take one thing from all this: the number on the box and the number in your speed test have almost nothing to do with how the connection feels. The feel comes from the small numbers nobody reads. Which is why I now start every diagnosis there — after wasting a perfectly good weekend on WiFi channels that were never the issue.