To improve WiFi speed, use the quick checks first and then match the fix to the symptom. Prove whether the bottleneck is the room, device, wireless band, household contention or router before replacing hardware.
Immediate quick fixes
Start beside the router, compare the slow room, then test another device. That sequence quickly shows whether the real bottleneck is weak signal, one poor client, busy-household contention or the line beyond Wi‑Fi.
Use a clean reboot before changing channels or buying hardware.
If speed is good nearby, the slow room is the clue.
Busy-household load can look like a Wi‑Fi fault.
This separates one bad client from a room-wide wireless issue.
Guide index
Use the section that fits the result you saw, rather than reading the whole page in order.
Start here
Keep the device, room and test server consistent. Use the same LinkSpeed speed test for each comparison so each result removes one possible cause instead of creating a new guess.
This is your best-case wireless baseline. Record download, upload, ping and jitter.
If speed collapses here, distance, walls or band choice are the main suspects.
If a modern phone is fast but the TV or laptop is slow, the client is likely the bottleneck.
If Ethernet is also slow, stop blaming Wi‑Fi and investigate the line or router load.
| If you see this result | It usually points to | Go to this section next |
|---|---|---|
| Fast beside the router, slow in the problem room | Weak signal, poor placement, thick walls, foil-backed insulation or a bad band choice. | One room is slow |
| Only one device is slow everywhere | Older Wi‑Fi standard, fewer MIMO streams, outdated drivers or weak client hardware. | One device is slow |
| Everything slows when the household gets busy | Airtime contention, uploads, queueing or router load rather than simple signal loss. | Busy-household slowdowns |
| Wi‑Fi looks fine but Ethernet is also poor | The line, provider path or router under load may be the real limit. | Advanced checks |
Room-based slowdown
This is the classic weak-signal pattern. The fix is rarely “buy faster broadband”. It is usually better placement, shorter distance, fewer obstructions or getting the device onto the right band.
If Wi‑Fi is good within sight of the router and poor only in one room, the broadband line is probably fine. The device is losing link rate as the signal passes through distance, floors, brickwork, chimney breasts or foil-backed materials.
Move the router into the open, away from the floor, large TVs, metal furniture and corners. If possible, test the same room on 5 GHz and 2.4 GHz to see whether one band is clearly more stable.
A mesh node works best halfway between the router and the slow room. Putting the node inside an existing dead zone usually just repeats a weak signal more neatly.
For a fixed TV, desktop PC or console, an Ethernet cable often fixes the problem more cleanly than chasing perfect Wi‑Fi through multiple walls.
If the issue is isolated to an upstairs room or one side of the house, also compare the room-specific fixes in Wi‑Fi slow upstairs and Wi‑Fi slow in one room.
Client bottleneck
If other devices are fast in the same place, the router is usually not the main problem. Look at the client first.
Budget TVs, streaming sticks and older laptops often use weaker radios and fewer antennas than a modern phone. They may also support narrower channels or older standards that cap real throughput far below what the router advertises.
A 4×4 router does not guarantee 4×4 performance on a 1×1 or 2×2 client. The negotiated rate is limited by the weaker end of the link, so one slow device can stay slow everywhere.
Update the device OS, Wi‑Fi driver and firmware where supported. Disable aggressive power saving during testing so the client does not reduce its own link performance.
Retest the same device beside the router. If it is still much slower than a modern phone or laptop there, the client hardware is the limiting factor. For fixed devices, use Ethernet where possible.
Loaded household
This often feels like “bad Wi‑Fi”, but the real bottleneck can be shared airtime, background downloads, cloud sync or router queueing. Use the bufferbloat test and a repeatable speed test to see what changes under load.
Wi‑Fi is half-duplex, so devices take turns transmitting on the same channel. Add uploads, app updates and cloud backups, and the router may also queue traffic badly when the broadband link is full.
Pause large downloads, cloud backups and CCTV uploads, then rerun the same test. If Wi‑Fi improves immediately, the slowdown is caused by contention or queueing rather than raw signal strength.
Schedule heavy transfers outside busy hours, wire fixed devices where possible, and enable sensible QoS or SQM if the router supports it.
If latency rises sharply or throughput collapses only when the house is busy, the router CPU or queue management may be the real issue. That is when faster broadband alone rarely fixes the experience.
If the symptom is loaded latency rather than basic throughput, go straight to how to fix bufferbloat or the deeper router settings guide for SQM and traffic-priority checks.
Band, channel and placement
Use 5 GHz where coverage is strong and you want speed. Use 2.4 GHz for difficult rooms or older devices that need range more than raw throughput.
In 2.4 GHz, channels 1, 6 and 11 are normally the safest non-overlapping options. In crowded areas, scan nearby Wi‑Fi first instead of changing channels at random.
Put the router out in the open, as central as practical and above desk height. Avoid cupboards, floor level, radiators, mirrors and sitting directly behind a TV.
If Smart Connect keeps pushing capable devices onto the wrong band, split 2.4 GHz and 5 GHz temporarily and compare results. Keep the change only when it produces a clear improvement.
Advanced checks
A slow speed test does not tell you whether the client is stuck on the wrong band, limited by low MIMO capability or just sharing too much airtime. These checks help power users confirm the real wireless ceiling.
Run netsh wlan show interfaces and record the receive rate, transmit rate, radio type, channel and signal strength. The receive/transmit rates are the negotiated Wi‑Fi link rate, not guaranteed internet throughput.
On macOS, hold Option while opening the Wi‑Fi menu. On Android, inspect the active network details where link speed is exposed. On Linux, use iw dev and iw dev wlan0 link where supported.
A low link rate beside the router usually means the device is on the wrong band, using a narrow channel, or limited by old client hardware. A healthy link rate with poor speed tests points back to queueing, router load or the line beyond Wi‑Fi.
If the broadband line also feels unstable, compare this page with why is my broadband slow. If gaming feels worse than browsing, use why is my ping high for latency-led diagnosis.
FAQs
That usually points to weak signal, thick walls, bad placement or the device falling back to a slower link rate in that room. Test beside the router first, then in the slow room, and compare the band if possible.
One device can be limited by older Wi‑Fi standards, fewer antennas, weaker MIMO capability, outdated drivers or power‑saving behaviour. Compare a second device in the same spot before changing the router.
That is often shared-airtime contention or router queueing, especially when streaming, gaming, cloud sync and uploads happen together. Pause background traffic and retest to prove whether load is the trigger.
Only if testing proves Smart Connect is placing important devices on the wrong band. Split the SSIDs temporarily, compare results in the same room and keep the change only if it clearly improves stability or speed.