VPN Slowing Down Your Internet? 9 Causes and Fixes

The 60-Second Diagnosis

Most VPN slowdowns come down to one of three things: you are connected to a distant or overloaded server, you are using the wrong protocol, or your packets are getting fragmented due to MTU mismatch. Run a Speed Test with the VPN disconnected, then again connected, and note the percentage drop. A well-configured VPN on a modern connection should cost you no more than 10-15% of your base speed. If you are losing more, one of the nine causes below is responsible.

How Much Speed Loss Is Normal?

All VPNs add some overhead: encryption, tunnel encapsulation, and the extra routing hop all take time. But the range between a good setup and a poor one is wide.

Independent testing by CNET in 2025 found that top-tier paid VPNs averaged 3-18% speed loss. Losses above 30-40% point to a specific, fixable problem.

Cause 1: You Are Connected to a Distant Server

The single biggest factor in VPN speed is physical distance between you and the VPN server. Data travels at roughly the speed of light through fiber, but every extra mile adds measurable latency. A nearby server in your own country might add 5-10 ms. A server on the other side of the world can add 150-200 ms or more, which degrades page loads, video calls, and gaming.

Test: Use our Ping Tool to measure round-trip latency to your VPN server's IP address. Anything above 80-100 ms to the VPN server itself will noticeably affect interactive traffic.

Fix: Connect to the geographically closest server when speed is the priority. Most VPN apps have an "Optimal" or "Fastest Server" option. Only use distant servers when you specifically need an IP from that country for geo-restricted content.

Cause 2: The VPN Server Is Overloaded

VPN servers share bandwidth among hundreds or thousands of simultaneous users. A congested server degrades everyone's speed regardless of geographic distance.

Signs: consistent slowdowns at specific times of day, especially evenings and weekends. The VPN connects successfully but speeds are poor no matter which server location you pick.

Test: Check the server load percentage in your VPN app. Most clients display this. Run a Speed Test connected versus a different server in the same region and compare.

Fix: Switch to a less popular server below 50% load. Connecting to a different city in the same country often gives a similar geographic IP with much less congestion. Connecting during off-peak hours for your target region also helps.

Cause 3: You Are Using the Wrong Protocol

VPN protocols have dramatically different speed characteristics. WireGuard consistently outperforms OpenVPN by a large margin in real-world benchmarks. In 2025-2026 testing, WireGuard reached 940-960 Mbps on a 1 Gbps connection versus OpenVPN's approximately 480 Mbps. WireGuard achieves this by running in kernel space, eliminating the packet-copying overhead that slows down user-space implementations like OpenVPN.

If your app defaults to OpenVPN TCP, you may be giving up 20-30% of your speed for no security benefit.

Test: Open your VPN app settings, check which protocol is active, run a Speed Test, then switch to WireGuard and retest.

Fix: Switch to WireGuard. If it is unavailable, try OpenVPN UDP before OpenVPN TCP. IKEv2 is also a strong option, particularly on mobile devices. See VPN Protocols Compared: WireGuard vs OpenVPN vs IKEv2 for a full breakdown.

Cause 4: MTU Mismatch Is Causing Packet Fragmentation

This is the most overlooked VPN speed killer. VPNs add bytes to every packet for encryption and tunnel headers. WireGuard adds exactly 80 bytes of overhead. When the resulting packet exceeds the 1500-byte standard Ethernet MTU, routers must fragment it. On many paths, fragmentation triggers retransmissions and stalls rather than a clean split, causing mysterious slowdowns that look nothing like a typical "high latency" problem.

My testing has found this cause to account for seemingly random slowdowns that persist even on nearby, low-load servers.

Test: Send a ping with the "Don't Fragment" bit set and a large payload size. On Linux: ping -M do -s 1420 8.8.8.8. On Windows: ping /f /l 1420 8.8.8.8. On macOS: ping -D -s 1420 8.8.8.8. If packets are lost or you receive a "Fragmentation Needed" error, MTU is the problem. You can also use our Ping Tool to measure basic latency as a baseline.

Fix: In your VPN client's advanced settings, set the MTU to 1420 for WireGuard (1500 minus 80 bytes of WireGuard overhead). For OpenVPN, try 1400-1450. This prevents fragmentation before it starts.

Cause 5: Your ISP Is Throttling VPN Traffic

Some ISPs deliberately slow down VPN traffic using deep packet inspection to identify and rate-limit encrypted tunnels. This is more common in certain regions and on lower-cost consumer plans.

Test: Run a Speed Test without VPN as your baseline. Then connect to a nearby, low-load server and retest. If the drop is dramatic despite optimal server selection, and switching servers or protocols makes little difference, ISP throttling is likely.

