// FAULT-FINDING · HOMES & SMALL OFFICES

Why is my WiFi slow? Find the real fault

Nearly every “bad WiFi” call turns out to be one of about a dozen faults, and most of them are not the WiFi at all. This is the order we diagnose in and the fixes that actually work — including the honest moment where the answer is “your broadband line is the bottleneck and no equipment will change that”.

Rated 4.9 on GoogleFamily-run since 1995 · no fix, no fee

/01 — DIAGNOSE FIRST

Seven tests, in this order, before you change anything

Changing settings before you have measured anything is how people end up three hours in with a worse network than they started with. Do these first and write down three numbers each time — download, upload and ping.

  1. Wired versus wireless, in the same spot, in the same minute. This single test splits every fault into “the line” or “the WiFi”.
  2. At the router versus in the problem room, recording band, channel and signal strength each time.
  3. 11am versus 8–10pm. Congestion faults only appear in the evening.
  4. Latency and packet loss, not just megabits. Most “slow” complaints are actually latency complaints.
  5. Latency under load — start a big download and watch the ping. This is the test almost nobody runs and it explains more faults than any other.
  6. The provider’s status page. Ten seconds, and it occasionally ends the whole investigation.
  7. On copper lines only, the master test socket — and only where the faceplate has a horizontal split across it. If there is no horizontal bar, do not unscrew it.

// FIX IT WITH ME · STEP BY STEP

Run the seven tests with me, in order

The seven tests from this guide, one at a time, before you change anything. Tell it what each test showed and it moves you on. Nothing here leaves your device.Last reviewed 6 October 2026

Checking which Windows you have…STEP 1 OF 7
  1. 01Wired versus wireless

    Wired versus wireless, in the same spot, in the same minute. This single test splits every fault into “the line” or “the WiFi”. Full detail in the guide below ↓

    Did that test find the fault?

Rather have it done for you? Remote help from £20, or in person across Bournemouth, Christchurch, Poole, Ringwood and the New Forest, with no call-out fee.

/02 — THE SYMPTOM MATRIX

Find your symptom

