A site that loads in one second in Europe or the US can take five seconds, or time out, for visitors in mainland China. The causes are well understood: congested international links at peak times, routing through busy carrier backbones, and third-party resources that are slow or blocked in China. Here’s a practical checklist for faster access from China, without hosting inside the country.

Why it’s slow

  1. Cross-border capacity. Traffic between China and the rest of the world passes through a limited number of international gateways. In the evening (around 20:00–23:00 Beijing time), standard routes congest, and packet loss climbs.
  2. Carrier-specific routing. China Telecom, China Unicom and China Mobile each have their own international routes, with different quality. A server that’s fast for Telecom users may be slow for Mobile users. See CN2 GIA explained.
  3. Distance. Physics adds latency from far-away locations, but good routes from Hong Kong or Japan keep it low.
  4. Blocked or slow third parties. Google services (Fonts, reCAPTCHA, Analytics, Maps, YouTube), some CDNs, Facebook and Twitter widgets fail to load or time out, and they can block page rendering.

Measure first, from China

You need data from inside China, ideally from all three carriers, at peak hours:

  • online multi-location ping and HTTP testing services with nodes in Chinese cities;
  • a contact or user in China running mtr and browser DevTools;
  • real-user monitoring (RUM), so you see actual load times from Chinese visitors.

Look at latency, packet loss (more important), and which requests are slow or failing in the waterfall. See packet loss troubleshooting and ping and mtr.

Fix 1: choose the right location and route

Option Pros Cons
Hong Kong with China-optimised routes (CN2 / BGP) Lowest latency to South China, no ICP filing needed Route quality varies by provider. Bandwidth often costs more
Japan (Tokyo) with CN2 GIA Low latency, stable premium route, good for Asia overall Slightly higher latency than Hong Kong
US West Coast with CN2 GIA Larger bandwidth and resources for the price ~130–170 ms latency
Mainland China hosting Fastest inside China Requires ICP filing, a local entity, and Chinese regulations

VPS.DO offers Hong Kong VPS on CN2 + BGP and Japan VPS with CN2 GIA routing. Test from your users’ locations with the published test IPs before ordering. See Hong Kong VPS and Japan VPS.

Fix 2: remove blocked and slow third-party resources

Often the biggest improvement, and free:

  • Google Fonts: self-host fonts. See host fonts locally.
  • reCAPTCHA: use alternatives that work in China, or hCaptcha or Cloudflare Turnstile (test availability), or server-side protections.
  • Google Analytics / Tag Manager: load asynchronously, and make sure nothing render-blocking depends on them. Consider self-hosted analytics. See Umami analytics.
  • Embedded YouTube, Google Maps, social widgets: lazy-load them, show placeholders, or offer alternatives.
  • JavaScript libraries from public CDNs (e.g. Google-hosted jQuery): self-host them.

Check DevTools for requests that stay pending for many seconds. Those are your blockers.

Fix 3: reduce round trips and bytes

High latency multiplies the cost of every round trip:

  • HTTP/2 or HTTP/3, TLS 1.3, and connection reuse. See HTTP/1.1 vs 2 vs 3 and TLS configuration.
  • Fewer requests: bundle sensibly, inline critical CSS, and avoid long chains of dependent requests.
  • Compression (Brotli) and optimised images (WebP or AVIF, correct sizes). See Nginx gzip and Brotli.
  • Caching: long cache lifetimes for static assets, and page caching for dynamic sites. See website speed optimization.

Fix 4: tune the server for lossy paths

  • TCP BBR keeps throughput higher on paths with loss and long RTT. See TCP BBR.
  • Make sure MTU problems aren’t causing stalls. See MTU explained.

Fix 5: a CDN with China coverage

International CDNs vary widely in mainland China performance. Some have no PoPs there (traffic is served from Hong Kong or nearby). Chinese CDNs with local PoPs require ICP filing for your domain. For many sites, a well-located origin in Hong Kong or Japan on good routes, plus good front-end hygiene, beats a CDN that isn’t optimised for China.

Checklist

  • Measured from China at peak hours, across carriers
  • Server in Hong Kong or Japan, or on CN2 GIA routes
  • No Google Fonts, reCAPTCHA or other blocked resources on the critical path
  • HTTP/2 or 3, TLS 1.3, Brotli, image optimisation
  • BBR enabled
  • Real-user monitoring set up

Related: latency vs bandwidth and choosing a VPS location.

  • Networking
  • China
  • Performance