Why Is My Wi-Fi So Slow? How to Speed It Up at Home (Without Buying a "Booster")

This is one of the most maddening tech problems there is, precisely because nothing looks broken. The Wi-Fi symbol is full. It says "connected." And yet a web page takes an age to load, a video stalls to buffer every thirty seconds, and a call freezes your face mid-sentence. It's worse than no internet at all, because there's nothing obvious to point at — so people assume they're stuck paying for a faster plan or buying a new router. Most of the time, you need neither.

A slow-but-connected Wi-Fi problem almost always comes down to a handful of free, physical things: which band your device joined, where the router is sitting, how many devices are fighting over it, how crowded the airwaves are where you live, and — sometimes — whether the trouble is actually your internet company's and not your Wi-Fi at all. Before any of that, one thing to skip: the "Wi-Fi booster," "speed up," and "network cleaner" apps you'll see advertised. They don't work. Independent testers have found the speed-booster apps are essentially placebos that make money from ads; the only honest "Wi-Fi analyzer" apps just show you which channels are crowded — none of them add a single megabit to what your connection can actually carry. Everything below is a real lever, and none of it costs anything.

First, run a real speed test — and compare it to what you pay for

Before you change anything, get a number, because "slow" means different things and the test tells you where to look. On a phone or laptop, run a speed test (Speedtest by Ookla or Fast.com are the usual ones) while standing right next to the router, then run it again from the room where things feel slow. Write down both. Then do the single most useful test if you can: plug a laptop straight into the router with an Ethernet cable and run it once more. That wired number is close to what your internet line is truly delivering, with Wi-Fi taken out of the equation.

Now compare. If the wired test roughly matches the speed on your bill (say you pay for 300 Mbps and wired gives you ~300), then your internet is fine and your problem is Wi-Fi — every fix in this article applies, and you don't need a faster plan. If even the wired test comes back far below what you pay for, the problem is upstream of your Wi-Fi: it's your modem, your line, or your provider, and no amount of moving the router will help (skip to the "when it's your ISP" section). And here's the honest possibility nobody selling you anything will mention: sometimes the speed test simply shows you're getting what you signed up for. A cheap 50 Mbps plan shared across a house of streamers and gamers will feel slow no matter how perfect the Wi-Fi is — that's a plan problem, not a fault.

You might be on the slow lane: 2.4GHz vs 5GHz

Almost every modern router broadcasts on two different bands at once, and which one your device is using makes a huge difference. The 2.4GHz band reaches farther and pushes through walls better, but it's slower and — crucially — it's the crowded one: microwaves, cordless phones, baby monitors, garage remotes, Bluetooth, and every neighbor's router all sit on 2.4GHz too. The 5GHz band is much faster and far less congested, but its range is shorter and it doesn't punch through walls as well. If your phone or laptop has quietly latched onto the 2.4GHz band while you're sitting close to the router, you're crawling in the slow lane for no reason.

Many routers hand out both bands under a single network name and decide for you, often badly — a device can "stick" to 2.4GHz long after you've walked back into the same room as the router. If your router lets you split them into two separate names (many show something like "MyWiFi" and "MyWiFi-5G"), do it, and when you're near the router join the 5GHz one for the fast, high-bandwidth stuff — video calls, streaming, big downloads, gaming. Save 2.4GHz for range: the far bedroom, the thermostat, the garage door opener. This one change alone fixes a startling number of "my Wi-Fi is slow" complaints.

Where the router sits matters more than you'd think

Wi-Fi is radio, and radio gets weaker with distance and every obstacle in the way. A router shoved in a closet, behind the TV, on the floor, or in a far corner of the house is fighting a losing battle before it starts. Two thick walls between you and the router can cut your speed roughly in half, and the worst offenders are things with water or metal in them: a fish tank, a mirror, a refrigerator, a stack of pipes in a wall. The fix costs nothing — move the router to a central, open spot, up off the floor (a shelf around chest height is ideal), with a few inches of air around it and as clear a line as possible to where you actually use your devices.

There's a very Southern California wrinkle here worth knowing. A lot of the older housing stock across LA, Pasadena, and the inland valleys was built with metal-lath-and-plaster interior walls and stucco exteriors — and that thin layer of metal mesh inside the plaster is genuinely rough on Wi-Fi, far more so than the drywall in newer builds. If you're in a 1920s–1950s bungalow or Spanish-style home and the signal dies the moment you cross one particular wall, that wall is very likely lath-and-plaster. You can't change the walls, but you can put the router on the same side of them as the rooms you use most, or plan for a mesh point on the far side (more on that below).

