If your VPN slows down every evening, peak-hour congestion may be part of the problem, but it is rarely the only possibility. A busy Wi-Fi network, a distant server, a protocol that does not suit your current connection, or an app that is uploading in the background can all make browsing and streaming feel sluggish. The useful first step is to identify what is slow: the internet connection itself, the VPN route, or one particular app.
Change one setting at a time and repeat the same simple test after each change. If you switch servers, protocol, and Wi-Fi together, a better result will not tell you which change helped. The checks below are designed to narrow down the cause before you spend time rebuilding a configuration or reinstalling a client.
Identify what is slow before changing settings
Begin with a comparison between your connection with the VPN enabled and the same connection with it paused or disconnected. Use the same device, network, website, and app where possible. Do not start a large download during one test and compare it with an idle connection during the other. The aim is not to produce a laboratory benchmark; it is to see whether the slowdown follows the VPN, the local network, or a specific service.
First, check whether ordinary websites and local network services are also slow. If everything responds slowly, including pages that do not need the VPN, investigate the router, Wi-Fi signal, device, or internet provider before adjusting VPN settings. If only traffic routed through the VPN is affected, the server, route, protocol, or client configuration becomes a more likely place to look. If one streaming app is slow while other VPN traffic works normally, the cause may be app-specific rather than a general connection problem.
Keep the comparison consistent. Use the same browser tab or app, wait for any page or video to settle, and repeat the check if the result seems unusual. A single slow page can be caused by that website or its content delivery network. Avoid judging a route only by how quickly a page begins to load: video quality changes, background buffering, and large downloads reveal different aspects of performance.
- ✅ Compare the same app and destination with the VPN on and off.
- ✅ Check whether other devices on the same Wi-Fi have slowed down too.
- ✅ Note whether the issue affects all VPN traffic or only one app or website.
- ❌ Do not change several client settings at once and assume you know which one helped.
When the connection is slow with the VPN off as well, restarting the VPN client is unlikely to fix the underlying network issue. Check whether the router has a weak signal, whether another device is using the connection heavily, and whether the slowdown continues on a different network. If the problem appears only on VPN traffic, keep the local connection unchanged for the next checks so that the comparison remains useful.
Check the selected server and route
A server that worked earlier may be busy later, or the network path between your device and that server may be having trouble. This does not mean every server in a region is equally affected. Try another available server in the same general location first. If the issue remains, compare with a nearby alternative location that still meets the requirements of the app or website you are using.
Do not select a server solely because its name suggests a popular city or because it appears near the top of a list. Availability, routing, and server load can vary, and the client may provide different locations for different purposes. If you need a particular region for a service, stay within the regions that service accepts; choosing a distant location just to test speed can add distance without answering the question you are trying to solve.
After switching servers, allow the client to establish a fresh connection and test again. If a client offers a route or server status view, use it as a diagnostic clue, not as proof that an app is using that route. Some apps maintain existing connections until they are restarted, and a browser may reuse a connection opened before the server change. Close and reopen the affected app if necessary, then repeat the same test.
| What you notice | Possible area to investigate | Practical next step |
|---|---|---|
| All VPN apps feel slow | Selected server, route, or client connection | Reconnect, then compare a different server |
| VPN and non-VPN apps are slow | Wi-Fi, router, device, or internet connection | Check another device or network before changing VPN settings |
| One app is affected | App-specific routing, cached connection, or service behavior | Restart the app and check its proxy or network settings |
| The problem changes by location | Route distance, regional path, or destination requirements | Compare suitable nearby alternatives under the same conditions |
For travelers comparing a route before using region-dependent sites and apps, the VPN for China Travel page provides the service’s main entry point; whichever route you choose, check that it fits your destination and app needs rather than assuming that the closest-looking server is automatically the fastest.
Keep notes in plain language: which server location you tried, whether the VPN was on, which app you tested, and what changed. You do not need to record invented precision or rely on a single speed-test result. A repeatable observation such as “video playback improves on the alternate server, while general browsing is unchanged” is more useful than an isolated number without context.
Review protocol and client settings
The protocol determines how the client establishes and carries the tunnel, but there is no protocol that is universally fastest on every network. A connection that handles one Wi-Fi network well may behave differently on mobile data, a restricted workplace network, or a router with unusual settings. If the client provides a protocol choice, compare only the options it actually supports and follow its documentation for the recommended configuration.
Protocol names are not interchangeable labels for server locations. Shadowsocks is a proxy protocol; VMess and Trojan are also used in proxy configurations, while WireGuard is a VPN protocol. Hysteria2 is designed around QUIC and can use UDP. Support depends on both the service configuration and the client: seeing a protocol in a third-party app does not mean a particular subscription provides a compatible profile for it. Do not manually change protocol fields in an imported configuration unless you know the service supports that combination.
For a safe comparison, note the current setting, choose a different supported option in the client, reconnect, and retest the same app. If the connection fails or becomes less stable, restore the previous option. Avoid running two proxy or VPN clients at the same time. Their system proxy settings, virtual interfaces, DNS handling, or routes can conflict, making an apparent speed issue difficult to diagnose.
Also check whether the client is in a mode that captures the traffic you are testing. A system proxy usually affects applications that honor the operating system’s proxy settings. A TUN-based mode can capture traffic through a virtual network interface, but it may require permissions and correct routing and DNS settings. Global and rule-based modes determine how captured traffic is handled; changing a routing policy will not necessarily capture an app that never entered the client in the first place.
Restore the client to a known-good state if you have recently imported several profiles or changed advanced settings. Confirm that the selected configuration is current, the client reports a connected state, and the app is using the intended route. If you use a compatible third-party client such as Clash Verge, sing-box, or Shadowrocket, check that the subscription format and supported protocol match that client. Importing a profile successfully is not the same as confirming that every rule and app is routed as intended.
Rule out Wi-Fi and device load
Evening slowdowns can come from the local network. More people may be using the same Wi-Fi, a device may be uploading photos or backing up files, or a television may be streaming at the same time. Those activities can affect the connection before VPN traffic reaches a server. Check the router’s connected-device list if available, pause nonessential transfers briefly, and compare again. Do not disable security features or make permanent router changes simply to test a temporary slowdown.
Signal quality matters too. A device at the edge of Wi-Fi coverage may experience retries or interruptions that are easy to mistake for a slow VPN. Move closer to the router or test with a wired connection where practical. If the device supports separate Wi-Fi bands, try the one that gives a more stable connection in your location; walls, interference, and router placement can affect the result. Reconnect to Wi-Fi after changing networks so the device is not holding onto a weak connection.
Check the device itself for background work. Operating-system updates, cloud synchronization, game downloads, and browser tabs playing media can compete for bandwidth or processing resources. A nearly full device or an overloaded browser can also make pages feel slow even when the network route is working. Close unnecessary downloads and apps temporarily, then repeat the same test without changing the VPN configuration.
DNS and local filtering are worth checking when connections take a long time to begin, some domains fail while others work, or changing servers has no consistent effect. A client may have DNS settings of its own, and security, parental-control, or ad-blocking software can also affect name resolution. Do not add arbitrary public DNS addresses or disable protection as a first response. Check the client’s documented DNS options and change them only when you can restore the original setting.
- ✅ Compare Wi-Fi with mobile data or another trusted network when available.
- ✅ Pause large uploads, downloads, and cloud backups while testing.
- ✅ Restart the affected app after switching routes so it creates a fresh connection.
- ❌ Do not run multiple VPN or proxy clients together during diagnosis.
- ❌ Do not turn off device or router security permanently to chase a speed improvement.
Use a repeatable evening checklist
When the slowdown returns, follow the same order rather than making random changes. Start by checking whether other apps and devices are affected. Then compare the same destination with the VPN temporarily disconnected, if it is safe and appropriate to do so. If the local connection is normal but VPN traffic is slow, reconnect to the current server, test a suitable alternative, and only then consider a supported protocol or client-mode change.
Keep an eye on what changed between a good session and a slow one. The device may have moved to another Wi-Fi access point, the router may have restarted, a client may have updated, or a subscription profile may have been refreshed. These details can explain why the same server or setting behaves differently. If the issue began after an update, confirm that the client and imported configuration remain compatible before reinstalling anything.
Once a change improves the result, leave the other settings untouched for a while and see whether the improvement persists. If you need to undo it, return to the recorded previous setting. This is especially important for DNS, TUN, and routing rules: a quick experiment should not leave you with an undocumented configuration that breaks other apps later.
Bottom line: First determine whether the slowdown affects the local connection, all VPN traffic, or one app. Then test a fresh connection and a suitable alternate server before changing supported protocol or routing settings. A controlled comparison is more useful than repeatedly switching options without a clear baseline.
If the issue persists across suitable servers and networks, collect the client name and version, device platform, approximate time the slowdown occurs, selected location, connection mode, and the steps you have already tried. Share those details with the service’s support team through its official support channel. Do not post account credentials, private subscription links, or other sensitive configuration data in a public forum.
A consistent evening pattern is useful diagnostic information, but it does not by itself prove that a server is overloaded. Local Wi-Fi demand, internet-provider routing, a destination service, and device background activity can produce similar symptoms. By separating these possibilities and changing one factor at a time, you can identify a practical fix without weakening security or rebuilding a working setup unnecessarily.