What should I check first for one device slow internet?

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 one device slow internet?

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 Internet Slow on One Device? Validate Device and Wi‑Fi Causes

One device troubleshooting guide

Why Is Internet Slow on One Device?

This guide helps you validate whether one slow device has a local device problem, weak Wi‑Fi, old hardware, software issues or a router compatibility problem.

Run speed test Broadband issue hub

One device slow internet troubleshooting illustration comparing phone laptop and router

Issue

Symptoms of One Device Slow Internet

Use these signs to confirm that the fault is isolated to one device before changing router settings, switching provider or replacing broadband hardware.

One phone, laptop, TV or console is much slower than the rest: the device may be busy with hidden background telemetry, operating system updates, iCloud, OneDrive, Google Photos sync, or game launcher downloads such as Steam or Epic Games. These tasks can silently consume the device's own network adapter capacity while every other household device remains fast.
Other devices work normally on the same broadband connection: this points away from the broadband line and towards a local device fault such as DNS cache corruption. A scrambled DNS cache can make one computer or phone hang while translating website names, even when the raw connection is healthy.
The slow device is worse in one room or on Wi‑Fi only: the router may be applying dynamic modulation capping to that device earlier than it does to stronger devices. A lower-tier wireless chip or loose internal antenna can force the connection onto slower, more robust Wi‑Fi modes room by room.
The issue started after an update, app install or network change: a VPN, third-party firewall, web shield or anti-malware tool may now be intercepting and scanning every packet. If that software deadlocks after an update, it can choke internet speed entirely at the device software layer.
The device struggles with streaming, downloads or video calls while others do not: the device may lack hardware decoding support for modern video formats such as AV1 or VP9. Its CPU then has to decode streams in software, causing dropped frames, buffering and call problems that look like slow internet.

Likely causes

Most Common Causes

When one device is slow but the rest of the home is fine, the cause is usually inside that device, its local Wi‑Fi path, its software stack or its hardware limits.

Weak device Wi‑Fi

Antenna array and form factor limits: budget smart TVs, streaming sticks and small devices often use basic 1×1 MIMO Wi‑Fi, so they cannot use the same parallel data streams as a modern phone.

Chassis RF absorption: consoles and televisions contain metal shielding, disk drives and power circuitry that can absorb or deflect radio waves before they reach the internal Wi‑Fi card.

Co-channel contention vulnerability: weaker adapters struggle to filter neighbouring router noise, so they pause more often while waiting for clean airtime.

Software or browser issue

Extension script deadlocks: ad blockers, privacy tools or corrupted browser extensions can get stuck processing modern web scripts, pinning a CPU core and making a fast connection feel frozen.

Security suite packet inspection: anti-malware, firewall and web shield tools deep-scan traffic before it reaches the device, which can create a local bottleneck after updates or conflicts.

VPN tunnel and MTU mismatches: VPN software can add encryption overhead, poor routing and packet fragmentation if the MTU is set incorrectly.

Poor location

Static dead-zone locking: fixed devices such as TVs, desktop PCs and consoles can sit permanently in a Wi‑Fi dead zone or phase cancellation point.

Electronic near-field noise: microwaves, baby monitors, cordless phone bases and unshielded power bricks can corrupt packets close to the device's network card.

Dense structural barriers: brick, concrete floors and foil-backed insulation can block high-frequency 5GHz Wi‑Fi and force the device onto slower 2.4GHz.

Old hardware

Legacy Wi‑Fi protocol caps: older Wi‑Fi 4 devices lack modern modulation and wide channel support, creating a hard speed ceiling regardless of broadband package speed.

CPU decoding throttling: older processors may not decode AV1, VP9 or complex modern web content quickly enough, making video and web pages look network-limited.

System bus constraints: mechanical drives, slow storage and old motherboard designs can choke during large downloads even when the network card receives data quickly.

Network settings

DNS and IP cache corruption: a damaged local DNS or routing cache can make one device pause while resolving websites after an update, crash or network change.

Aggressive power-saving modes: laptops and tablets can reduce voltage to the network card to save battery, lowering antenna sensitivity and link speed.

Stuck profiles and proxy loops: old VPN adapters, ghost proxy settings or orphan network profiles can route traffic through broken internal paths.

Validate

Steps to Narrow Down the Root Cause of the Issue

Work through these checks in order. Test the slow device against a known-good device so you can prove whether the fault is device, room, Wi‑Fi, software or hardware related.