Too many devices — or one quietly hogging everything

Your Wi-Fi has a finite amount of capacity, and every connected thing takes a slice: phones, laptops, TVs, tablets, doorbells, speakers, thermostats, watches, the kids' consoles. Most sit idle most of the time, so a long device list on its own isn't the problem. The problem is when one of them starts doing something heavy — someone streaming 4K in one room, a game console downloading a 90GB update, a laptop uploading a backup to the cloud, or a phone syncing its whole photo library. Any one of those can eat most of your bandwidth and leave everyone else crawling, and it often explains why your Wi-Fi is fine all day and then falls apart at 8pm.

To find it, think about what changed when the slowdown started, and check the obvious heavy hitters: pause a big download, stop a cloud backup mid-sync, or turn off a stream and see if everything else springs back to life. If your Wi-Fi is reliably slow at the same time every evening, that's the household-congestion pattern, not a fault. Some routers have a "Quality of Service" (QoS) setting that lets you prioritize, say, video calls over background downloads — worth turning on if you have it. And if the slowdown is genuinely every device, all the time, no matter what's running, that points away from a single hog and back toward the band, placement, or router-age issues in the rest of this guide.

If your suspicion is that the hog isn't yours at all — that a neighbour is on your Wi-Fi — you can check that directly in your router's device list, though be warned that the list is much harder to read than it used to be and most "unknown" entries turn out to be your own gadgets. We've written a separate guide to seeing exactly who's connected and getting anyone who shouldn't be there off for good.

Crowded airwaves: the apartment and dense-neighborhood problem

If you live in an apartment, a condo, or a packed neighborhood, your Wi-Fi is competing with everyone else's. Every router around you is broadcasting on one of a small number of channels, and when yours happens to share a channel with three neighbors, all of you slow each other down — like everyone trying to talk in the same crowded room. This is especially bad on the 2.4GHz band, which has very few non-overlapping channels to go around, and it's a real, everyday issue in the denser parts of Southern California, from Koreatown and Hollywood apartments to the packed condo blocks near the coast.

It is worth understanding what "sharing a channel" actually means, because it explains why this feels so different from a slow connection. Cisco's own network-design documentation describes every device sitting on one channel within range of each other as forming "a single broadcast domain, similar to an Ethernet hub" — one conversation, and only one device can talk at a time. Before any device transmits it listens, and if it hears anything already in progress it backs off a random moment and listens again. That "anything" includes your neighbour's television. As the documentation puts it, once enough devices need the channel, "devices spend more time receiving than sending. This results in slower speeds because devices have to wait longer to send data." Nothing is broken and no signal is weak. Your house is simply queueing behind a building.

In a house, the good news is you rarely have to fiddle with channels by hand. The simplest fix is the oldest one: reboot the router. Unplug it, wait a full thirty seconds, and plug it back in — most routers pick a less-crowded channel automatically on restart, and this alone can take a connection from a stuttering crawl back to full speed. If yours has an "auto" channel setting, leave it on auto. If you want to go one step further and your router lets you log in to its settings, the free Wi-Fi analyzer apps mentioned earlier are actually useful for exactly this: they show which channels your neighbors are crowding so you can move yours to a quieter one. That's the honest, useful thing those apps do — not "boosting" anything, just helping you dodge the crowd.

But in a genuinely dense building that advice runs out, and it is worth being honest about why. Auto-channel finds the least-bad channel available; it cannot create a quiet one. On 2.4GHz in the United States there are only three non-overlapping channels — 1, 6 and 11 — so in a stack of thirty units there is no quiet channel to move to, and every router on the floor is running the same auto-channel logic against the same three options. That is the point at which the standard advice stops being enough, and the next section is about what changes.

In a dense building, the usual advice starts working backwards

This is the part almost nothing written about slow Wi-Fi will tell you, and it is the single most useful thing on this page if you live in an apartment, a condo stack, a townhouse row, a duplex, or one of the coastal blocks where the houses stand a few feet apart. When congestion rather than distance is the problem, the three things everyone reaches for — a wider channel, more transmit power, another Wi-Fi box — each make it measurably worse. Not "help less." Worse. Every one of them puts more radio into a room that already has too much.

