The invisible auction happening before you load a page

You open your laptop in a coffee shop. Four bars of Wi-Fi. A loading spinner that just keeps spinning. You blame the café, or your ISP, or some vague cosmic malevolence, but the actual culprit is probably a channel collision you can't see and the router made no attempt to avoid.

Your phone didn't choose badly on purpose. It followed rules baked into the Wi-Fi standard, rules designed for a world with far fewer routers. In dense environments, those rules produce genuinely terrible outcomes. Understanding why explains a lot about why wireless performance is so weirdly, maddeningly unpredictable.

What a Wi-Fi channel actually is

Think of the radio spectrum as a highway with painted lanes. A Wi-Fi channel is one lane. On the 2.4 GHz band, which most older and budget devices still use, there are technically 14 channels, but only three don't overlap: 1, 6, and 11. Every other channel bleeds into its neighbours. A router on channel 3 is partially colliding with both channel 1 and channel 6 simultaneously, which is about as useful as straddling two motorway lanes at once.

The 5 GHz band is less crowded. It has somewhere between 24 and 45 non-overlapping channels depending on your country's regulatory domain, which is why moving to 5 GHz almost always feels faster in an apartment building humming with competing networks.

Channel width matters too. A 40 MHz channel carries more data than a 20 MHz one, but it eats more spectrum. In a congested building, a router blasting a 40 MHz channel on 2.4 GHz is essentially swallowing two of the three usable lanes at once.

How your phone actually picks a channel

Here's the part that surprises most people: your phone doesn't pick the channel. The router does.

When you connect to a network, the router is already broadcasting on a fixed channel. Your phone scans for available networks, reads the beacon frames each router sends (tiny packets broadcast roughly ten times per second), and sees which channel each access point is using. When you tap to connect, your phone tunes its radio to match whatever channel that router has already claimed.

So the real question is how the router chose its channel in the first place.

Most consumer routers do this once, at boot, using automatic channel selection. The router scans the spectrum, counts how many other networks it detects on each channel, and picks the one that looks least occupied. Some also measure signal strength and noise floor. The smarter ones, especially those running enterprise firmware or newer Wi-Fi 6 and 6E hardware, rescan periodically and shift if congestion builds.

Most cheap home routers scan exactly once and then stay put forever. Which means if your neighbour bought the same router model, both units may have scanned at the same quiet moment, both concluded channel 6 was empty, and both camped there permanently.

The passive scan problem

When your phone looks for networks to join, or reassesses which access point to connect to on a mesh network, it runs a passive scan: listening on each channel for beacon frames rather than transmitting anything itself.

Polite. Also slow. Scanning all 2.4 GHz channels takes a few hundred milliseconds. Scanning 5 GHz and the newer 6 GHz band takes longer. During a scan, the radio isn't receiving data, so active connections pause briefly. That tiny stutter when your phone considers switching access points? That's this.

The phone's decision about whether to stay or switch is governed by a roaming aggressiveness threshold. Most phones are conservative: they'll hold a mediocre connection rather than drop it to hunt for a better one, because dropping and reconnecting costs time. Both iPhones and Android devices tend to cling to their current access point until signal drops below roughly minus 70 to minus 75 dBm. Two bars is still a connection, and the phone treats uncertainty as worse than a known mediocre signal.

When six routers share three lanes

Marta and Tom buy identical mesh router systems and move into flats on the same floor of an apartment building. Both systems boot on a Wednesday afternoon, scan the spectrum, and both pick channel 1 on 2.4 GHz because the building is quiet. Four neighbours have older routers that haven't moved from channel 6 in years.

By Saturday evening, networks from channel 11 are bleeding in from the floor below. Marta's phone, in her kitchen near a shared wall, is connected to her mesh node on channel 1. Tom's router is also on channel 1, two flats away. Both routers are taking turns, because 802.11 uses a collision-avoidance system called CSMA/CA: devices listen before they transmit, and if the channel is busy, they wait a random back-off interval and try again.

With two routers sharing channel 1, all their connected devices are constantly yielding to each other. Throughput doesn't halve exactly, but it degrades noticeably. Add a third device on channel 1, say a neighbour's baby monitor, and the back-off intervals stack. Each device waits longer. Latency climbs. Video calls stutter even though the signal bars look fine.

This is why a speed test in a crowded flat sometimes returns 20 Mbps on a connection theoretically capable of 300.

What people consistently misread about this

The most common mistake is blaming signal strength. Someone sees two bars and assumes the router is too far away. They move it closer, signal jumps to four bars, speed stays miserable. The channel is still congested. Signal strength and channel congestion are completely separate problems, and conflating them sends you on a furniture-rearranging goose chase.

The second mistake is assuming a newer phone will sort this out. Phones don't control the channel. A Wi-Fi 6 phone connecting to a Wi-Fi 5 router on a congested channel is still on that congested channel. The newer radio handles the protocol more efficiently, but it cannot invent spectrum.

And here's the subtler one, the mistake even technically-minded people make: assuming 5 GHz is always the better choice. It has more lanes, yes. But 5 GHz signals attenuate faster through walls. Two rooms and a concrete wall away from the router, your phone's 5 GHz radio may be running at reduced modulation rates anyway, and you'd have been better off on a clear 2.4 GHz channel all along.

The one setting worth checking

If your router has a manual channel selection option in its admin panel, use it. Log in, check which channels your neighbours are using (Wi-Fi Analyzer on Android will show you a real-time channel map), and park your router on whichever of channels 1, 6, or 11 has the fewest competing networks.

On 5 GHz, channels in the 149-165 range (the upper UNII-3 band, where regulations allow it) are often less used than channels 36-48, simply because older devices don't support them.

And if you have a Wi-Fi 6E router? The 6 GHz band is almost certainly empty. Connecting a compatible phone to a 6E network in a congested building is like discovering a third motorway that opened last month and nobody else knows about yet.

Have you ever actually opened your router's admin panel? Most people haven't. Most people are also quietly suffering on channel 6 with four of their neighbours.

The deeper issue here is one that no firmware update fully solves: wireless performance is a shared resource problem, not a personal technology problem. Your phone and router can be excellent. The spectrum they run on is a commons, and commons get congested. Every version of Wi-Fi since 802.11n has responded by adding more lanes, smarter scheduling, and better ways for devices to take turns. Wi-Fi 7's multi-link operation, which lets devices use two bands simultaneously and switch mid-stream, is the latest attempt to paper over a fundamental scarcity. It helps. The coffee shop will still be slow on a Tuesday morning.