Skip to main content

SHOW THE METHOD, NOT JUST THE SCORE

How we test VPN performance

A reliable comparison starts before the VPN connects: with a clean baseline, consistent conditions and transparent quality checks.

Independent test evidenceSource and date matterNo invented winners
Transparent benchmark methodology

We start by measuring the connection without a VPN. Then we test one specific VPN setup — provider, protocol and exit location — from the same source. After quality checks, we compare the VPN result with that clean baseline.

Step 1 Measure the clean connection Check the source connection before the VPN is added.
Step 2 Test one VPN setup Provider, protocol and exit location are kept separate.
Step 3 Check the measurement Only tests that pass our quality rules are used in headline results.
Step 4 Compare against the baseline The VPN result is judged against the clean connection measured just before it.

Why we measure a clean baseline first

Before each VPN test, we measure the same source without a VPN. That gives us a clean reference point and helps separate VPN overhead from normal differences in connection speed.

Clean connection speed Shows how much speed is available before the VPN is turned on.
VPN speed Shows how the same connection performs after the selected VPN route is active.

How much speed the VPN keeps

We still show raw Mbps, but raw speed alone can be misleading. A faster source connection can make a VPN look better than it really is, so we also show how much of the original speed was retained.

How much speed the VPN keeps (%) = VPN speed Mbps ÷ paired baseline download Mbps × 100

Check the measurement

Headline Heatmap, Rankings and Analytics views use measurements marked rankable=true by the quality layer. Invalid baselines and other disqualifying measurements are kept out of headline calculations instead of being silently averaged in.

A test is not automatically good enough for rankings just because it exists in the database. It still has to pass the quality checks and have enough useful coverage.

Where the test starts is not the same as where the VPN exits

The test location is where the connection starts. The destination is the VPN exit. The same exit can perform very differently depending on where the connection begins.

Test location The physical Secure-VPN benchmark origin.
VPN destination The VPN exit country, city or endpoint being tested.

We do not mix VPN protocols together

NordLynx, Lightway and OpenVPN are measured separately. A provider may perform very differently depending on which protocol you use.

Compare providers fairly Compare providers using compatible routes and benchmark conditions.
Compare protocols directly See how NordLynx, Lightway and OpenVPN differ without blending them together.
Personalized VPN Speed Predictor

How the personalized speed estimate works

The Speed Test starts with your own connection. We then compare that result with past quality-checked VPN tests for specific providers, protocols and exit locations.

1 · Test your connection We measure your current direct download speed first.
2 · Look at matching VPN setups Provider, protocol and exit location stay separate in the estimate.
3 · Build a likely speed range Your measured speed is combined with historical VPN retention data.
4 · Show how strong the estimate is We show the sample count and confidence so you can judge how much data supports the result.
Expected VPN speed range ≈ measured baseline × historical VPN retention range
The result is an estimate, not a guaranteed future speed. ISP routing, congestion, Wi-Fi, server load, device limits and time of day can change actual VPN performance.

Why sample coverage matters

We show sample counts and destination coverage instead of hiding them. If the data is thin, the result may be held back or shown with lower confidence.

Technical results stay separate from commercial relationships

Affiliate payout, CPA and revenue-share data are kept separate from the technical benchmark. Commercial relationships are not used to decide which VPN ranks first on performance.