A guest network is usually described as a security feature, and it is one. What the description leaves out is that the guest SSID sits on the same radio as everything else in the house. Four visitors streaming on your 5 GHz channel can push a work call into stutter even though the two networks cannot see each other at the IP layer. The separation is logical; the queue is physical.
One channel, one queue, and the phone at the end of the garden
Wi-Fi is not a switch that gives each device a private lane. Every station on a channel waits for a turn, and the access point decides how much airtime each turn consumes. A phone two metres away links at 866 Mbps on an 80 MHz channel; in a back bedroom it drops to 390, then 130, and at the garden’s edge to the 6 Mbps basic rate. From there a single photo upload holds the channel roughly a hundred times longer than it would from the sofa.
That is why “the internet crawls when guests arrive” seldom means the fibre line is saturated. A 100 Mbps connection with four people watching 1080p video is using about 20 Mbps. The line is bored. The channel is not.
Two controls attack the cause. Business access points expose a minimum basic rate setting; on consumer firmware the equivalent hides under “legacy rates” in the advanced wireless page, and raising the floor pushes distant clients off the network instead of letting them slow everyone. Asus routers also offer Airtime Fairness under Wireless > Professional, which stops one weak client from monopolising the channel. Turn both on if you have them. On Wi-Fi 6 hardware, OFDMA splits each transmission into resource units so several clients share one turn instead of queueing for the whole slot — the mechanism the Wi-Fi Alliance credits with better performance in crowded rooms.
Give guests the band with room to spare
Run the guest SSID on 5 GHz and leave the 2.4 GHz radio to smart plugs, baby monitors and the neighbour’s doorbell. The arithmetic is stark: 80 MHz on 5 GHz with two spatial streams gives an 866 Mbps nominal link and 400–500 Mbps of real throughput nearby, while a 20 MHz 2.4 GHz channel tops out at 144 Mbps nominal and often delivers 40–70 Mbps once the street’s other routers are counted.
Keep 80 MHz on 5 GHz only if a scan shows the 36–48 block empty; in a terraced street, 40 MHz loses less to retries than it gains in headline speed. On 2.4 GHz set 20 MHz and pick channel 1, 6 or 11, never in between. If the router hides behind a television cabinet, moving it beats every toggle below — see this guide to router placement for the before-and-after numbers.
If the guest SSID has never been switched on, start with the ten-minute guest Wi-Fi walkthrough for the exact menu names on TP-Link, Asus and Netgear firmware, then come back to tune it.
Cap the guest pipe with a number you chose
A bandwidth limit beats a ban, because you never have to be the person who tells a friend their phone is not allowed on the Wi-Fi. Most routers can apply a rule to the guest SSID rather than to individual devices, which means new visitors inherit it automatically.
- TP-Link Archer: Advanced > Bandwidth Control, enable the rule, then enter the guest ceiling. The interface wants kilobits, so 8 Mbps is 8000.
- Asus: Adaptive QoS > Bandwidth Limiter, or drop the guest SSID to the lowest QoS class.
- Fritz!Box: Internet > Filters > Priorities, guest profile in the “Background” class.
An HD stream needs about 5 Mbps, a 4K stream about 25 Mbps, and a video call 3 Mbps up and down. On a 100 Mbps line, a 30 Mbps guest ceiling covers four HD streams and leaves 70 Mbps for the house. Cap upload at 3–4 Mbps as well: most fibre plans are asymmetric, and guests backing up photos can ruin your call while the download graph still looks healthy.
Settings that cost throughput and buy nothing
Hiding the guest SSID keeps nobody out — the name travels in every association request — and it makes phones probe harder. A WPA3-only guest SSID looks strict until a visitor’s older handset refuses to join and somebody reads out the main password instead, which defeats the arrangement. Use WPA2/WPA3 mixed mode on the guest network.
Client isolation is worth keeping on: it blocks guest-to-guest traffic and cuts multicast chatter from discovery protocols. The trade-off is that Chromecast and AirPlay stop working from a guest phone, so point visitors at the television’s own apps. Leave UPnP and “allow guests to access local network” off.
A ten-minute test with three devices
Before the next gathering, run a speed test on a wired laptop, start two 1080p videos on guest phones, and ping 1.1.1.1 with ping -t. Latency should stay under 30 ms with no spikes past 150 ms. If it triples, the limiter is too high or the router’s NAT table is the bottleneck; iperf3 between laptop and guest phone separates the two by removing the internet from the measurement.
If the ping graph still looks like a saw blade after the cap is in place, the router’s CPU is the ceiling and no wireless setting will rescue it. A basic access point cabled to the LAN, broadcasting its own guest SSID with the same 8 Mbps limit, will hold the party together better than another hour in the admin pages.