VPN Speed Test: How I Test (2025 Method)
By Saleem Ishaq | Cybersecurity analyst | 1 year testing 30+ VPNs | Last tested: Nov 1, 2025
In 2025, VPN speeds aren't just marketing hype—they're make-or-break for 4K streaming, gaming, and torrenting. But advertised "950 Mbps" claims? Often fluff. I test 30+ VPNs rigorously on 1 Gbps fiber to cut through the noise, revealing real-world performance like NordVPN's 3% speed loss or Proton VPN's 16% drop.
This transparent method ensures unbiased results. No cherry-picked servers or peak-hour tests—everything's replicated under typical conditions. I've run 500+ tests this year, using tools like Ookla CLI for accuracy. Here's exactly how I do it, step-by-step, so you can verify at home.
Why share? Readers deserve proof, not promises. My tests align with industry standards from CNET, ZDNET, and Comparitech, but tailored for everyday users in Toronto (Eastern Time, mixed ISP traffic).
Baseline Setup: Establishing Your Starting Point
Every test starts with a no-VPN baseline. This measures your raw connection—essential for calculating speed loss percentage (aim for under 25% for top VPNs).
Hardware & Environment
- Connection: 1 Gbps fiber (Rogers, Toronto)—symmetric up/down, low jitter.
- Device: Mid-range Windows 11 laptop (Intel i7, 16GB RAM) + wired Ethernet (Cat6 cable, no Wi-Fi interference).
- Conditions: Off-peak hours (2-4 AM EST) to mimic real use; close bandwidth hogs (downloads, updates).
- Software: Clean OS—no other apps running. Firewall/antivirus disabled during tests (re-enabled after).
Pro tip: Use Ethernet over Wi-Fi for 10-20% speed gains. Baseline results? Typically 945 Mbps down / 920 Mbps up / 10 ms ping.
Baseline: 945 Mbps ↓ / 920 Mbps ↑ / 10 ms ping
Step 1: Measuring Raw Speed (No VPN)
Use Ookla Speedtest CLI—more reliable than browser versions, as it avoids JavaScript overhead. Why CLI? It runs server-side for precise multi-threaded tests.
Command-Line Test
- Install Ookla CLI: Download from speedtest.net.
- Run:
speedtest --server-id=US-NY (for New York)—5 runs, average results. - Record: Download (Mbps), Upload (Mbps), Ping (ms), Jitter (ms).
- Tools: Wireshark for packet analysis (ensure no ISP throttling).
Example baseline: 945 Mbps down (ideal for 4K@60fps, needing 25 Mbps min). If under 500 Mbps, upgrade your ISP first—VPNs can't fix bad pipes.
Step 2: VPN Connection & Protocol Selection
Test multiple protocols—WireGuard/NordLynx for speed, OpenVPN for security trade-offs.
Key Protocols Tested
| Protocol | VPNs Supporting | Avg Speed Loss | Best For |
|---|---|---|---|
| WireGuard/NordLynx | NordVPN, Proton, Surfshark | 3-18% | Streaming/Gaming |
| Lightway | ExpressVPN | 18% | Travel (Obfuscated) |
| OpenVPN | All | 25-40% | High Security |
- Connect to 10+ servers: 5 nearby (US/Canada), 5 distant (Japan/Australia).
- Enable features: Kill switch, split tunneling (test bypassed traffic).
- Wait 30 seconds for stabilization—avoids initial handshake lag.
2025 update: NordLynx (WireGuard-based) leads with 3% loss
Step 3: Running Speed Tests with VPN Active
Repeat baseline, but VPN on. Focus on download (streaming/torrents), upload (Zoom/calls), and ping (gaming, under 50 ms ideal).
Detailed Process
- Run Ookla CLI 5x per server/protocol:
speedtest --csvfor data export. - Calculate: % Loss = (Baseline - VPN) / Baseline x 100. Target: <25%.
- Test latency: Ping google.com (via VPN)—add 20-50 ms expected.
- Buffer bloat: Upload a 1 GB file to Dropbox; measure spikes.
Tools: Fast.com for Netflix-specific (measures sustained throughput). Results averaged: NordVPN 935 Mbps (3% loss), Proton 885 Mbps (16% loss)
Process: Baseline → Connect → 5x Tests → Average % Loss
Step 4: Leak & Stability Checks
Speed without security? Useless. Post-test verification:
- DNS Leaks: dnsleaktest.com—must show VPN IP only.
- WebRTC/IPv6: ipleak.net—disable if leaking.
- Kill Switch: Force disconnect mid-test; traffic must halt (0 bytes out).
- Stability: 1-hour sustained test (stream 4K video); log drops.
2025 insight: Proton's Secure Core (double-hop) adds 20% loss but zero leaks
Step 5: Real-World Benchmarks
Beyond numbers: Simulate use cases on 1 Gbps base.
Activity Tests
| Activity | Test Tool | NordVPN Result | Proton Result | Express Result |
|---|---|---|---|---|
| 4K Netflix | Buffer time | 0 sec | 2 sec | 1 sec |
| Torrent 10 GB | qBittorrent | 1:48 | 1:55 | 2:05 |
| Gaming Ping | CS:GO to Tokyo | 45 ms | 55 ms | 50 ms |
| Zoom Call | Upload stability | 890 Mbps | 710 Mbps | 845 Mbps |
Data from 50 runs—NordVPN edges out for mixed use
Common Pitfalls & Optimization Tips
Why tests vary: Time of day (peak congestion), server load, protocol choice.
- Avoid Browser Tests: Use CLI for accuracy
. - Close Apps: Bandwidth hogs skew results.
- Choose Nearby Servers: Distant ones add 50-100 ms ping.
- Enable Accelerator: Proton's boosts 400% on long hauls
.
Run your own: Download Ookla CLI—compare to my baselines.
FAQ: Speed Testing Essentials
Best protocol? WireGuard for 95% retention.
Acceptable loss? Under 25%—NordVPN at 3% is elite
Test mobile? Yes, but expect 20% Wi-Fi drop.
Bottom Line: My method—baseline, CLI tests, leaks—exposes true performance. NordVPN leads 2025 speeds; see comparison table for full rankings.
Affiliate Disclosure: Commissions from links. Tests independent.
Last updated: November 3, 2025