How to Test Your VPN Speed in 2026: The Right Method and What to Expect

VPN speed tests are easy to do wrong. Running a single speed test, comparing it to your unprotected speed, and concluding “the VPN slows me down by X%” gives you a number but not useful information. What matters is whether the speed is adequate for your use case, and whether the drop is caused by the VPN or by something else.

Here is how to test VPN speed correctly.

What you are actually measuring

VPN speed is affected by three factors:

Encryption overhead. Every VPN packet is encrypted and encapsulated, adding CPU overhead and size. Modern protocols (WireGuard, NordLynx) reduce this overhead significantly compared to older protocols (OpenVPN, L2TP). On a modern device with hardware AES acceleration, this overhead is negligible.

Server distance. The further the VPN server from you, the more latency (ping) you add to every round trip. Connecting from London to a New York server adds roughly 80-100ms of latency. This is irreducible: it is the speed of light through fiber optic cable.

Server load. A VPN server handling many simultaneous connections has less capacity per user. Good VPN providers manage this with load balancing. Choosing a less-congested server often improves speed more than switching protocols.

Your actual bottleneck might be your home internet connection, not the VPN. If your ISP provides 100 Mbps and the VPN can sustain 500 Mbps, the VPN is not your limiting factor.

The correct testing methodology

Step 1: Establish your baseline

Test your internet speed without the VPN connected. Use Speedtest.net, Fast.com, or nperf.com. Run three tests and average the results. Do this on a wired connection if possible; Wi-Fi introduces its own variability.

Note three numbers: download speed, upload speed, and latency (ping).

Step 2: Connect to a nearby VPN server

Connect to the VPN server in your country or the nearest country. Do not test to a distant server for your baseline VPN comparison; you want to measure the protocol overhead, not the geography.

Step 3: Run the same speed tests

Run three speed tests through the VPN on the same test server (use the same Speedtest.net server). Average the results.

Step 4: Calculate retention

Divide your VPN download speed by your baseline download speed. A result of 0.90 means the VPN retained 90% of your speed (a 10% reduction). A result above 0.85 is good for a premium VPN.

Step 5: Test for your actual use case

Run tests on a server in the country you will actually use. If you want a UK Netflix server, test a UK VPN server. If you connect to US streaming sites, test a US server. The numbers that matter are for your actual use case, not a nearby server.

Reference benchmarks: what to expect

Based on our monthly testing across providers:

On a 100 Mbps connection, NordLynx typically delivers 90-97 Mbps on a nearby server, dropping to around 75-80 Mbps on a transatlantic connection. This is adequate for any streaming or browsing task.

Want to compare all VPNs side by side? Check our full VPN comparison table with scores across 18 criteria.

Diagnosing slow VPN speeds

If your VPN is slower than the benchmarks suggest it should be:

Try a different protocol first. If you are on OpenVPN, switch to WireGuard or NordLynx. This single change often doubles measured speed. OpenVPN is reliable but not fast.

Try a different server. In the same country, different servers have different load levels. A server at 90% capacity will be slower than one at 20% capacity. Try two or three different servers and compare.

Check your device. Older devices with slow CPUs cannot decrypt VPN traffic fast enough to saturate a fast connection. A phone from 2018 might cap out at 100 Mbps through a VPN even if the network and VPN server could deliver more.

Check your Wi-Fi. A 5 GHz Wi-Fi connection on a modern router can deliver 200-400 Mbps; older 2.4 GHz Wi-Fi caps at around 50-100 Mbps in practice. A wired connection eliminates this variable entirely.

Check the server distance. If you are using a server in another continent, some slowdown is inherent. Test a closer server to confirm the VPN itself is not the issue.

Speed vs. latency: different things matter for different use cases

Streaming needs sustained throughput but is tolerant of latency. A 50ms ping with 25 Mbps throughput is fine for 4K streaming. A 5ms ping with 25 Mbps is not meaningfully better for this use case.

Gaming needs low latency more than high throughput. A 15ms ping to a game server through a VPN is fine; 80ms will affect your performance in competitive games. Connect to a VPN server close to the game server, not close to you.

Video calls need symmetric throughput (both upload and download) and low latency. A VPN with 50 Mbps down/20 Mbps up and 30ms latency is adequate for most video call platforms.

File downloads and uploads benefit from throughput and are not sensitive to latency. Any good VPN in WireGuard mode will not meaningfully slow large transfers.

Keep reading: Why Is My VPN Slow? Fixes That Actually Work and WireGuard vs OpenVPN: Which Protocol Should You Use?.