Article

How to Test Your Website from China Without Flying There

September 28, 2026

Your Shanghai colleague says the site is slow. That is a complaint, not a measurement. Before you open a budget conversation with your hosting provider or start rewriting DNS records, you need numbers — first-render time, blocked dependencies, DNS resolution path, and CDN edge location — collected from a mainland vantage point.

This article gives you the procedure to test your website from China — four tests, run from mainland China, classified into two failure modes, with benchmarks you can defend in a planning meeting. No flights required.

What You Are Testing For: Four Measurements

First-render time and TTFB from a mainland vantage

The first question is quantitative: how long does the page take to render for a visitor on a mainland connection? Open the page and record two numbers — the time until visible content appears (first render) and the time until the server sends its first byte (TTFB).

Global-only sites commonly take 15–30+ s to load in China. TTFB from China runs 2–8+ s on a global-only setup, compared with under 1 s with mainland hosting and tuning. If your numbers match the first pattern, the cause is transit and offshore origin — the cross-border hop adds latency to every request. For the underlying causes, see why your website is slow in China.

Blocked third-party dependencies

Open the browser's network tab and list every third-party domain the page calls. Note which requests time out or return errors. Google Maps, YouTube, and Vimeo embeds fail or time out for mainland visitors — the result is blank map tiles and dead video players. Font hosts, icon libraries, tag managers, and auth or payment APIs can all fail. A dependency audit maps which flows break. For the per-dependency replacement paths, see the blocked-API playbook.

DNS resolution location

Run a DNS lookup for your domain. Check where your nameservers resolve. Nameservers outside China add lookup round trips on every fresh connection. If the authoritative answer comes from a server in Virginia or Frankfurt, mainland resolvers must cross the border just to learn your IP address.

CDN edge presence

Check whether your CDN serves content from nodes inside mainland China. Offshore CDN edge nodes do not cut the cross-border hop. A CDN that terminates in Hong Kong, Tokyo, or Los Angeles still routes every request through an international transit link. The edge must be inside the mainland to remove that hop. What a mainland edge requires — and why the filing gates it — is the CDN glossary entry. Weighing a Hong Kong origin against a mainland one? See Hong Kong server vs mainland server — what changes and what does not.

Test Your Website from China Without a Mainland Office

The colleague method

The simplest vantage: a colleague on a mainland connection. Ask them to open your site, record the first-render time, and capture a HAR file or network-tab screenshot. This gives you a real-user data point from inside China. It is manual, but it costs nothing and it is real.

Mainland test-point services

Four services provide browser-accessible test points inside mainland China. Each lets you enter a URL and receive timing data from multiple vantage points.

boce.com offers a website speed test, Ping, DNS test, IPv6 test, ICP filing query, and Whois. Node coverage: "large numbers of high-performance nodes inside and outside China."

17ce.com provides real-time website speed tests, CDN tests, PING, DNS, HTTP, TRACEROUTE, and DIG. Monitoring points cover every domestic province and abroad, with line filters for China Telecom, China Unicom, China Mobile, Great Wall Broadband, and CERNET.

ping.chinaz.com lets you ping a server from multiple locations to check response speed. The page offers Telecom, Unicom, Mobile, and multi-line filters. Request-frequency limits are tiered across guest, member, and VIP access levels.

itdog.cn offers multi-location ping, tcping, website and API speed tests, traceroute, online MTR, and DNS queries. Its node pool includes paid residential home-broadband vantage points.

Verify your monitoring vendor's node list

Before you rely on a global monitoring vendor for China testing, check its public node list. Datadog, Uptrends, and Checkly all publish theirs, and none of the three lists includes a mainland-China vantage point — Checkly lists Hong Kong only. If mainland China is absent from the list, the tool cannot measure what your mainland visitors experience.

Testing whether your site is blocked

GreatFire, an organization that has fought censorship since 2011, uses a simple methodology: compare access from outside China against access from inside. If the site loads from outside but fails from inside, it is labeled blocked. This is a binary test — "is the domain unreachable?" — not a latency diagnosis.

