[{"data":1,"prerenderedAt":247},["ShallowReactive",2],{"blog:vpn-slow-speed-fixes":3},{"zh-CN":4,"en":132},{"blocks":5,"faq":116},[6,9,11,15,17,24,26,29,31,64,66,68,71,82,85,87,89,91,94,96,100,102,105,107,109,112,114],{"type":7,"html":8},"p","VPN 显示已连接，网页也能打开，但下载慢、视频一直转圈——这种「慢」和「连不上」是两种完全不同的故障，原因也不重叠。连不上通常是 DNS、分流规则这一类问题；慢，几乎总是这六个地方之一，而且往往不止一个原因叠在一起。",{"type":7,"html":10},"按从最常见到最少见的顺序查一遍，比反复换节点、卸载重装快得多。原则也不变：每次只改一个变量，同时换节点又换设备又换网络，问题消失了也不知道是哪一步起的作用，下次遇到还是要从头再来一遍。",{"type":12,"id":13,"html":14},"h2","bp-triage","先做三十秒基准测试",{"type":7,"html":16},"打开测速工具，测三次：不连 VPN 直连一次，连上以后测两个不同地区的节点各一次。结果对应四种情况，指向完全不同的方向。",{"type":18,"items":19},"list",[20,21,22,23],"直连也慢，VPN 也慢：问题在本机网络，和 VPN 没关系，先看 Wi-Fi 信号或流量套餐。","直连快，两个节点都同样慢：更可能是设备处理能力或者当前时段整体拥堵，不是单个节点的问题。","直连快，节点 A 慢、节点 B 快：节点 A 当时拥堵，换掉就好，不需要再查别的。","三次都快，只是某个具体操作卡（比如某个网站加载慢）：问题可能出在那个网站或服务本身，不是网络。",{"type":7,"html":25},"这一步不能跳，跳过去，后面查哪一项都是在猜。三次测试花不了一分钟，但能直接把六个排查点砍掉一半，剩下的才值得逐条细查。",{"type":12,"id":27,"html":28},"bp-six-checks","最该先查的六个地方",{"type":7,"html":30},"六个地方按常见程度从高到低排列，先查表格靠前的几项，命中率更高。",{"type":32,"align":33,"head":35,"rows":39},"table",[34,34,34],null,[36,37,38],"排查点","怎么快速判断","怎么处理",[40,44,48,52,56,60],[41,42,43],"节点当时拥堵","同一时间换另一个地区的节点，速度明显不同","换一个不同地区的节点，别在同一地区来回换",[45,46,47],"选节点没经过对比","一直用默认节点，从没测过其他选项","用免费试用把两三个候选节点都测一遍，选相对稳的",[49,50,51],"本机网络信号弱","断开 VPN 直连也慢","先解决本机网络：换 Wi-Fi、靠近路由器，或者切换到移动数据",[53,54,55],"后台程序抢带宽","同时在下载、自动更新或云同步","暂停其他下载任务，只留正在用的那一个",[57,58,59],"晚高峰限速","每天固定时间段变慢，白天基本正常","避开高峰时段，或提前把大文件下载完",[61,62,63],"设备处理跟不上","换一台新设备测同一条线路明显更快","关掉其他吃资源的 App，或者接受这是设备瓶颈而不是线路问题",{"type":7,"html":65},"前两项加起来占了大多数「时不时就慢」的情况，值得优先排查。表格越往下越少见，不代表完全不会发生，只是排查顺序应该按概率来，不该每次都从最麻烦的那项查起。",{"type":7,"html":67},"有一个简单的判断习惯：如果换了节点立刻见效，别再往下查，问题已经解决了；如果换了两三个节点都没用，才值得往表格下方走，去看本机网络、后台程序和设备本身。倒着查的效率通常更低，因为设备和后台这两项相对少见，先查它们大概率是白费功夫。",{"type":12,"id":69,"html":70},"bp-switch-node","换节点是最快的一步",{"type":72,"items":73},"steps",[74,78],{"title":75,"body":76},"怎么确认是节点的问题",[77],"按三十秒基准测试的结果，如果直连快、某个节点明显慢，问题基本可以锁定在那个节点或者它所在的线路上。这种情况最容易辨认，也是六项里占比最高的一种，值得作为默认的第一反应。",{"title":38,"body":79},[80,81],"换一个不同地区的节点，而不是同地区内换来换去——同地区的出口经常共享上游资源，一起拥堵的概率不低。换完立刻恢复正常，就不需要再动其他设置了。","值得养成的习惯是：拿到免费试用之后，先把两三个常用地区的节点都测一遍，记住哪个平时比较稳，而不是等到卡顿了才现场着急换。日常稳定的那个节点未必是延迟数字最低的，而是在不同时间段测下来波动最小的那个，这个信息只有自己多测几次才知道，别人的推荐参考意义有限。",{"type":12,"id":83,"html":84},"bp-peak-hour","晚高峰变慢，很多时候是运营商在动手",{"type":7,"html":86},"如果慢的时间点很固定，基本都在晚上八点到十一点之间，白天用起来正常，这种模式指向的不是节点，而是那个时间段本身：一是同时在线人数变多，线路负载升高；二是部分运营商会在高峰期对识别出的加密流量做限速，这属于运营商网络层面的策略，换节点、换设备都绕不开。",{"type":7,"html":88},"这种情况能做的更多是错峰：大文件、更新包提前在白天下好，晚高峰只做对速度要求不高的事情。也可以试试换到一个当下使用人数相对少的地区节点，效果因人而异，不一定每次都管用，但代价很低，值得作为第一反应先试一下。更完整的时间规律和数据，见\u003Ca href=\"\u002Fblog\u002Fslow-at-night-peak-hours\u002F\">为什么一到晚上就变慢\u003C\u002Fa>。",{"type":90},"downloads",{"type":12,"id":92,"html":93},"bp-overlooked","容易被忽略的两个细节",{"type":7,"html":95},"前面六项查完，多数「慢」都能找到原因。但还有两个小地方经常被忽略，单独看都不严重，混在一起排查却很容易被误判成「线路不行」。",{"type":18,"items":97},[98,99],"首次打开一个网页比后续刷新慢一截，很多时候是域名解析（DNS）本身耗时，不是线路慢——第一次访问要先查到地址，之后一段时间会用缓存的结果，速度自然不一样。\u003Ca href=\"\u002Fblog\u002Fwhat-is-dns\u002F\">DNS 是什么\u003C\u002Fa>讲了这一层具体在做什么。","老设备处理加密流量更吃力，尤其是用了三四年以上的手机。同一条线路，新设备可能完全感觉不到卡顿，老设备却很明显，这是处理器跟不上，不是线路的问题，换节点也不会有变化。",{"type":7,"html":101},"分清楚这两点之后，再遇到「偶尔卡一下」的情况，就不用每次都从头怀疑节点或者账号了，很多时候等一下、刷新一次就过去了。",{"type":12,"id":103,"html":104},"bp-mismatch","测速数字和体感不一致时",{"type":7,"html":106},"有时候测速跑出来的数字挺好看，几十兆的下行，但看视频依然卡、网页依然慢。这通常不是测速软件在说谎，而是它测的和你实际在做的不是同一件事——测速多数考验的是持续下载大文件的能力，视频和网页更依赖延迟和小文件的连续响应速度。两者不匹配的具体原因，见\u003Ca href=\"\u002Fblog\u002Fwhy-speed-test-looks-wrong\u002F\">测速数字好看，实际却很卡\u003C\u002Fa>。",{"type":7,"html":108},"遇到这种情况，别只盯着测速 App 的数字，直接测你真正要用的那个场景——打开常看的视频网站，看它多久缓冲一次，比一次性下载测试更贴近实际体验。如果测速数字一直很好看，体感却持续很差，值得怀疑测的根本不是同一条线路，比如测速走的是某个专门优化过的节点，日常用的却是另一个，这种情况换回同一个节点测才有意义。",{"type":12,"id":110,"html":111},"bp-final","总结",{"type":7,"html":113},"VPN 慢下来，按节点拥堵、选节点没对比、本机网络、后台占用、晚高峰限速、设备本身这六项从前往后查，配合开头的三十秒基准测试，大多数情况能在几分钟内定位。记住每次只改一个变量，换完一样再测一次，而不是把节点、设备、时间一起换。",{"type":7,"html":115},"想少一点这类排查，方向就是让客户端自己处理好节点选择和连接质量，而不是每次卡顿都靠自己一项项手动核对。\u003Ca href=\"\u002Ffeatures\u002F\">快橙\u003C\u002Fa>一键连接，换节点也是点一下就行，不需要手动改设置，注册后每天有免费试用时长，可以直接拿它把上面六项过一遍，找到当前环境下最稳的那个节点。如果连续几天同一地区都偏慢，直接找\u003Ca href=\"\u002Fcontact\u002F\">客服\u003C\u002Fa>反馈会比自己每天重复测试更省事，也更容易得到针对那条线路的具体答复。",[117,120,123,126,129],{"q":118,"a":119},"换了好几个节点都还是慢，说明什么？","说明问题大概率不在某一个节点，而是本机网络、时间段或者设备本身。换节点是第一步该试的，但不是唯一一步，六个地方没查完之前别急着下结论。",{"q":121,"a":122},"测速软件显示的数字能代表实际体验吗？","不完全能。测速跑的是一次性大文件下载，看视频、刷网页考验的是延迟和小文件的连续加载，两者不是一回事，具体差异见\u003Ca href=\"\u002Fblog\u002Fwhy-speed-test-looks-wrong\u002F\">测速数字好看，实际却很卡\u003C\u002Fa>。",{"q":124,"a":125},"老手机用 VPN 会更容易卡吗？","会。客户端要处理加密和解密，老设备的处理器跑起来更吃力，同样一条线路，新旧设备的体感速度可能不一样。",{"q":127,"a":128},"为什么一到晚上就明显变慢？","多数情况是晚高峰用户集中、线路负载升高，运营商也可能在这段时间对识别出的加密流量限速。详细规律见\u003Ca href=\"\u002Fblog\u002Fslow-at-night-peak-hours\u002F\">为什么一到晚上就变慢\u003C\u002Fa>。",{"q":130,"a":131},"免费试用能测出真实速度吗？","能。用当天的试用时长在早晚各测一次，比只测一次更能反映真实情况，晚高峰那一次尤其有参考价值。",{"blocks":133,"faq":231},[134,136,138,140,142,148,150,152,154,185,187,189,191,202,204,206,208,209,211,213,217,219,221,223,225,227,229],{"type":7,"html":135},"The icon says connected, pages open fine, but downloads crawl and video keeps spinning — that kind of "slow" is a completely different failure from "will not connect," with causes that barely overlap. A failure to connect is usually DNS or a routing rule; slow almost always comes down to one of six things, and often more than one stacked together.",{"type":7,"html":137},"Working through them most-common-first beats switching nodes over and over or reinstalling the app. The rule stays the same here too: change one variable at a time. Change the node, the device and the network all at once, and even if the problem goes away you will not know what actually fixed it, so next time starts from zero again.",{"type":12,"id":13,"html":139},"Start with a thirty-second baseline test",{"type":7,"html":141},"Open a speed test and run it three times: once with the VPN off, then once each on two different node regions. The result lands in one of four buckets, and each points somewhere different.",{"type":18,"items":143},[144,145,146,147],"Both direct and through the VPN are slow: the problem is your local network, nothing to do with the VPN. Check Wi-Fi signal or your data plan first.","Direct is fast, both nodes are equally slow: more likely the device's processing power or general congestion at that moment, not one specific node.","Direct is fast, node A is slow, node B is fast: node A was congested at that moment. Switch and move on, nothing else to check.","All three are fast, but one specific thing lags (a particular site loads slowly): the problem is probably that site or service, not the network.",{"type":7,"html":149},"Do not skip this step. Skip it, and everything that follows is a guess. The three tests take under a minute and immediately cut the six suspects in half, leaving only the ones actually worth chasing.",{"type":12,"id":27,"html":151},"The six places to check first",{"type":7,"html":153},"The six are ranked roughly by how often each one turns out to be the cause. Work down the table: the top rows have a much higher hit rate.",{"type":32,"align":155,"head":156,"rows":160},[34,34,34],[157,158,159],"Where to look","How to tell quickly","What to do",[161,165,169,173,177,181],[162,163,164],"The node is congested right now","Switch to a node in a different region at the same moment and speed clearly changes","Pick a node in a different region rather than swapping within the same one",[166,167,168],"The node was never actually tested","You have always used the default node and never compared it to anything else","Use free trial time to test two or three candidate nodes and keep the steadiest one",[170,171,172],"Weak local signal","Disconnecting the VPN and going direct is also slow","Fix the local network first: switch Wi-Fi, get closer to the router, or try mobile data",[174,175,176],"Something else is using the bandwidth","A download, an auto-update or a cloud sync is running at the same time","Pause other downloads and leave only the one you actually need",[178,179,180],"Peak-hour throttling","Slow at the same time every day, fine during the day","Avoid peak hours, or finish large downloads earlier",[182,183,184],"The device cannot keep up","The same route is noticeably faster on a newer device","Close other resource-heavy apps, or accept this is a device limit, not a route problem",{"type":7,"html":186},"The top two rows account for most "randomly slow sometimes" cases, and are worth checking first. Rows further down are rarer, not impossible — the order reflects likelihood, not a rule that you must exhaust the top of the list first every single time.",{"type":7,"html":188},"One simple habit: if switching the node fixes it right away, stop there: it is solved. If two or three different nodes all fail to help, that is when it is worth moving further down the table to your own network, background apps and the device itself. Working the list backwards is usually a waste of time, since the device and background-app rows are comparatively rare.",{"type":12,"id":69,"html":190},"Switching nodes is the fastest fix",{"type":72,"items":192},[193,197],{"title":194,"body":195},"How to confirm it is the node",[196],"Going by the baseline test above, if direct is fast and one specific node is clearly slow, the problem can usually be pinned on that node or the route it sits on. This is the easiest case to recognise and the single most common of the six — treat it as the default first guess.",{"title":198,"body":199},"How to fix it",[200,201],"Pick a node in a different region rather than swapping within the same one — exits in the same region often share upstream capacity, so they tend to get congested together. If switching fixes it immediately, nothing else needs touching.","A habit worth building: once you have free trial time, test two or three regions you actually use and remember which one tends to hold up. The steadiest node day to day is not necessarily the one with the lowest latency number on a single test — it is the one whose numbers barely move across different times of day, and that only shows up after testing it yourself a few times. Someone else's recommendation is not much use here.",{"type":12,"id":83,"html":203},"Slowdowns at peak hours are often the carrier's doing",{"type":7,"html":205},"If the slow window is consistent — roughly the same hours every evening, fine during the day — that pattern points at the time of day itself rather than the node: more people online at once raises load on the route, and some carriers throttle traffic they can identify as encrypted specifically during peak hours. That is a carrier-network-level policy, and no amount of switching nodes or devices gets around it.",{"type":7,"html":207},"The realistic move here is to shift the timing: download large files and updates earlier in the day, and save peak hours for things that do not need much speed. Switching to a node in a region with fewer people online at that moment is also worth a quick try; it does not always help, but it costs nothing to test. For the fuller pattern and the numbers behind it, see \u003Ca href=\"\u002Fen\u002Fblog\u002Fslow-at-night-peak-hours\u002F\">Why it gets slower every night\u003C\u002Fa>.",{"type":90},{"type":12,"id":92,"html":210},"Two details that are easy to overlook",{"type":7,"html":212},"Work through the six above and most slowness gets explained. Two smaller things still slip through, though, and neither is serious on its own; mixed in with everything else, they get misread as "the route is bad."",{"type":18,"items":214},[215,216],"The very first time you open a page is slower than every refresh after it, and that is often DNS lookup time, not the route — the first visit has to resolve the address, and a cached result speeds up everything after it. \u003Ca href=\"\u002Fen\u002Fblog\u002Fwhat-is-dns\u002F\">What DNS is\u003C\u002Fa> covers what is actually happening at this layer.","Older devices work harder to keep up with encrypted traffic, especially phones three or four years old or more. On the exact same route a newer device may not notice any lag at all while an older one clearly does, and that is the processor falling behind, not the route. Switching nodes will not change it.",{"type":7,"html":218},"Once these two are separated out, an occasional single stutter stops looking like something to re-investigate from scratch every time; often it just needs a moment and a refresh.",{"type":12,"id":103,"html":220},"When the number and the feel do not match",{"type":7,"html":222},"Sometimes the speed test comes back with a great number, tens of megabits down, and video still buffers, pages still feel slow. That is usually not the speed test lying — it is testing something different from what you are actually doing. A speed test mostly measures sustained large-file download; video and browsing depend more on latency and a steady stream of small responses. \u003Ca href=\"\u002Fen\u002Fblog\u002Fwhy-speed-test-looks-wrong\u002F\">Why the speed test looks fine but it still feels slow\u003C\u002Fa> covers exactly why the two diverge.",{"type":7,"html":224},"When this happens, stop watching the number in the speed test app and test the actual thing you use: open the video site you actually watch and see how often it buffers, which tracks real experience far better than a one-shot download test. If the number stays great while the feel stays bad over time, it is worth suspecting the test is not even hitting the same route you use day to day; a speed test sometimes runs through a specially optimised node while daily use goes through another one, in which case testing the same node you actually use is the only comparison that means anything.",{"type":12,"id":110,"html":226},"In summary",{"type":7,"html":228},"When a VPN slows down, work front to back through node congestion, an untested node, your own network, background apps, peak-hour throttling and the device itself, backed by the thirty-second baseline test at the top — most cases get located within a few minutes that way. Change one variable at a time and retest before changing the next one, instead of swapping the node, the device and the time of day all together.",{"type":7,"html":230},"The way to run into this less often is to let the client handle node selection and connection quality itself, instead of manually checking each item every time something lags. \u003Ca href=\"\u002Fen\u002Ffeatures\u002F\">FastOrange\u003C\u002Fa> connects in one tap, and switching nodes is just as quick, with nothing to configure by hand. Every registered account gets free trial time daily, which is enough to run through all six checks above and find the steadiest node for where you are right now. If the same region stays slow for several days running, reporting it to \u003Ca href=\"\u002Fen\u002Fcontact\u002F\">support\u003C\u002Fa> directly saves more time than re-testing it yourself every day, and gets you an answer specific to that route.",[232,235,238,241,244],{"q":233,"a":234},"I have tried several nodes and it is still slow. What does that mean?","It means the problem is probably not any single node, but your local network, the time of day, or the device itself. Switching nodes is the first thing to try, not the only thing. Do not conclude anything until you have worked through all six.",{"q":236,"a":237},"Can I trust the numbers a speed test app shows me?","Not entirely. A speed test runs one continuous large download; watching video or browsing depends more on latency and a steady stream of small responses. They are not the same test. See \u003Ca href=\"\u002Fen\u002Fblog\u002Fwhy-speed-test-looks-wrong\u002F\">Why the speed test looks fine but it still feels slow\u003C\u002Fa> for the details.",{"q":239,"a":240},"Does an older phone make a VPN feel slower?","Yes. The client has to encrypt and decrypt everything, and an older processor works harder to keep up. On the exact same route, an old and a new device can feel noticeably different.",{"q":242,"a":243},"Why does it get noticeably slower every night?","Usually because more people are online at once and the route gets busier, and some carriers throttle traffic they can identify as encrypted during peak hours. \u003Ca href=\"\u002Fen\u002Fblog\u002Fslow-at-night-peak-hours\u002F\">Why it gets slower every night\u003C\u002Fa> goes into the pattern in more detail.",{"q":245,"a":246},"Can the free trial actually show me real speed?","Yes. Testing once in the morning and once in the evening with that day's trial time tells you more than a single test, and the evening one — peak hours — is the most informative of the two.",1793276291384]