SymptomUsual causeWhat actually fixes it
Fast on Ethernet, slow on WiFiDevice sitting on 2.4 GHz; wrong channel width; an old device; a single-radio extender in the pathCheck which band the device is on. Set 2.4 GHz to 20 MHz and 5 GHz to 80 MHz. Test a second modern device from the same spot. Remove plug-in extenders.
Fine in one room, dead in anotherThe building — solid brick, foil-backed board, concrete, low-E glass. Or the router is in a cupboardMeasure, don’t guess. Reposition the router first, then run one Ethernet cable to a well-placed access point. A cable costs about £3 and is usually the best value fix available.
Drops out at the same time every dayAlmost never WiFi. A scheduled reboot, a DHCP lease expiring, parental-control downtime, or household electrics switching onRead the router’s event log — it distinguishes a broadband resync from a wireless event. Check the DHCP lease time and look for a second DHCP server. Correlate the time with what switches on. Full method: WiFi keeps dropping.
WiFi calling won’t workNot provisioned; no registered 999 address; UDP 500/4500 blocked; SIP ALG enabledIn order: confirm provisioning with the network, register the emergency address, update the handset, then allow outbound UDP 500 and 4500 and disable SIP ALG. If the toggle is missing entirely, no router change will help.
Video calls stutter but downloads are fineBufferbloat, or a saturated upload — cloud backup and file sync are the usual culpritsEnable Smart Queue Management (fq_codel or CAKE) with a shaper just below your real line rate, then re-test. Check what is uploading in the background. Prefer 5 GHz and use split tunnelling on VPNs.
Phone clings to a distant nodeRoaming is the device’s decision, not the network’s. Usually over-powered nodesEnable 802.11k/v/r where supported, set a minimum-signal threshold around −70 to −75 dBm, disable the slowest legacy rates, and turn the transmit power down on over-powered nodes. Some devices simply refuse to roam.
Smart-home devices keep dropping off2.4 GHz-only devices; auto-channel moving under them; WPA3 or mandatory PMF; the address pool running outPin the 2.4 GHz channel manually — the only durable fix with a smart home. Use WPA2 or transitional mode on 2.4 GHz. Widen the DHCP pool: many ISP hubs ship with only 32–64 addresses, after which devices “connect but have no internet”.
The printer keeps vanishingClient isolation (on by default on most guest networks) breaking discovery; or it changed address after a power cutSame network and subnet? Client isolation off? Then give the printer a fixed address reservation and add it by IP address rather than by automatic discovery.
Everything slows when the neighbours get homeEither radio congestion or provider backhaul congestion — completely different fixesRun a wired test at 8–10pm. Still slow on the cable? It is the provider, and no WiFi change helps. Fine on the cable? Radio congestion: pick 1/6/11 manually at 20 MHz and consider reducing transmit power.
Buffering on one TV onlyThe TV’s radio is usually the cheapest component in the set, and it is often in a wall unitCheck the TV’s network screen for band and signal. Streaming needs far less than people think — if it has 25 Mbps and still buffers, bandwidth is not the problem. Wire it, or add a streaming stick with a better radio.
5 GHz drops for a minute, 2.4 GHz unaffectedRadar detection — not a fault. Common near airports, ports and the coastConfirm from the router log that radar was detected, then pin 5 GHz to a non-radar channel, or drop from 160 to 80 MHz so the radio is not forced into the radar range. Never defeat this in firmware — it is a legal condition of using the band.
Some sites load, others don’tName resolution, not WiFi — especially if mobile data loads the same sites fineCheck whether the address resolves. Also check provider-level filtering and parental profiles before changing anything. Set the resolver on the router, not per device. On a business network, be careful — changing this can bypass required filtering.
Port forwarding does nothing; console says Strict NATDouble NAT, or carrier-grade NATCheck the router’s WAN address. A private address means self-inflicted double NAT — put the ISP hub in modem mode. An address in the 100.64.x.x range means carrier-grade NAT, and no local change fixes it: you need the provider to give you a public address, or an outbound-only remote-access product.
“The internet is down”The line, not the WiFiCheck the broadband light, the provider’s status page, and a wired device. On copper, repeated resyncs get managed by the network and can permanently reduce your speed — fix the noise source rather than rebooting daily.

/03 — INTERFERENCE

Interference: what actually matters in a UK home

  • Microwave ovens leak around 2.45 GHz, and the peak sits over 2.4 GHz channels 9–11 — so channel 1 is the least affected. This is a genuine, measurable effect for the two minutes the oven runs.
  • Baby monitors: DECT models work around 1.9 GHz and do not affect WiFi at all. The 2.4 GHz frequency-hopping ones hop across the whole band and genuinely do. It is worth knowing which you have before blaming it.
  • Cheap analogue 2.4 GHz cameras and video senders transmit continuously and are among the worst offenders in any house.
  • USB 3.0 ports, external drives and unshielded cables radiate broadband noise centred right in the 2.4 GHz band. Move any 2.4 GHz hub or dongle away from them — this one surprises people.
  • Neighbouring networks are usually the dominant interferer in flats and terraces, and there is no setting that removes them.

An honest limitation: a WiFi analyser app only shows you networks. If the noise floor is raised with no networks visible, the source is something that isn’t WiFi — and proving what needs either a spectrum analyser or the patient business of switching suspects off one at a time.

/04 — FREE TOOLS

The free diagnostic kit we actually use

  • A UK-hosted speed test with a bufferbloat grade — run it wired, not over WiFi.
  • A broadband quality monitor that logs latency and loss over days. Evidence over a week is what gets a line fault taken seriously.
  • Windows: netsh wlan show interfaces for live band, channel and signal; netsh wlan show wlanreport for a full connection history; ipconfig /flushdns and pathping.
  • macOS: hold Option and click the WiFi icon for signal and noise; Wireless Diagnostics for a full scan.
  • The router’s own event log — by far the most under-used tool in home networking. It tells you whether you lost the broadband or lost the WiFi, which is the whole question.
  • A 10 m patch lead. Unglamorous, and it settles more arguments than any app.
  • Our own free tools: the 365 WiFi Optimizer for live signal quality, the broadband speed test, and is it down? to check whether a service is broken for everyone or just you.

