Which parts of your stack break first in China
Fonts, captcha, auth, analytics — the dependency failures we see most, ranked by impact.
Most teams assume “China access” is one big switch. It isn’t. A site that loads perfectly from London can fail in a dozen small, independent ways from Shanghai — and the failures rarely announce themselves. They show up as a blank login button, a hero section with no typeface, or a checkout that silently stalls.
After running these checks across dozens of products, the same dependencies break first, in roughly this order of impact.
1. Web fonts and icon kits
Google Fonts and many icon CDNs are unreachable or throttled from the mainland. The page still renders, but with fallback type and missing glyphs — the most common “looks broken” report we receive.
2. Auth and identity widgets
Social login buttons, hosted auth widgets, and bot-protection challenges that phone home to blocked domains will hang. Users see a spinner that never resolves.
3. Analytics and tag managers
Blocked analytics scripts are usually loaded synchronously near the top of the page. When they time out, everything below them is delayed.
4. Maps, media, and embeds
Embedded video players, map tiles, and third-party widgets are frequent silent failures — present in the DOM, blank on screen.
The fix is almost never “move everything to China.” It is identifying the specific dependencies that fail and replacing only those. That is what a readiness assessment measures before you commit to any hosting route.
