Quick answer: A proper VPN speed test checks download, upload, latency and jitter under comparable conditions. Modern protocols (WireGuard family) and nearby servers deliver 80–90% of your original speed.

What does a VPN speed test measure?

It’s not just about one “number”. Speed tests reflect how efficiently your VPN handles data transfers and network latency. Key metrics include:

• Download speed — how fast data reaches you; affects streaming and downloads.
• Upload speed — how fast you send data; important for calls and backups.
• Ping (latency) — round-trip time in milliseconds; lower is better for gaming and VoIP.
• Jitter — latency variation; spikes cause lag or audio glitches.
• Packet loss — missing packets that force retransmission and slow apps.

How to test VPN speed accurately

1. Start with a baseline (no VPN) using a trusted speed test service.
2. Connect to the nearest VPN server and repeat the test 3 times; average results.
3. Switch to a mid-distance server (e.g., another state or region) and test again.
4. Compare download, upload, and ping values to identify where speed drops.
5. Try different protocols (WireGuard, IKEv2, OpenVPN) to see which performs best on your network.
6. Record results at different times of day to factor in ISP congestion.

Reading your results

If you get 80–90% of baseline speed on nearby servers, your VPN is well-optimized. Drops below 60% mean it’s time to change server location or protocol. Higher latency (100 ms+) is fine for streaming but hurts gaming and calls.

Practical ways to make your VPN faster

1. Use WireGuard or NordLynx instead of OpenVPN.
2. Connect to the closest server physically and logically.
3. Choose a different city within the same region to avoid crowded servers.
4. Use Ethernet or strong 5 GHz Wi-Fi instead of 2.4 GHz.
5. Close background apps syncing data (cloud, game updates).
6. Restart router to clear bufferbloat and improve latency.
7. Try Split Tunneling to exclude non-essential apps (learn more).
8. Use servers tagged as Streaming or P2P for those tasks (server types explained).
9. Run a DNS leak test to ensure resolvers aren’t slowing down (DNS leak guide).
10. Keep your VPN app updated — new versions often boost speed.

Watch: How to test VPN speed properly

Watch on YouTube — NordVPN official channel.

Common testing mistakes

• Comparing different targets for baseline and VPN tests.
• Testing only once instead of multiple runs.
• Using Wi-Fi during rush hours — use Ethernet when possible.
• Ignoring upload and jitter values.
• Sticking to slow protocols like OpenVPN-TCP by default.

Advanced diagnostics: when results look “wrong”

Sometimes your numbers look inconsistent across runs. Before blaming the VPN, check for background sync (cloud drives, system updates), QoS rules on your router, and overloaded test targets. Try two independent testers and keep the one that’s closer to your real-world apps (streaming vs. large file mirrors). If Ethernet outperforms Wi-Fi by a lot, interference or 2.4 GHz congestion is the likely culprit.

Streaming, gaming and remote work scenarios

Streaming

Throughput matters most. Aim for stable download above 25–50 Mbps for 4K streams with reasonable headroom. Specialized locations often work better; see our VPN for streaming guide and, for specific services, Netflix or BBC iPlayer.

Gaming

Latency and jitter dominate. Pick a server closest to the game region. If ping still spikes, switch protocol (WireGuard → IKEv2) and move from Wi-Fi to Ethernet. Our gaming guide covers hitboxes, tick-rate, and NAT quirks.

Remote work & calls

Video calls need consistent upload and low jitter. Test at the same time you usually meet. If your corporate stack uses split DNS or strict firewalls, match the VPN protocol to your network (often IKEv2). See remote work and online banking for stability tips.

Protocol impact on speed

In 2025, WireGuard-based stacks typically win on raw throughput and CPU efficiency, while OpenVPN-TCP remains the slow, compatibility fallback. OpenVPN-UDP can be fine on stable networks; IKEv2 shines on mobile because it roams between networks quickly. Compare options in our overview: VPN protocols.

Server choice: proximity vs. capacity

Nearby servers aren’t always fastest. Capacity, peering and congestion matter. If your closest city underperforms, try another in the same region, then a neighboring country. For task-specific performance use tags like Streaming or P2P; details in VPN server types.

Mobile testing specifics

• Use airplane mode toggle before each run to clear radio state.
• Prefer 5 GHz Wi-Fi; on LTE/5G, cell load varies minute to minute.
• Disable battery savers that throttle background networking.
• On iOS/Android, try protocol auto → WireGuard → IKEv2; keep screenshots of each run.

Suspecting ISP throttling?

If your baseline to certain video CDNs is consistently worse than the same path over VPN, your ISP may shape traffic. Compare against geo-blocked services and run tests to multiple targets. A well-peered VPN can restore normal speed, but expect a small latency trade-off.

Security settings that also influence speed

MTU mismatches, DNS timeouts, and aggressive kill-switch rules can hurt performance. Start with defaults from your provider, then fine-tune using our optimal settings checklist. Always re-test after each change.

Quick troubleshooting checklist

• Retest on Ethernet → compare to Wi-Fi.
• Switch server (same region → neighbor city).
• Change protocol (WireGuard ⇄ IKEv2 ⇄ OpenVPN-UDP).
• Restart router; avoid 2.4 GHz; close heavy background apps.
• Exclude non-critical apps via Split Tunneling.
• Verify no DNS leaks or packet loss.

FAQ — VPN speed testing