What should I check first for slow broadband?

Start by validating the scope of the issue: check whether it affects one device, one room or the whole connection, then compare Wi‑Fi and Ethernet where possible.

Can Wi‑Fi cause slow broadband?

Yes. Weak Wi‑Fi, interference, router placement and device limitations can cause many broadband symptoms even when the line itself is working.

When should I contact my provider?

Contact your provider if the problem affects Ethernet as well as Wi‑Fi, router or ONT lights show a service fault, or repeated tests prove the issue is outside your home network.

Why Is My Broadband Slow? Validate Wi‑Fi, Router and Line Causes

Slow broadband guide

Why Is My Broadband Slow?

This guide helps you validate whether slow broadband is caused by Wi‑Fi, router load, package limits, evening congestion or a provider fault.

Run speed test Broadband issue hub

Home router with some devices showing strong connection and others showing slow broadband warning indicators

Issue

Symptoms of Slow Broadband

Use these signs to confirm that slow broadband is the closest matching issue before changing settings, replacing equipment or contacting your provider.

Pages and apps feel slow across several devices: DNS resolution failures can make a healthy broadband line feel sluggish. If your ISP's default DNS servers are congested or failing, web pages may hang before loading because your router is struggling to translate web addresses into IP numbers.
Downloads are far below expected package speed: On FTTC lines, copper cross-talk can reduce sync speed as nearby usage rises. Also check whether an app is showing megabytes per second (MB/s) rather than megabits per second (Mbps): a 100Mbps line downloads files at roughly 12MB/s.
Streaming quality drops or buffers: Streaming platforms rely on Content Delivery Networks. If your provider has limited peering capacity to a busy CDN during live events or peak hours, Netflix, YouTube or BBC iPlayer can buffer even when a generic speed test looks healthy.
Upload tasks make browsing and calls worse: Many home broadband lines are heavily asymmetric. When a backup, camera or cloud sync fills the narrow upload pipe, downloads can stall because acknowledgement packets cannot leave your home quickly enough.
Ethernet and Wi‑Fi results differ sharply: Older routers, laptops and TVs may use Fast Ethernet ports capped at 100Mbps, while a modern Wi‑Fi 6 phone beside the router can test much faster. This can make Ethernet look unexpectedly slower than wireless on faster full-fibre packages.

Likely causes

Most Common Causes

The same slow-broadband symptom can come from Wi‑Fi, the package itself, router load, provider capacity or the device you are testing with. Use the validation steps to prove which cause fits your home.

Wi‑Fi bottleneck

MIMO stream depletion: Many phones, laptops and tablets only have a 2×2 antenna layout. Behind thick walls or at long range, they cannot use enough spatial streams to reach full package speed.

Legacy device drag: Older Wi‑Fi 4 devices take longer to transmit data. Because Wi‑Fi airtime is shared, one slow legacy device can reduce performance for faster devices on the same band.

5GHz and 6GHz attenuation: Faster wireless bands offer high throughput but struggle through brick walls, foil-backed insulation and metal objects, often pushing devices back onto slower 2.4GHz Wi‑Fi.

Package or line limit

Copper cross-talk and REIN: FTTC lines can slow down when neighbouring copper pairs create electrical interference, or when faulty appliances and street equipment inject noise into the line.

Profile capping: Dynamic Line Management can reduce speed or increase interleaving after repeated drops, storms or frequent manual router reboots.

Per-device bandwidth starvation: On modest packages, one 4K HDR stream or game update can consume most of the available headroom and make every other device feel slow.

Router congestion

NAT table limits: Every app, stream and smart-home device needs a tracking entry inside the router. Older hubs can run out of capacity, making new web pages and apps respond slowly.

Asymmetric buffer choking: When uploads saturate the narrow upstream pipe, outgoing acknowledgement packets are delayed and downloads can collapse even though the download side of the line is much larger.

Hardware acceleration disabled: Parental controls, device limits or traffic monitoring can force a router to process packets on its main CPU instead of its acceleration chip, sharply reducing top speed.

Peak-time congestion

Over-subscribed SVLANs: If your ISP has not bought enough capacity in your exchange area, speeds can fall in the evening even when your own router and Wi‑Fi are fine.

CDN and peering saturation: Major live events, streaming peaks or game launches can overload provider links to content networks, so one app buffers while a local speed test still looks normal.

Device limits

