A distant or congested server is almost always the cause. Switching server location and protocol gives you the fastest result with the least effort.
Every VPN connection routes your traffic through a server — the further that server is from your physical location, the more latency is added to every request. A server on another continent can add 150–300ms of latency to connections that previously had 10–20ms, making browsing feel sluggish regardless of bandwidth. Server load compounds this: a congested server has less capacity per user, reducing throughput even on fast connections. Switching to a nearby, lightly loaded server is the single most impactful fix.
Different VPN protocols have different performance profiles. OpenVPN, while widely supported, carries more overhead per packet than newer protocols. WireGuard uses modern cryptography that's implemented closer to the OS kernel, resulting in significantly lower CPU overhead and higher throughput — especially on machines where CPU is the bottleneck. IKEv2 is a middle ground: faster than OpenVPN, generally well-supported, though less universally available than WireGuard.
All VPN connections add some overhead — encryption/decryption processing, routing through an additional server, and protocol encapsulation. On a fast connection (100+ Mbps), VPN overhead might reduce throughput by 10–30%. On a slower connection (10–25 Mbps), the same overhead represents a larger percentage reduction and feels more significant. If your base speed without the VPN is already limited, no VPN optimization will make the connection feel fast.
Some ISPs use deep packet inspection to identify and throttle VPN traffic. This is less common than the other causes but tends to produce a distinctive pattern: normal speeds without VPN, consistently slow speeds with any VPN server, with throttling particularly affecting high-bandwidth activities like streaming or large downloads. Using an obfuscated protocol that disguises VPN traffic as standard HTTPS is the primary workaround.
Disconnect from the VPN and run a speed test (fast.com or speedtest.net). Note your download speed, upload speed, and ping/latency. Reconnect to the VPN and run the same test again. This tells you exactly how much the VPN is reducing your speed. A 10–30% reduction is normal; more than 50% suggests a server, protocol, or ISP issue worth investigating further.
In your VPN client, select a server in your own country or a neighboring country rather than one on another continent. Most clients show server locations on a map or list. Some clients also display server load — aim for servers below 50% load. If your client has an 'auto' or 'fastest server' option, try it, but manually selecting a nearby server often yields better results since the auto-selection algorithm doesn't always prioritize latency.
In your VPN client's settings, look for a Protocol section. If WireGuard is available, select it and reconnect. WireGuard's leaner implementation means lower CPU overhead per packet, which translates to meaningfully higher throughput and lower latency compared to OpenVPN on the same hardware and server. If WireGuard isn't available, try IKEv2 as the next-fastest option. Reconnect and run a speed test again to compare.
VPN server congestion varies with peak usage — evenings and early mornings when many users are active tend to be slower than midday. If your VPN is consistently fast in the morning but slow in the evening, server congestion during peak hours is the cause. Some providers offer dedicated or less-advertised servers for paying users that handle congestion better than the default servers.
Close or pause any applications consuming bandwidth while testing: Windows Update (Settings > Windows Update > Pause updates temporarily), cloud backups (OneDrive, Backblaze, Google Drive syncing), video streaming, and large file downloads. These compete for bandwidth with the VPN tunnel and can skew speed tests. Once you've established clean VPN performance, you'll know your true available bandwidth for work tasks.
If switching servers and protocols doesn't improve speed, and your base connection is fast, the issue may be infrastructure-level on your provider's end — capacity constraints, routing issues, or regional congestion outside the client. Contact your VPN provider's support with your speed test results. Many providers have a server recommendations tool or can suggest servers performing well for your region.
Share your speed test results with and without VPN — our AI can help identify whether the bottleneck is server-side, protocol-related, or your base connection.
Tell our AI your VPN provider, protocol, and speed test results — it'll identify what's limiting your connection.
Start Free Diagnostic Chat →