Quick Answer
Wi‑Fi can be fast on one device and slow on another because devices differ in wireless standards (Wi‑Fi 4/5/6/6E/7), antenna design, number of spatial streams, and how they choose bands and channels. Distance, walls, and interference matter too, as do router settings (band steering, channel width, QoS), background apps, power saving, VPNs, and outdated drivers or firmware. A phone hanging onto 2.4 GHz two rooms away will be much slower than a laptop on 5 or 6 GHz near the router. Matching each device to the best band, updating software, tuning router settings, and reducing interference usually closes the gap.
Why One Device Gets Fast Wi‑Fi While Another Crawls
Different Wi‑Fi Standards and Radio Capabilities
Devices “speak” Wi‑Fi differently. Older clients may only support 802.11n (Wi‑Fi 4), while newer ones use 802.11ac (Wi‑Fi 5), 802.11ax (Wi‑Fi 6/6E), or Wi‑Fi 7. A 1×1 radio (one spatial stream) negotiates much lower link rates than a 2×2 or 3×3 client on the same access point (AP). Two devices side by side can show very different negotiated link speeds (PHY rates); those link speeds cap real throughput even under ideal conditions.
2.4 GHz vs 5 GHz vs 6 GHz
Each band trades range for capacity. 2.4 GHz travels farther and penetrates walls better but offers limited clean spectrum and suffers heavy interference. 5 GHz provides higher throughput and more non‑overlapping channels but has shorter reach. 6 GHz (Wi‑Fi 6E/7) is very fast and less congested, yet has the shortest range and requires compatible clients. If your slow device is on 2.4 GHz while the fast one is on 5/6 GHz, the difference will be obvious.
Antenna Design and Device Size
Laptops often include multiple, well‑spaced antennas for spatial diversity and 2×2 or 3×3 MIMO. Phones and budget tablets may be 1×1 with compact antennas that detune easily. Even hand placement can alter signal strength and throughput by changing how the antenna couples to your surroundings.
Interference and Congestion
2.4 GHz is crowded: neighboring Wi‑Fi, microwaves, baby monitors, older cordless phones, Bluetooth, and even poorly shielded USB 3.0 devices can create noise. On 5 GHz, radar events on DFS channels can force a channel change or reduced performance. A device near a noisy appliance or contending with overlapping networks will slow down while another in a cleaner spot runs fine.
Router Settings and Airtime Sharing
Mixed modes, aggressive channel widths, and “smart” features can affect clients unevenly. Slow or distant clients use more airtime to transfer the same data, dragging down everyone unless airtime fairness prioritizes faster stations. Band steering can misplace a client on 2.4 GHz. Per‑device QoS, parental controls, or bandwidth limits can throttle a single MAC address—sometimes unintentionally, especially with randomized MACs.
Software, Drivers, and Power Policies
Old Wi‑Fi drivers or OS bugs can cause poor roaming, low link rates, or random disconnects. Battery saver and Wi‑Fi power save modes slow radios to preserve energy. VPNs, ad blockers, firewalls, and security suites add CPU and encryption overhead and can route traffic through congested servers. Background updates, cloud sync, and photo/video backups quietly consume bandwidth and skew tests.
Physical Placement and Obstacles
Concrete, brick, metal, mirrors, thick doors, and aquariums attenuate signals. 5/6 GHz attenuates faster with distance and obstacles than 2.4 GHz. A device two rooms away at −75 dBm will negotiate much lower MCS rates and link speeds than another at −50 dBm near the AP.
How Wi‑Fi Standards and Bands Impact Real Speeds
| Wi‑Fi Standard | Typical Client Streams | Common Bands | Typical Max Link Rate (2×2) | Notes |
|---|---|---|---|---|
| Wi‑Fi 4 (802.11n) | 1×1–2×2 | 2.4/5 GHz | Up to ~300 Mbps | Often limited to 2.4 GHz on older gear; 40 MHz is rare on 2.4 GHz due to coexistence rules. |
| Wi‑Fi 5 (802.11ac) | 1×1–3×3 | 5 GHz | Up to ~867 Mbps (80 MHz) | Many phones are 1×1 (433 Mbps link). Real throughput is typically 50–70% of the link rate. |
| Wi‑Fi 6 (802.11ax) | 1×1–4×4 | 2.4/5 GHz | Up to ~1200 Mbps (80 MHz, 2×2) | OFDMA boosts efficiency with many clients; benefits depend on AP and client support. |
| Wi‑Fi 6E (802.11ax in 6 GHz) | 1×1–2×2 (typical) | 6 GHz | Up to ~2400 Mbps (160 MHz, 2×2) | Very clean spectrum but shorter range; visible only to 6E‑capable clients. |
| Wi‑Fi 7 (802.11be) | 1×1–4×4 (emerging) | 2.4/5/6 GHz | Higher with 320 MHz & MLO | Multi‑Link Operation can combine bands; real‑world gains vary by AP and client. |
Band Characteristics at a Glance
| Band | Range | Throughput | Interference | Best For |
|---|---|---|---|---|
| 2.4 GHz | Long | Low–Moderate | High (crowded, non‑Wi‑Fi devices) | IoT, long distance, basic browsing, smart home gadgets |
| 5 GHz | Medium | High | Moderate (more channels) | Streaming, gaming, video calls at near/medium range |
| 6 GHz | Short | Very High | Low (clean spectrum) | High‑bitrate transfers, low‑latency tasks near the AP |
Check Whether the Internet or Wi‑Fi Is the Bottleneck
A slow device may be limited by your internet connection, not by Wi‑Fi. Check both paths:
- Run a speed test on a wired computer connected directly to the router. If that’s slow too, the ISP, modem, or WAN link is the issue.
- Measure local Wi‑Fi performance. If the Wi‑Fi link speed is high but internet tests are slow, the bottleneck is upstream. If the link speed is low, optimize the Wi‑Fi connection.
How to Diagnose: Step‑by‑Step
1) Compare Link Speed, RSSI, and Band
- Windows: Settings > Network & Internet > Wi‑Fi > Hardware properties for Link speed and Protocol; or run “netsh wlan show interfaces”.
- macOS: Hold Option and click the Wi‑Fi icon to see RSSI, Tx Rate (link speed), PHY Mode, and Channel (band/width).
- Android: Settings > Network & Internet (or Connections) > Wi‑Fi > your network > Link speed/Frequency.
- iOS/iPadOS: The system UI hides link speed; use your router’s client list to see the band and link rate, or enable the AirPort Utility Wi‑Fi Scanner.
If the slow device shows 2.4 GHz or a low Tx Rate while the fast one shows 5/6 GHz with a high rate, you’ve found the cause.
2) Test Near the Router
Move the slow device next to the router and retest. If speeds jump, distance or obstacles were the problem. If not, focus on software, drivers, or router policies affecting that device.
3) Eliminate Background Load
- Pause cloud backups, OS updates, and app downloads.
- Check Task Manager/Activity Monitor for bandwidth‑heavy processes.
- Temporarily disable VPNs, proxies, or security filters and test again.
4) Use Local Speed Tests
To isolate Wi‑Fi from the internet, test within your LAN:
- Copy a large file from a NAS or another PC and note the transfer rate.
- Advanced: run iperf3 between two LAN devices; the slowest hop reveals the bottleneck.
5) Inspect Router and AP Settings
- Open the router’s client list to confirm band, channel width, link rate, and RSSI per device.
- Look for per‑device QoS, parental controls, or bandwidth caps.
- Review band steering, Smart Connect, and airtime fairness behavior for that client.
Fixes That Work
On the Slow Device
- Forget and rejoin the network; connect to the 5 GHz or 6 GHz SSID when available. If bands share one SSID, temporarily split them to force 5/6 GHz.
- Update the OS and Wi‑Fi drivers/firmware. On Windows, use Device Manager > Network adapters; on Macs and phones, apply the latest system updates.
- Disable battery saver and Wi‑Fi power save. On laptops, set the wireless adapter power setting to Maximum Performance.
- Turn off VPNs and traffic‑filtering apps while testing. Some mobile VPNs cap throughput or add latency.
- Work around buggy drivers: if you see issues on Wi‑Fi 6/6E, try locking the client to Wi‑Fi 5; or re‑enable 6/6E after updating drivers.
- Reduce 2.4 GHz interference: temporarily turn off Bluetooth during large transfers, and keep USB 3.0 hubs and drives away from 2.4 GHz adapters.
- As a last resort, reset network settings (you’ll need to reenter Wi‑Fi passwords).
On the Router or Access Point
- Update firmware. Vendors routinely fix band steering, DFS, and client compatibility bugs.
- Split SSIDs by band (e.g., “Home‑24”, “Home‑5”, “Home‑6E”). This prevents sticky 2.4 GHz associations and lets you pick the best band per device.
- Pick clean channels:
- 2.4 GHz: use channels 1, 6, or 11 only; prefer 20 MHz width (avoid 40 MHz in busy areas).
- 5 GHz: favor 80 MHz on clear channels; if DFS triggers drops, try non‑DFS channels (36–48, 149–165) or step down to 40 MHz in dense apartments.
- 6 GHz: use 80–160 MHz where supported; prefer PSC channels for faster discovery and better client compatibility.
- Security mode: use WPA2‑AES or WPA3‑SAE. Avoid TKIP and WEP; mixed WPA2/WPA3 can slow certain clients—test a pure mode if supported.
- Keep WMM enabled. Disabling WMM forces legacy rates and slashes throughput; apply QoS only if you need to shape traffic.
- Review airtime fairness and band steering. If a device is starved or keeps bouncing between bands, disable or tune these features.
- Disable legacy 802.11b rates and long preamble if you have no ancient clients to reduce airtime overhead.
- Check for per‑device limits. Remove rate caps or schedules that might throttle one device; remember randomized MACs can bypass or misapply rules.
- Reposition the AP high and central, away from metal, mirrors, and thick masonry. Aim for line‑of‑sight for 6 GHz clients.
Reduce Contention and Interference
- Keep USB 3.0 disks/docks away from 2.4 GHz adapters and the router.
- Don’t share channels with microwaves or baby monitors; use 5/6 GHz for critical devices if those appliances are nearby.
- When neighbors are dense, reduce channel width; narrower channels can improve stability and net throughput by lowering retries.
Improve Coverage
- Add a mesh node or wired access point where speeds fall off. One powerful router at one end of the house won’t beat a well‑placed secondary AP.
- Use Ethernet backhaul for mesh when possible; wireless backhaul consumes airtime that could serve clients.
Edge Cases That Cause Per‑Device Slowness
- Sticky roaming: a client clings to a distant AP at low rates. Configure minimum RSSI, minimum data rates, or separate SSIDs to encourage a roam.
- DFS hopping: some clients underperform or drop on DFS channels after radar events. Try a stable non‑DFS channel.
- Driver quirks with WPA3 or 160 MHz: certain chipsets run slower unless you switch to WPA2‑AES or 80 MHz.
- Private/Randomized MAC: rules tied to the old MAC won’t apply; speeds or limits may differ unexpectedly.
- IoT devices: many are 2.4 GHz‑only and stick to 20 MHz; isolating them on a separate SSID can protect high‑throughput devices from airtime hogging.
When to Replace Hardware
If a client only supports Wi‑Fi 4 or a single 2.4 GHz stream, it will never match modern speeds. A USB or internal Wi‑Fi 6 adapter is an inexpensive PC upgrade. On the network side, older routers without OFDMA or with weak CPUs struggle with many clients, buffer heavily, and apply QoS poorly. If firmware updates don’t stabilize performance and you want strong 5/6 GHz coverage through several rooms, consider a Wi‑Fi 6 or 6E mesh with Ethernet backhaul.
A Short Checklist
- Confirm the slow device’s band, link rate, and RSSI.
- Move closer and retest to separate signal issues from software issues.
- Update device drivers/OS and router firmware.
- Split SSIDs or force the device onto 5/6 GHz.
- Pick clean channels and sensible channel widths for your environment.
- Disable VPNs/power saving and stop background traffic while testing.
- Use mesh or an extra AP to fix dead zones.
Frequently Asked Questions
Why is my phone slow on Wi‑Fi while my laptop is fast?
Phones often have 1×1 radios with fewer antennas, connect more readily to 2.4 GHz, and use aggressive power saving. Laptops typically support 2×2 at 5 or 6 GHz with higher link rates and better antennas. Check the phone’s band and link speed; forcing 5 GHz and disabling battery saver usually helps.
Can a single slow device reduce speeds for everyone?
Yes. Legacy or distant clients transmit at low data rates and consume more airtime, leaving less for others. Airtime fairness and minimum data rate controls help, but you’ll get the best result by improving that client’s signal or moving it to a less busy band.
Is 2.4 GHz ever the right choice?
Yes. For long range, multiple walls, or IoT devices with weak radios, 2.4 GHz is more reliable. For high‑throughput tasks like 4K streaming, cloud backups, or large downloads on modern devices, 5 or 6 GHz delivers better results when signal is strong.
How do I know if my VPN is causing the slowdown?
Run back‑to‑back speed tests with the VPN on and off. If throughput improves markedly or latency drops with the VPN disabled, the VPN server path or encryption overhead is the bottleneck. Some mobile VPNs cap speeds due to server load or protocol limits.
Should I enable 160 MHz channels?
Only if you have compatible clients, a clean RF environment, and minimal DFS interruptions. 160 MHz can deliver very high link rates on 5/6 GHz, but it’s more sensitive to interference and may be unstable in dense neighborhoods. Often, 80 MHz provides higher, more consistent real‑world throughput.
Why does my device keep connecting to the slower 2.4 GHz band?
Devices often prioritize signal strength over capacity, and band steering isn’t perfect. If the 2.4 GHz RSSI is higher, the client may choose it. Split SSIDs by band and connect to the 5 or 6 GHz SSID, or adjust band steering settings on your router if available.
Do mixed WPA2/WPA3 or older security modes affect speed?
They can. Mixed modes sometimes trigger compatibility fallbacks and extra overhead. Sticking to WPA2‑AES only (no TKIP) or WPA3‑SAE only—when all clients support it—can improve stability and throughput.