ISP-line variance

China's three major carriers — Telecom, Unicom, and Mobile — route traffic differently. A site that loads acceptably on one carrier may time out on another. When your test tool offers carrier-line filters, run the test on each line and record results separately. Do not average across carriers.

What to record per run

For each test run, record:

• Timestamp — conditions change over time
• Network type — Wi-Fi, 4G, wired; carrier if known
• First-render time — seconds until visible content appears
• TTFB — seconds until first byte from server
• Timed-out domains — list every third-party domain that failed
• DNS resolution location — whether your nameservers answer from inside or outside China
• CDN edge location — which node served the content

Reading Your Results: Blocked or Just Slow?

Two failure classes cover most findings.

Everything is slow. The page loads, but takes 15–30+ seconds. All requests eventually complete — just late. This is a transit problem: your origin sits offshore, and every byte crosses the international link.

Specific parts are missing. The page renders partially — blank map tiles, dead video players, system-default fonts. Some third-party calls never complete. This is a blocked-dependency problem. The domain is unreachable from mainland China regardless of origin speed.

Benchmark table

From Symptom to Fix: A Decision Matrix

The four measurements produce findings. The matrix below maps eight common symptoms to the likely cause, the test that confirms it, and the fix path. Every cell traces back to the measurement procedure above — no new numbers, just the routing logic.

Note: one run is a snapshot. Re-run the four tests after every infrastructure change, new third-party integration, or DNS modification. Map findings to the first six items of the 10-point China readiness diagnostic.

What to Do with the Results

Transit findings → mainland hosting. If your numbers match the global-only pattern, the next step is an infrastructure assessment. Mainland hosting on Alibaba Cloud or Tencent Cloud, with a CDN that terminates inside China, removes the cross-border hop. What a mainland CDN requires first is its own checklist. Our infrastructure service covers the architecture.

Blocked findings → dependency audit. If specific domains time out, identify every external script, API, font, and embed your site calls. Map which ones fail behind the firewall. Replace them with mainland-accessible alternatives, proxy them through a mainland-reachable intermediary, or self-host the assets. The infrastructure service includes dependency audit.

When the timed-out list includes payment gateways, that finding usually becomes a payments decision of its own. See WeChat Pay for foreign companies for the acceptance paths.

Compliance inventory → ICP filing check. If mainland hosting is indicated, check who holds the ICP filing. A mainland-hosted site requires an ICP filing (Bei'an) on a mainland-registered entity. Filing typically takes 2–4 weeks. See the ICP filing timeline for the process. Our ICP & compliance service runs the filing end to end.

Make It Repeatable

One test run is a snapshot. A measurement cadence catches regressions. Re-run the four tests after every infrastructure change, new third-party integration, or DNS modification.

Map your findings to the first six items of the 10-point China readiness diagnostic:

1. Does your site take 15 seconds or more to first render from a mainland connection?
2. Is the origin your China visitors hit hosted outside mainland China?
3. Does your CDN serve China visitors from edge nodes outside the mainland?
4. Do your domains resolve through nameservers outside China?
5. Do you embed Google Maps, YouTube, or Vimeo?
6. Do login, checkout, chat, fonts, or tag-manager flows call endpoints that time out from China?

If items 1–6 return "yes," your visitors have a materially worse experience than your analytics suggest. Items 9–10 on the diagnostic are launch gates — ICP filing and entity requirements — and should be addressed in parallel.

FAQ: Testing your website from China

Next steps

Testing tells you what is wrong. Fixing it requires the right infrastructure, the right dependency choices, and the right compliance posture.

• Start with the 10-point China readiness diagnostic to score your current position across all ten readiness items.
• If your findings point to transit or CDN gaps, our infrastructure service covers mainland hosting, CDN architecture, and dependency audit.
• Email hello@chinagateway.pro with your test results. We will tell you which findings are fixable in weeks and which require a structural change.