Start with channel width, because it is the setting nobody touches and the one that matters most here. A "wider" channel is not a bigger pipe carved out of thin air; it is made by bonding neighbouring channels together, so the width you gain comes directly out of how many separate lanes exist. Cisco's design guidance for high-density spaces states it plainly: moving to 40MHz is "effectively halving" and 80MHz "quartering" the number of non-overlapping 5GHz channels. The arithmetic at your address is stark. In the US, the 5GHz channels a router can use without touching the radar-shared DFS band are 36, 40, 44 and 48 at the bottom and 149, 153, 157 and 161 at the top — eight lanes at 20MHz wide, which at 80MHz collapse into exactly two. Two lanes, for a building with forty routers in it. If your router exposes the setting (look for "channel width", "bandwidth" or "VHT80"), put 5GHz on 40MHz, or 20MHz if things are grim, and leave 2.4GHz on 20MHz always.

The honest trade is that you will lose peak speed on the label. You will usually gain speed in practice, because a narrower channel that you actually get to use beats a wider one you spend your evening waiting for — and Cisco notes that in badly contested airwaves even 80MHz-capable devices frequently end up using just the 20MHz base channel anyway. One caveat before you go looking: plenty of provider-supplied gateways bury this setting, and several mesh systems (eero being the well-known example) deliberately do not expose channel or width at all. If yours does not offer it, that is not a fault — skip to the band advice below, which does not need the setting.

Transmit power is the second reflex, and turning it up is the wrong direction in a building. You cannot out-shout your neighbours — they are running the same hardware, and the loudest thing in the room does not get served first, it just makes a larger area of the building unusable for everyone including you. There is also a plain physical asymmetry: your laptop and your phone still answer at their own small power, so a louder router does not make the reply any easier to hear. Leave power on automatic, or turn it down if your router offers the choice. We go through this and the rest of the renter-specific version of the problem in our guide to what you can actually change about the internet in a home you do not own.

The third reflex is the expensive one: buy another box. Here the vendors document the problem themselves. Cisco Meraki's high-density guidance states outright that "adding additional access points on the same channel with overlapping coverage does not increase capacity" — an extra radio on a busy channel is one more device waiting its turn, not more room. And a mesh node that talks to your router over the air is relaying every packet twice on that same congested channel: the same vendor's mesh guide puts the cost at "about 50%" of throughput per wireless hop and recommends designing for no more than one. In a one- or two-bedroom apartment, where the far wall is thirty feet away, a second wireless node is nearly always the wrong purchase.

So what does work, in order of how much it helps. Move everything you can to 5GHz, and to 6GHz if you have Wi-Fi 6E or 7 hardware — not despite the shorter range but because of it, since the walls that have been ruining your signal are the same walls keeping your neighbours' signal out. (6GHz is especially quiet: when the FCC opened the band in 2020 it allowed 1,200MHz of spectrum for low-power indoor use, which is an enormous amount of room that very little hardware is using yet.) Narrow the channel as above. Leave power alone. Put the stubborn 2.4GHz-only devices — most smart plugs, most older printers — on their own network name so they stop dragging your laptop down to the slow band. And wire whatever you can reach: a device on a cable is a device that has left the queue entirely, which helps every other device in the house at the same time.

An aging router (or one that just badly needs a reboot)

Routers wear out in a way that isn't obvious, because they don't break — they just get slower and flakier over years of running hot, 24/7, quietly leaking memory. If you've genuinely never restarted yours, do it now; it's the single most effective free fix there is, and a good habit is to power-cycle the router once a month. While you're in there, check for a firmware update in the router's settings (or the app for a newer model) — makers push fixes for speed and security that you otherwise never get.

If a reboot helps for a day and then it's slow again, or the box is genuinely old, age may be the real answer. Wi-Fi standards have moved on: an older router built to the Wi-Fi 5 standard (or, worse, something from before that) simply can't juggle a modern houseful of devices the way a Wi-Fi 6 or Wi-Fi 7 router can — the newer ones are built specifically to keep per-device speeds up when a dozen things are connected at once. If your router is more than about four or five years old, or it's the basic gateway your provider handed you years ago, upgrading it is often the thing that finally fixes a chronically slow house. Two honest caveats before you spend: a new router only helps if your devices are new enough to use the newer standard too, and if your problem is really a weak signal in one distant room, a faster router in the same spot won't reach any farther — that's a coverage problem, covered below.

And if you want to settle the age question properly rather than guess at it, there's a better test than the calendar: check whether the manufacturer still ships security firmware for your exact model, which is a published date you can look up in a few minutes. Our guide to how old your router is and whether it needs replacing walks through finding the model and hardware version, checking it against the maker's end-of-service list, and the two settings worth changing on any older router even if you keep it.

