Steps
- Use TCPing or a connectivity check to remove unreachable profiles. A -1 means that test failed, not necessarily that every possible protocol path is impossible.
- Run a real delay test that includes the proxy handshake and target response; it better reflects browsing.
- For downloads or streaming, perform one short test against a reputable service and watch sustained throughput and jitter rather than the peak.
- Repeat on the network and at the time you actually use. Compare failures and variance, not just the smallest number.
Why this matters
A server with low TCP latency may be congested or poorly routed to your destination. Layered tests separate fast connection setup from a good session.
How to verify
The chosen profile opens several sites repeatedly, does not reconnect constantly and keeps real delay within an acceptable range.
Things to watch
Bulk bandwidth tests consume quota and load the server. A public benchmark is not a permanent service guarantee.