# Performance & Networks

A VPN that stays connected but crawls isn't much use. SecurQbit is tuned to deliver usable speed on exactly the kinds of networks where VPNs struggle — slow cellular, congested public Wi-Fi, and oversubscribed hotel links.

## Network-aware optimization

SecurQbit continuously measures the conditions of the link you're on and adapts the tunnel to match. Rather than assuming a fast, stable connection, it tunes packet sizing, batching, and retransmission behavior to the real characteristics of the network:

- **High-latency links** (e.g. 3G, distant servers) get pacing adjustments that keep throughput from collapsing under round-trip delay.
- **Lossy links** (congested Wi-Fi) get tuned recovery so a few dropped packets don't stall the whole session.
- **Constrained links** (hotel, captive networks) get traffic shaping that fits within tight bandwidth budgets.

This happens automatically and shifts in real time as you move between networks.

## Behavior on common networks

| Network | What SecurQbit does | What to expect |
| --- | --- | --- |
| 3G / weak cellular | Latency-aware pacing, smaller effective packets | Connection holds; speed is bounded by the cellular link |
| Congested public Wi-Fi | Loss-tolerant recovery | Smoother browsing than a naive tunnel |
| Hotel / captive networks | Shaping within bandwidth caps, [obfuscation](/firewall-bypass) | Reliable connection where other VPNs may be blocked |
| Fast home / fiber Wi-Fi | Minimal intervention | Near-line-rate, low overhead |

## Tips to improve speed

1. **Use Auto (fastest).** Auto-select weighs latency and server load to pick the best endpoint. See [Connecting to a Server](/connecting).
2. **Pick a nearby server** when you don't need a specific region — distance is the biggest single factor in latency.
3. **Let obfuscation adapt.** It's always on at full strength, and its network-aware optimization already keeps overhead low on open networks — there's nothing to tune. See [Firewall Bypass & Obfuscation](/firewall-bypass).
4. **Use [split tunneling](/split-tunneling)** to keep bulky, non-sensitive transfers off the tunnel.
5. **Avoid stacking VPNs or proxies** — chaining tunnels multiplies overhead and latency.

## Expected overhead

Every VPN adds some cost: encryption, encapsulation, and the extra network hop through the server. With SecurQbit:

- On a fast, unrestricted link, overhead is modest and most users won't notice it day to day.
- Encryption itself is cheap on modern devices thanks to hardware-accelerated AEAD ciphers; see [Encryption & Protocols](/encryption).
- The largest variable is usually **distance to the server** and the quality of the underlying network — not SecurQbit itself.

```text
Tunnel overhead ≈ encryption + encapsulation + extra hop
Dominant factors: server distance, base link quality, network conditions
```

> **Tip:** If speeds feel low, switch to **Auto (fastest)**, try a closer server, and confirm whether your base (VPN-off) connection is already slow. See [Troubleshooting](/troubleshooting).