When it's your internet company, not your Wi-Fi

Sometimes the fault is genuinely upstream and nothing in your home will fix it — which is exactly why that wired speed test at the top matters. If even a device plugged straight into the router is slow, or your whole neighborhood grinds to a halt at peak evening hours, the issue is on your provider's side: a local outage, congestion on the node your street shares, a line problem, or the plan itself. Check your provider's app or outage map, and if the slowdown is severe or constant, call them — you're paying for a speed, and they can test your line remotely and tell you whether the signal reaching your home is bad.

Which company that is depends on where in Southern California you are: Spectrum covers much of Los Angeles, Orange, Riverside, and Ventura counties on cable; Cox is the main cable provider across San Diego and the Coachella Valley; AT&T and Frontier offer fiber in parts of the region where it's been built out; and where wired options are thin, T-Mobile and Verizon now sell 5G home internet that runs over the cellular network. Fiber, where you can get it, tends to be the most consistent; cable is widely available but shares capacity with your neighbors (hence the peak-hour slump); and 5G home internet is convenient but can vary with cellular load. Knowing which you have — and whether the speed reaching your house actually matches your plan — is the difference between chasing a Wi-Fi fix that was never the problem and getting your provider to sort out their end.

And if the answer at your address turns out to be that there is no wired option at all — no cable, no fibre, and a DSL line nobody will invest in — that is a different problem with a different set of answers, and we have written it up separately: how to check what is genuinely available at your exact address rather than your town, how to challenge a provider that claims to serve you and will not connect you, and what quietly stops working once your internet arrives over satellite or a cellular gateway instead of a wire.

One room that's always dead? That's coverage, not speed

It's worth separating two problems that feel the same. If your Wi-Fi is slow everywhere, it's one of the band, placement, congestion, router, or ISP issues above. But if it's fast near the router and dies in one specific room — the back bedroom, the garage, the upstairs office, the far end of a long house — that's not a speed problem, it's a coverage problem, and no amount of rebooting or band-switching will reach a room the signal physically can't get to. Those lath-and-plaster walls and long SoCal ranch-house layouts are classic culprits.

The real fix for a dead room is to extend the network, and the modern answer is a mesh Wi-Fi system — a set of units that blanket the whole house in one seamless network so you keep full speed as you move between rooms. It's a genuine purchase rather than a free tweak, so it's worth understanding when it's actually the right call versus when a better-placed single router would do; we walk through that trade-off honestly in our guide on mesh Wi-Fi versus a single router. But if you've got real dead zones, that's the lever — not another speed test.

With one caveat that follows directly from the section above: if you live somewhere dense, feed that extra node with a wire. A mesh unit talking to your router over the air is relaying on the same crowded channel your neighbours are already filling, which is why the throughput cost per wireless hop is roughly half. A wired node has none of that problem — it takes traffic off the air instead of adding to it. That does not have to mean drilling: the coax outlets already in the walls of most Southern California homes will carry a network with a pair of MoCA adapters, and a single ethernet run up a stairwell is often a one-afternoon job. We compare the options — coax, powerline, and when each is worth it — in our guide to getting ethernet to a room that has none. In a long ranch house with a dead back bedroom, a wireless node is fine. In a condo stack, wire it or skip it.

How we can help

The honest short version: connected-but-slow Wi-Fi is almost never a broken router and almost never fixed by an app. Run a speed test and compare it to the plan you pay for; get on the 5GHz band when you're near the router; move the router out of the corner and up off the floor; find the device that's hogging everything; reboot to dodge crowded channels and clear an aging router's cobwebs; and know the difference between a slow house (band, placement, router) and one dead room (coverage — a mesh job). And if you live somewhere dense, remember that the advice inverts: narrower channel, not wider; power down, not up; wire an extra node rather than letting it relay over air. Work through those and you'll fix the large majority yourself, for free.

If you've tried all of it and the house is still slow — or you'd simply rather someone come figure out whether it's your router, your layout, your neighbors' airwaves, or your provider shortchanging you — that's exactly the kind of everyday tech headache we help with. We work with people across Southern California and the Coachella Valley on home Wi-Fi that isn't keeping up: sorting out router placement and settings, telling you honestly whether a mesh system or a new router is genuinely worth it or whether a free tweak will do, and helping you hold your internet provider to the speed you're paying for. Because we don't sell you internet plans or hardware, there's no reason for us to tell you to buy something when a reboot and a better shelf were the whole fix.