Fast Ethernet restrictions: Older TVs, budget laptops and legacy router ports may be limited to 100Mbps, capping real-world tests at around 90–95Mbps.

CPU and bus limitations: Older tablets and low-end laptops can lack the processing power needed to handle encrypted modern web traffic at high speed.

Browser rendering bottlenecks: Web speed tests use complex JavaScript. A slow computer, overloaded browser or too many extensions can show a low result that is caused by the device, not the broadband line.

Validate

Steps to Narrow Down the Root Cause of the Issue

Work through these checks in order. Change one thing at a time so the result isolates whether the slowdown is local Wi‑Fi, device hardware, router load, provider capacity or the physical line.

1
Run a LinkSpeed test near the router. This checks local wireless throughput close to the hub. Then log into the router admin page and compare the result with the broadband sync speed or line rate. If sync speed is high but device speed is low, the fault is inside the home.
2
Repeat over Ethernet if possible. A wired test removes Wi‑Fi from the equation. Check the network link speed too: if it reads 100/100Mbps, you may be using a legacy port, damaged cable or older network card. Full-fibre testing normally needs a 1000/1000Mbps or 1Gbps link.
3
Compare download, upload, ping and jitter rather than download alone. Near-zero upload points to asymmetric buffer choking. Good download with high ping or unstable jitter suggests transit delay, congestion or DNS problems rather than a simple speed shortage.
4
Pause heavy downloads and uploads, then retest. Stop cloud backups, console updates, streams and phone photo syncs. If speed recovers immediately, household usage and router congestion are maxing out the package rather than a provider fault.
5
Test at different times of day. Compare morning and evening results. If speeds are fine at 9:00 AM but poor at 9:00 PM, peak-time congestion is likely. On FTTC, matching evening jumps in ping and jitter can also suggest REIN electrical noise.
6
Compare one device with another. Test a modern phone and an older laptop in the same location. If one hits full speed and the other crawls, the broadband line is not the bottleneck; the slower device, browser, adapter or CPU is.

Fix

Problem Resolution

Apply the fix that matches the cause you validated. If the issue is outside your home network, collect wired test evidence before contacting your provider.

Improve Wi‑Fi or use Ethernet

Target cause: Wi‑Fi bottleneck, MIMO stream limits and 5GHz or 6GHz wall attenuation.

Why it works: A wired connection or better wireless setup removes local radio limits so you can use the speed entering the property.

Critical step: If Ethernet is capped at 90–95Mbps on a faster package, swap old cables for certified Cat6 and check that the router port is not in Green or Eco Mode. For Wi‑Fi, set a clear 5GHz channel width such as 80MHz or 160MHz if your router and devices support it.

Control uploads

Target cause: Upload saturation, asymmetric line collapse and blocked acknowledgement packets.

Why it works: Restricting upstream traffic keeps the return path clear so downloads, browsing and calls remain responsive.

Critical step: Limit or schedule uploads from security cameras, iCloud, Google Drive, OneDrive and similar services. You can also set custom DNS servers such as Cloudflare 1.1.1.1 / 1.0.0.1 or Google 8.8.8.8 / 8.8.4.4 to bypass slow provider DNS resolution.

Restart or replace weak hardware

Target cause: Router congestion, NAT table overflow and hardware acceleration being disabled.

Why it works: Power-cycling and firmware updates clear bloated memory caches, while stronger hardware can handle more devices and faster packages.

Critical step: Disable non-essential processing features such as deep parental controls, built-in device speed limits or complex traffic monitoring if they disable hardware acceleration. Homes with 20–30+ smart devices may need a stronger router or mesh system with at least a quad-core processor and 512MB of RAM.

Contact provider with evidence

Target cause: Package limits, DLM profile capping, low sync speed and peak-time provider congestion.

Why it works: Wired, timestamped evidence removes Wi‑Fi from the conversation and gives your ISP something concrete to escalate.

Critical step: If DLM has capped the line after drops or repeated reboots, do not keep restarting the router. Leave it stable for 14 days so automated line tests can clear the cap. For persistent faults, disconnect Wi‑Fi devices, run three wired tests over 24 hours, and screenshot the router sync speed. If sync speed is below your Minimum Guaranteed Speed, ask the provider to log an engineering fault.

Next guides

Related broadband troubleshooting guides

If this page does not exactly match the issue, use one of these related guides from the broadband issue hub.