1
Run a speed test on the slow device and a known-good device in the same place.
What it establishes: immediate environmental bandwidth delivery versus individual client hardware degradation.
Diagnostic logic: if a modern phone hits full speed in the same spot while the slow device crawls, the broadband line and router are innocent and the bottleneck is inside the slow device.
Critical missing detail: use the same test method on both devices, preferably a native speed test app rather than different browsers, so browser engines and extensions do not skew the result.
2
Move the slow device close to the router and retest.
What it isolates: room-by-room range limits and wall attenuation versus a fixed device configuration fault.
Diagnostic logic: if speed recovers within a clear two-metre line of sight of the router, the cause is poor location or weak device Wi‑Fi.
Critical missing detail: if speeds stay slow beside the router, the device may have a broken network profile, software bottleneck, or even a loose internal antenna connection.
3
Use Ethernet if the device supports it.
What it isolates: the device's wireless card and antenna array versus its operating system and processor.
Diagnostic logic: if the device works correctly on Ethernet, the issue is weak Wi‑Fi or local radio interference rather than the main broadband line.
Critical missing detail: check wired link speed. A reading of exactly 100/100 Mbps means a legacy Fast Ethernet port, damaged cable or old network card is restricting the test. Modern full-fibre testing needs a 1000/1000 Mbps or 1Gbps link.
4
Restart the device and forget/reconnect to Wi‑Fi.
What it isolates: corrupted network handshake caches versus structural hardware degradation.
Diagnostic logic: a reboot flushes temporary memory, while forgetting the Wi‑Fi network deletes the saved wireless profile and forces a fresh connection handshake.
Critical missing detail: use a hard restart where possible. On Windows, hold Shift while choosing Shut Down. For smart TVs, unplug from the wall for 60 seconds to clear standby memory and bloated DNS/IP caches.
5
Disable VPN/proxy/security extensions temporarily for testing.
What it isolates: software-layer packet inspection bottlenecks versus raw network carriage.
Diagnostic logic: disabling encryption layers, virtual adapters and web shields lets packets reach the network card without extra processing.
Critical missing step: in a browser, test in an Incognito or Private window with all extensions manually disabled. If speed recovers there, a corrupted ad blocker or privacy extension is probably maxing out the device CPU.
6
Check updates and storage/performance on the device.
What it isolates: system resource starvation versus an active network fault.
Diagnostic logic: Task Manager on Windows or Activity Monitor on Mac can show whether CPU, memory or storage is overwhelmed while the connection is being tested.
Critical missing detail: if CPU usage hits 100% during a speed test or video stream, the internet may not be slow at all. The device may be hitting a hardware limit while decoding modern web scripts or video formats such as AV1 and VP9.

Fix

Problem Resolution

Apply the fix that matches the cause you validated. If every other device is fast, treat this as a local device problem before changing broadband packages or blaming the provider.

Fix the local device first

Target cause: software or browser issues, network settings conflicts, and DNS/IP cache corruption.

Why it works: cleaning the operating system's network parameters removes packet-processing deadlocks so data can reach the network card without software delays.

Critical missing step: on Windows 11, open Command Prompt as Administrator and run netsh int ip reset, then ipconfig /flushdns. On Mac or iOS, test with Private Relay or Limit IP Address Tracking disabled, as these proxy-style protections can halve speeds on a healthy home network.

Improve the device connection

Target cause: weak device Wi‑Fi, poor location boundaries, and electronic near-field noise.

Why it works: improving the physical path or bypassing a weak wireless chip reduces over-the-air transmission failures.

Critical missing step: if the device is fixed in place, disable Smart Connect or band steering in the router admin page and split 2.4GHz and 5GHz into separate names. Lock the slow device to 5GHz where signal allows, or use a high-gain USB Wi‑Fi adapter with an external antenna.

Separate device from broadband diagnosis

Target cause: confounding variables and misinterpreting isolated device metrics.

Why it works: proving the issue is isolated prevents an unnecessary broadband upgrade or provider switch that will not fix a device-side fault.

Critical missing step: stop changing router settings or escalating to the ISP if other devices hit full package speed in the same room. Providers can usually only validate delivery to the master socket, ONT or router gateway, not repair a single device's software or hardware limit.

Replace or upgrade old hardware

Target cause: old hardware limitations, legacy Wi‑Fi caps, and CPU decoding throttling.

Why it works: modern adapters and processors can handle current Wi‑Fi standards, encrypted web pages and compressed video streams more efficiently.

Critical missing step: if Task Manager shows the CPU hitting 100% during tests, the computer has reached a hardware wall. For old laptops, consider an SSD and memory upgrade. For older smart TVs, use an external Apple TV 4K, Google TV Streamer or Roku 4K stick instead of replacing the whole television.