Fix: Switch to OpenVPN TCP on port 443. This routes VPN traffic over the same port as HTTPS, which ISPs are reluctant to throttle because doing so breaks normal web browsing for all their users. Some providers also offer obfuscation modes (NordVPN's Obfuscated Servers, for example) that disguise VPN traffic patterns using techniques like the REALITY protocol, making detection much harder.

Cause 6: Encryption Cipher Overhead on Older Hardware

On modern hardware with AES-NI acceleration, encryption is rarely the bottleneck. On older or budget devices without hardware crypto support, it can be. AES-256 requires dedicated silicon to run fast. Without it, every packet goes through software encryption, which consumes significant CPU time.

Test: Check CPU usage while the VPN is active and you are doing a speed test. If CPU pegs at 100%, encryption load is likely the problem.

Fix: Switch to WireGuard if you have not already. WireGuard uses ChaCha20-Poly1305, which is efficient on devices without dedicated AES hardware. On mid-range smartphones without hardware crypto extensions, ChaCha20 can outperform AES-256 significantly. On modern flagships with full hardware acceleration, AES-256-GCM is often equally fast.

Cause 7: DNS Resolution Delays

Slow DNS can make your connection feel sluggish even when raw download speeds are fine. Every page load starts with a DNS query. When connected to a VPN, those queries route through the VPN provider's DNS servers. If those servers are slow, distant, or overloaded, the initial connection to every site lags even though the actual data transfer is fast.

Symptom: Pages are slow to start loading but then download quickly once connected.

Test: Run a DNS Leak Test to see which DNS servers your VPN is using. DNS lookups under 50 ms are good; over 100 ms is noticeably slow.

Fix: If your VPN app allows custom DNS, try 1.1.1.1 (Cloudflare) or 9.9.9.9 (Quad9). After changing, rerun the DNS leak test to confirm no DNS queries are escaping outside the VPN tunnel.

Cause 8: Split Tunneling Is Misconfigured

If all traffic, including bandwidth-heavy local applications, routes through the VPN tunnel, you create unnecessary congestion on an already-limited pipe.

Conversely, if split tunneling is configured too broadly, traffic you need protected may bypass the VPN entirely.

Test: Check whether split tunneling is enabled in your VPN app. If it is disabled, every byte from every application goes through the tunnel, including software updates and local streaming services.

Fix: Enable split tunneling and exclude traffic that does not need VPN protection: OS update services, local network printers, and streaming platforms you access without geo-restriction needs. This reduces tunnel load and can substantially improve speeds for traffic that does use it. See Split Tunneling VPN: What It Is and When to Use It for configuration steps.

Cause 9: Your Base Connection Is the Real Bottleneck

Sometimes the VPN is not the problem. A 10% overhead on a 200 Mbps connection is invisible. The same 10% on a 10 Mbps connection cuts you to 9 Mbps, which is noticeable for HD streaming and video calls.

Test: Disconnect the VPN completely and run a Speed Test. Compare the result to your ISP's advertised speeds. If your base speed is significantly below expectations, the VPN is not the root cause.

Fix: Contact your ISP or check whether your router or modem hardware is limiting throughput. Once base speeds are healthy, re-run the VPN comparison.

Quick Reference: Symptoms and Fixes

How to Test VPN Speed Properly

For accurate, comparable results:

1. Disconnect the VPN completely
2. Run a Speed Test three times and record the average download and upload speeds
3. Use our Ping Tool to note your baseline latency to a nearby server
4. Connect to your VPN on the optimal server with your current protocol
5. Run the speed test three more times and record the average
6. Calculate the percentage difference: that is your actual VPN overhead
7. Switch to WireGuard and repeat to compare protocols
8. Try different server locations to isolate distance as a variable

Test at the same time of day. General internet congestion varies by hour, so comparing morning and evening results will skew the comparison.

When to Consider Switching Providers

If you have applied all the fixes above and still experience consistently poor speeds, the provider itself may be the bottleneck:

• Server loads are consistently high across all locations
• Few servers in your geographic region
• No WireGuard support (still running only OpenVPN)
• No independently published speed benchmarks
• You are on a free VPN (free servers are almost always congested)

After switching providers, verify the new VPN is leak-free with our VPN Leak Test.

FAQ

Why does my VPN slow down my internet even on nearby servers?

The most common causes when distance is not the factor are: an overloaded server at that location, the wrong protocol (switch from OpenVPN to WireGuard), or MTU fragmentation silently stalling your packets. Check server load in your VPN app, switch to WireGuard, and set your VPN MTU to 1420 to rule out all three.

Is a 50% speed drop normal with a VPN?

No. A quality paid VPN on WireGuard or IKEv2 connected to a nearby server should reduce speeds by 5-15%, not 50%. A 50% drop usually points to a specific problem: a distant or congested server, ISP throttling, or MTU fragmentation. A free VPN can drop speeds much further due to perpetually overloaded infrastructure.

Does WireGuard really make a noticeable difference over OpenVPN?

Yes, in most real-world cases. WireGuard runs in the OS kernel rather than user space, which reduces the overhead of shuffling packets between layers. Benchmarks consistently show WireGuard reaching close to full line speed on modern connections where OpenVPN tops out at 60-80% of available bandwidth. The difference is most obvious on connections faster than 100 Mbps.

Can my ISP tell I am using a VPN and slow it down?

Yes. Some ISPs use deep packet inspection to identify encrypted VPN tunnels by their traffic patterns and apply rate limiting. The most effective counter is running OpenVPN TCP on port 443, which makes your VPN traffic look identical to standard HTTPS web traffic. VPN providers with obfuscation modes add an extra layer of disguise on top of that.

Why is my VPN fast for downloads but slow for web browsing?

This is a classic sign of DNS latency. Every page load begins with a DNS lookup to resolve the domain name into an IP address. If your VPN's DNS servers are slow or far away, each lookup adds a noticeable delay before any actual data is transferred. The fix is to run a DNS Leak Test to identify your current DNS servers and, if your VPN app allows it, switch to a faster resolver like 1.1.1.1 or 9.9.9.9.

Sources

• WireGuard performance benchmarks - wireguard.com
• Does a VPN slow down the internet? - NordVPN
• WireGuard vs OpenVPN: Comprehensive 2026 Comparison - Cybernews
• How ISPs Throttle VPN Traffic and How to Bypass It - Undercode Testing
• How to Fix MTU Issues on VPN Connections - BufferSpeed
• AES-256 vs ChaCha20 in 2026: Which Cipher Is Faster for VPNs - vpn.how