Slow internet on Windows 11 — pages taking too long, streaming buffering, downloads crawling — is one of the most complained-about problems because it affects everything, and the cause can be anywhere from a browser tab to the ISP infrastructure. The right starting point is a speed test on multiple devices. If you want the full context, see our Complete Guide to Fixing Windows, Browser, and Software Errors.
Run fast.com or speedtest.net on the Windows machine and on your phone simultaneously (use mobile data for the phone, not Wi-Fi — or use Wi-Fi on both). If the phone also shows slow speeds: the router or ISP is the bottleneck, not Windows. If the phone is fast and Windows is slow: the problem is Windows-side. This single comparison eliminates half the possible causes instantly.
If Windows is the bottleneck
The most common Windows-side causes of slow internet, in order of likelihood:
- Background applications consuming bandwidth. Task Manager → Performance → Ethernet/Wi-Fi → shows current send/receive speeds. If it’s near the connection’s maximum: something is downloading or uploading. Task Manager → Processes → sort by Network → identify the high-usage process.
- Wi-Fi adapter power saving. Windows limits Wi-Fi performance in power-saving mode. Device Manager → Wi-Fi adapter → Advanced → “Power Save Mode” or “Power Management” → set to Maximum Performance.
- Network adapter driver. Generic drivers from Windows Update often perform worse than manufacturer drivers for throughput and latency.
Background traffic — the quick audit
Windows Update downloads. OneDrive/Dropbox/Google Drive syncing. Windows Defender scanning network shares. Steam or Epic updating games. These all consume bandwidth silently. Task Manager → Processes → Network column → click to sort descending. The top processes show who’s using your bandwidth.
For Windows Update specifically: Settings → Windows Update → Pause updates (pause for 1 week temporarily) → rerun the speed test. If speed improves: Windows Update was the consumer. Let the update finish at a convenient time rather than competing with what you’re doing.
NIC settings for throughput
Device Manager → right-click network adapter → Properties → Advanced tab:
- Speed and Duplex: confirm “Auto Negotiation” — mismatched duplex halves effective throughput
- Receive Buffers / Transmit Buffers: increase to maximum available (512, 1024) — larger buffers reduce packet loss during bursts
- Large Send Offload: keep Enabled — offloads packet segmentation from CPU to NIC hardware
- Receive Side Scaling: enable — distributes network processing across CPU cores
DNS configuration
Slow DNS makes every new connection sluggish — the time before a page even starts loading. The ISP’s default DNS servers are often slower than alternatives. Settings → Network → Ethernet or Wi-Fi → DNS server assignment → Manual → Primary: 1.1.1.1, Secondary: 8.8.8.8. After changing: open a new browser window and try a few sites. Faster initial connection time (not necessarily download speed) confirms DNS was the bottleneck.
For a more thorough DNS comparison: DNS Benchmark (GRC, free) tests 200+ DNS servers from your location and shows actual resolution times. The fastest server for your specific location may not be one of the well-known options.
TCP/IP stack tuning
Windows’ TCP auto-tuning should be enabled for good throughput. Administrator Command Prompt:
netsh int tcp show globalConfirm “Receive Window Auto-Tuning Level” = Normal. If it’s Disabled: run netsh int tcp set global autotuninglevel=normal. Also check “Chimney Offload State” — this moves TCP connection handling to the NIC. On modern NICs: set to Enabled for throughput improvement. On older or problematic NICs: Disabled is sometimes more stable.
VPN slowing everything
A connected VPN routes all traffic through its server, adding latency equal to the round-trip to that server plus encryption overhead. A VPN connected to a server in another country effectively adds 100–300ms of latency to every connection and limits throughput to what the VPN server can sustain. If a VPN is connected: disconnect it and retest. If speed returns to normal: the VPN is the bottleneck. Use split tunneling to route only necessary traffic through the VPN, or accept the speed tradeoff when privacy requires the VPN.
Wi-Fi vs Ethernet
Wi-Fi is inherently slower and more variable than Ethernet due to shared medium, interference, and signal variation. If slow speeds are on Wi-Fi: connecting via Ethernet is the most effective single upgrade, particularly for sustained transfers. Even a gigabit router produces 10–50% lower throughput over Wi-Fi than over Ethernet under typical home conditions.
If Ethernet isn’t available and Wi-Fi speed is the problem: 5 GHz is significantly faster than 2.4 GHz. Ensure the device is connecting to the 5 GHz band (SSIDs often have a “5G” suffix). Also check signal strength — a strong 5 GHz signal at 3 metres outperforms a weak 5 GHz signal at 15 metres.
For the NIC driver and advanced settings that affect throughput more deeply, our Ethernet performance guide covers the full set of adapter settings. For ISP-side issues including the modem signal levels and congestion data that affect ISP-level speed, our network stability guide covers the upstream diagnostics. Microsoft’s Windows 11 network performance documentation covers the Network Performance Monitor and the PowerShell network adapter statistics commands that provide per-interface throughput data for accurate baseline measurement.
Metered connection and throttled updates
Windows behaves differently on metered connections — it defers non-critical updates, reduces background sync, and changes some application behaviours. However, it also sets delivery limits for some features. Settings → Network → your connection → “Set as metered connection” → if you’ve marked the connection as metered to reduce Windows Update downloads, some performance features are also disabled. For maximum network performance on a reliable connection: unmark it as metered.
Peer-to-peer update delivery
Windows Update Delivery Optimization uses peer-to-peer technology — other PCs on the local network or the internet share update files to reduce load on Microsoft’s servers. In the process: Windows can upload data to other machines while you’re using the connection. Settings → Windows Update → Advanced options → Delivery Optimization → “Allow downloads from other PCs” → if you want to limit this, set to “Devices on my local network” rather than “Internet” or disable it entirely. On a constrained connection: this upload traffic is a real speed impact, particularly during active Windows Update periods.
Browser-specific slowness vs system-wide slowness
If internet feels slow in one browser but a speed test shows normal speeds: the slow browser is the problem, not the internet connection. Browser cache bloat, too many open tabs, extensions intercepting requests, or the browser’s connection pool being saturated all cause browser-specific slowness that looks like slow internet. Clear the browser cache, reduce open tabs, test in Incognito mode (extensions off), and confirm whether the slowness is global or browser-specific.
The speed test on the Windows machine plus comparison to another device (from the introduction) immediately confirms whether this is global slowness or browser-specific. If the speed test in the browser shows full speed but browsing feels slow: the issue is page rendering, JavaScript processing, or extension overhead rather than network throughput.
QoS (Quality of Service) configuration
Router QoS settings prioritise specific traffic types or devices. If QoS is enabled on the router and the Windows machine isn’t in a high-priority category: its traffic gets queued behind higher-priority traffic from other devices. Router admin panel → QoS → either add the Windows machine to a higher priority tier, or disable QoS if it’s not providing meaningful benefit. Some router QoS implementations are poorly calibrated and actually reduce performance for all devices due to processing overhead.
ISP throttling
ISPs throttle specific traffic types — video streaming, BitTorrent, gaming traffic — through deep packet inspection. This produces a characteristic pattern: speed tests show full speed, but specific services (Netflix, specific games, specific application types) are significantly slower. The speed test uses HTTP/HTTPS which bypasses most throttling; the throttled traffic uses protocols that the ISP identifies and limits.
Test: a VPN changes the appearance of traffic to the ISP, bypassing protocol-specific throttling. If speed on the throttled service improves significantly while using a VPN: ISP throttling is confirmed. Switching ISP plans (some offer true unlimited traffic without throttling), using a VPN permanently for the affected traffic, or adjusting applications to use connections the ISP doesn’t throttle are the options.
Antivirus real-time network scanning
Security suites that inspect network traffic in real-time add latency to every connection and reduce effective throughput. This overhead is usually small (5–15% reduction) but on slower connections it’s proportionally more significant. Security products like Kaspersky, ESET, and Bitdefender with “Network protection” features perform the most network-level inspection.
Test: temporarily disable the antivirus’s network scanning feature (not the whole antivirus — specifically the network component) → rerun the speed test. If speed improves noticeably: the network scanning overhead is significant. Configure the security software to exclude high-trust local network addresses or specific trusted application traffic from inspection to reduce overhead without eliminating protection.
IPv6 and connection negotiation
Windows 11 prefers IPv6 connections where available. ISPs with partial IPv6 support — where IPv6 addresses are assigned but routing is unreliable — cause connection timeouts as Windows attempts IPv6 first, waits for the timeout, then falls back to IPv4. Every new connection has this delay, making browsing feel sluggish even though throughput is fine once a connection is established.
Test: Settings → Network → Ethernet or Wi-Fi → your connection → IPv6 → disable. Restart → test browsing speed. If page load times improve noticeably: ISP IPv6 was unreliable and causing connection fallback delays. Disabling IPv6 forces all connections to IPv4 immediately without the timeout.
Hard drive bottleneck and download speeds
Downloaded files write to the hard drive. If the download drive is an HDD (not SSD) at near capacity or with fragmentation: write speed limits download speed regardless of internet throughput. A download that appears to “max out” at 50 MB/s when the internet connection should support 200 MB/s may simply be hitting the HDD’s write speed ceiling.
Check download target drive: Task Manager → Performance → Disk → compare write speed during active downloads to the drive’s rated speed. If the disk write speed is the ceiling: changing the download destination to an SSD, or defragmenting and clearing space on the HDD, increases effective download speed without changing the network configuration.
Router and modem performance over time
Home routers and cable modems accumulate state over uptime — NAT tables fill, connection tracking tables grow, firmware memory leaks accumulate. Routers that haven’t been restarted in months can show 50–60% lower throughput than after a fresh restart. This affects all connected devices equally, which is why it appears in the “router is the bottleneck” category but specifically affects machines that are always connected — the machine appears slow while others seem fine because other devices restarted more recently and got fresh connections.
Router restart: unplug for 60 seconds → plug in. Rerun the speed test on the Windows machine immediately after restart. If speed returns to expected levels: router state accumulation was the bottleneck. Schedule monthly router restarts as maintenance if this recurs — most modern routers support scheduled restart in their admin panel.
One pattern that’s worth knowing: if slow internet appeared the same day a new application was installed — particularly a security suite, a VPN client, or a peer-to-peer application — the new application is almost certainly the cause. These application types all interact heavily with the network stack and commonly reduce performance on installation. Uninstalling or disabling the application and testing immediately confirms or eliminates it as the cause in under 5 minutes.
Speed baseline and what “normal” is
Understanding what speed you should actually be getting is important before concluding something is wrong. ISP “up to” speed figures are theoretical maximums under ideal conditions. Typical achievable speeds: 70–90% of advertised for fiber over Ethernet, 50–80% for cable over Ethernet, 50–70% for Wi-Fi on 5 GHz, 30–50% for 2.4 GHz Wi-Fi. If measured speeds fall within these ranges: the connection is performing normally for the technology type. Only speeds significantly below these ranges indicate a problem worth investigating.
Time of day also matters for cable internet — peak hours (evenings, weekends) see 20–40% lower speeds due to shared infrastructure congestion. Testing at multiple times of day provides a realistic picture of actual typical performance rather than a single data point that may or may not represent typical conditions.
The network reset as a last resort: Settings → Network and internet → Advanced network settings → Network reset → Reset now. This removes and reinstalls all network adapters, resets all settings to defaults, and requires reconfiguring Wi-Fi passwords, static IPs, and VPN configurations. It’s disruptive but definitively resolves accumulated network stack corruption that specific settings changes don’t address. Use this only after the targeted fixes haven’t resolved persistent slow speeds — it’s effective but it’s the sledgehammer, not the scalpel. Related: Internet Connection Keeps Dropping.