/05 — WHEN IT IS THE LINE

When it is the line, not the WiFi

This is the section that costs us work and we are writing it anyway.

If a wired test at the router shows 8 Mbps down and 0.7 Mbps up, no mesh, extender or powerline adapter changes that number. Not a better one. Not a more expensive one. The honest advice is to look at the package, the provider, or whether full fibre has reached your street — not at hardware.

Copper lines and stability management: if a line keeps resyncing, the network automatically makes it more stable and slower — interleaving adds a few milliseconds of latency, and banding typically drops the sync speed by 10–20% to buy reliability. Fix the noise source first, then ask the provider to reset it. Rebooting the router every day because it feels better is the fastest way to a permanently slower line.

Your right to leave, stated accurately: Ofcom’s speed codes of practice let you exit — but only with providers signed up to them, only where speed falls below the minimum guaranteed figure (not the advertised average), and only where the fault is on the provider’s network. In-home WiFi problems do not qualify, and anyone telling you otherwise is setting you up for a disappointing phone call.

FAMILY-RUN SINCE 1995 · ★ 4.9 ON GOOGLE · 200+ COMPUTERS UNDER OUR CARE · NO FIX, NO FEE · SAME-DAY REMOTE SUPPORT

// GOOD QUESTIONS

Frequently asked

Why is my WiFi slow at night but fine in the morning?

Run a wired speed test at 8–10pm. If the wired test is also slow, it is congestion on your provider’s network and no WiFi change will help — log wired tests at fixed times for a week before raising a fault. If the wired test is fine, it is radio congestion from neighbouring networks: set 2.4 GHz manually to channel 1, 6 or 11 at 20 MHz, move 5 GHz to a quieter channel, and consider reducing transmit power.

Why does my 5GHz WiFi drop out for a minute at a time?

Most likely radar detection. UK regulations require equipment on certain 5 GHz channels to stop transmitting within 10 seconds of detecting radar and then avoid that channel for at least 30 minutes. It is not a fault. Confirm it in the router log, then pin 5 GHz to a non-radar channel — especially near airports, ports and the coast, which covers much of Dorset.

My video calls stutter but downloads are fast. Why?

Almost always bufferbloat or a saturated upload rather than a lack of bandwidth. Start a large download and watch your ping: if idle latency of around 15 ms climbs to 250 ms under load, that is the signature. Enable Smart Queue Management on the router with a shaper set slightly below your real line rate, and check whether cloud backup or file sync is quietly using all of your upload.

How do I know if the problem is my WiFi or my broadband?

Plug a laptop into the router with a cable and run a speed test in the same minute as a wireless test. If both are slow, it is the line or the provider. If the wired test is fast and the wireless one is not, it is the WiFi, and then it becomes a question of where in the house and on which band. This one test saves more wasted money than anything else on the page.

Why do my smart plugs and cameras keep disconnecting?

The most common cause is auto-channel selection quietly moving your 2.4 GHz network under devices that do not cope well with it. Pin the 2.4 GHz channel manually — that is the only durable fix in a smart home. Also check the address pool: many ISP hubs only hand out 32 to 64 addresses, and once exhausted devices appear connected but have no internet.

// Still stuck?

Tried all this and it’s still wrong?

That is genuinely what we are for. We diagnose properly rather than guessing, and we will tell you when the problem is your line, your device or your walls rather than selling you a box. No-fix-no-fee, across Bournemouth, Christchurch, Poole and Dorset.

We’ll fix it with you

  • Checking the problem is free
  • Fixes from £20, agreed before we start
  • We phone first, and you watch every step

Stop it happening again

  • A full service every six weeks, written up
  • Every program kept up to date
  • Unlimited remote help when you need it

Plans from £18.25 a month per computer · cancel any time

Mon–Fri 9–5 · family-run since 1995 · rated 4.9 on GoogleMeasure your signal free →