Connected but slow—pages load, video buffers, downloads crawl. Clash Verge Rev chooses the path; the ceiling is usually provider bandwidth and node load. Settings help you pick nodes, avoid hairpins, and cut overhead—they don’t invent capacity. The fastest way to waste an evening is to re-tune the client when the line itself is the limit.
Order of attack: lower-load node (not just lowest ping) → DIRECT for domestic bulk → check the test URL and protocol → rule out local contention → only then touch Tun/DNS. Latency basics: latency; picking a provider: choose a provider.
What client settings can and can’t fix
Before you touch anything, separate the two layers. Most “slow Clash” tickets are actually “slow line” tickets wearing a client costume.
| Symptom | Usually the client | Usually the line / node |
|---|---|---|
| One site slow, others fine | Routing rule sending it abroad | — |
| Everything slow at the same time | — | Provider load, home ISP, peak hour |
| Low ping but slow download | — | Throughput / peak / protocol cap |
| Domestic download crawls | Traffic riding the proxy (hairpin) | — |
| Packet loss spikes in-game | Wrong group / bad UDP node | Transit congestion |
The three-node, ten-minute test
Don’t trust the auto‑selector’s pick. At the same moment, pull three different nodes and compare. If all three are slow, the problem is not the client. If one is clearly faster, pin it and ask why auto‑select keeps jumping to the slow one.
Clash Verge Rev
→ Profiles (your subscription)
→ Right-click "Test All" or set the test URL
→ Sort by "Delay" but also eyeball "Download" in a real transfer
→ Pin the node that wins on throughput, not just latency
Low latency with a slow download almost always means throughput, peak, or protocol shaping—not a node you can “fix” by chasing a lower ping.
DIRECT, tests, and local noise
Domestic downloads routed through the proxy are hairpins—send them DIRECT (DIRECT rules, Steam). A bad test URL poisons auto‑select, so point it at a stable target. Local contention hides as “bad node” constantly: multiple downloaders, browser extensions, a leftover VPN, or AV real‑time scanning. Wi‑Fi interference often looks like a “bad node”—try ethernet before you blame the subscription.
Tun, DNS, MTU: touch only with a reason
| Knob | Touch it when… | Leave it when… |
|---|---|---|
| Tun | An app ignores system proxy | You only browse—system proxy is enough |
| DNS | You see resolution leaks / wrong region | It already resolves correctly |
| MTU | Fragmentation after a controlled trial | Never, as a “speed” guess |
| url-test interval | Auto-select keeps thrashing | Defaults feel stable |
Don’t force Tun for plain browsing (Tun). Random DNS edits can slow you down instead of helping (DNS). MTU is a single controlled trial with rollback, not a tuning dial. Prefer Rule over Global (routing).
Stop optimizing forever
If node swaps, DIRECT, and local cleanup all fail, change provider—not endless client tweaks. Logs when you suspect local errors (logs). AI slowness is usually region + Tun (Tun & AI). FAQ: FAQ; builds: download center.