Let's separate two things first: Can't open It's a connectivity issue, check it out Unable to access the Internet to troubleshoot;This article only solves slow——It works, but the video spins in circles, the web page drags, and the download speed cannot increase. Ninety percent of the reason for slowness is not in the software settings, but in the nodes and lines, so the troubleshooting idea is to "locate where the bottleneck is first, and then prescribe the right medicine." Don't change parameters randomly at the first step.

1First, distinguish: is the delay high or the bandwidth is small?

These are two different indicators, corresponding to different body sensations:

  • High latency (hundreds of ms): There was no response after clicking on the web page for a long time, but once the video started playing, it didn't freeze. Select all nodes button Ctrl+R You can see it by testing the real connection delay. Speed test tutorial I talked about how to read.
  • Small bandwidth: Web pages open in seconds, but buffering occurs at 1080P and above. Judgment method: open fast.com with the agent attached and test it once, then disconnect the agent and test the local bandwidth - if the local bandwidth is 300M and the node is only 10M, the bottleneck is at the node.

Don't judge speed by latency numbers: The bandwidth of a node with 38ms may only be 5M, but a node with 150ms may fill up your bandwidth. Delay determines whether the response is fast or not, and bandwidth determines whether the volume is large or not. Watching videos mainly depends on the latter.

2Nodes and lines: the main source of slowness

  • Evening rush hour congestion: 20:00–23:00 The international exit is the most crowded, and traffic flow during the day and lag at night is a typical symptom. This is not your problem, it's the line's problem—switch to a node with smaller delay fluctuations during peak periods, or switch to a package that uses dedicated lines (node ​​names are often marked with IEPL/IPLC/dedicated lines).
  • Try several more for the same subscription: The quality difference between nodes in the same region can be very large. Test all the nodes in Hong Kong and choose ones with low and stable connection latency. Don't use any node to death.
  • The region selection is too far: In terms of physical distance, Japan, Hong Kong, and Singapore are generally better for mainland users than the United States and Europe. The "U.S. Large Bandwidth" node can run large files, but the daily browsing experience is often not as good as that of nearby medium-sized nodes.
  • Change the port and try again: There are situations where the link where a certain port is located is speed-limited. If the service provider provides multiple ports/transit entrances for the same node, sometimes changing one will have an immediate effect.

3The impact of protocols and transmission methods

For the same server, the speed of different transmission methods can differ several times:

  • WS + TLS + CDN transit: One more hop to a CDN, which is more resistant to blockades but suffers from reduced latency and speed. It is a life-saving option when the line is severely interfered. Directly connected nodes are usually given priority.
  • TCP / Reality Direct connection: It has low overhead and is generally the fastest among the same servers.
  • Packet loss line test Hysteria2: It is based on UDP, has aggressive packet loss resistance, and significantly improves speed in environments with large packet loss during evening peak hours. If there are Hy2 nodes in your subscription, go there and compare during peak periods.

4Confirm that domestic traffic is not detoured

If you feel that "even domestic websites are slow after turning on the proxy", check whether the routing at the bottom of the main interface is global - in global mode, domestic websites also bypass foreign countries, which is naturally slow. For daily AFK use "Bypassing the Continent", direct connection at home and agency abroad, no delay on either side. For the principle and setting of shunt, see Routing rules tutorial.

Troubleshooting path: segment by segment from local to node
local broadband Disconnection test fast.com Change node comparison Test more in the same area Change protocol/port Hy2 · Reality Still slow to find a service provider Problems with the line itself
Step by step: there is no problem locally → horizontal comparison between nodes → protocol port adjustment → if it doesn't work, it's time to change the line.

5Local Factors Quick Checklist

  • Is the laptop connected to 2.4G WiFi? Change the 5G frequency band or plug in the network cable. If the wireless environment is poor, the local speed will be lost.
  • Are there downloaders, network disks, and Windows updates running in the background? Once the upstream is full, all requests will be slow.
  • Is there any other proxy plug-in installed in the browser? The superposition of two layers of proxies will cause various strange phenomena, so disable them first during testing.
  • If the router has not been restarted for a long time, it will become overheated and slow down inexplicably, so you might as well rule it out.

6reasonable expectations

Finally, let's be honest: client settings can only "not hold back", and the speed limit is always determined by node bandwidth and line quality. If the same node is slow on both mobile phones and computers, changing the settings will be useless—it's time to report it to the service provider or change the line.

Download v2rayN (Windows version)v7.22.6 · Support x64 / ARM64 · Open source and free