An article from Marketing to China argues that when an international website performs poorly in mainland China, two common explanations are cross-border network constraints and China's internet controls. For New Zealand and Australian businesses with digital channels central to their China strategy, that is a useful starting point. But in practice, the issue is often less about one single cause and more about how several technical and operational decisions interact.
A article from Marketing to China argues that when an international website performs poorly in mainland China, two common explanations are cross-border network constraints and China’s internet controls. That is a useful starting point. But in practice, the issue is often less about one single cause and more about how several technical and operational decisions interact.
For many businesses, the confusing part is that the website is not necessarily “down.” It may load partially, stall on certain elements, work inconsistently by city or network, or feel slow enough that users give up before the page is usable. That distinction matters, because the fix depends on what is actually failing.
It is not always a block. Sometimes it is an architecture problem.
One reason international websites struggle in mainland China is that traffic often has to cross network boundaries before it reaches the site’s server or supporting services. AWS explicitly describes architectures designed to keep China-origin traffic inside China in order to minimize latency and improve performance for users there. Cloudflare makes a similar point in its China Network documentation, which highlights in-mainland data centers and in-China authoritative DNS and nameservers to improve time to first byte.
That is why a website can work well in Europe, North America, or Southeast Asia and still feel unreliable from mainland China. The issue is not always that the entire site has been blocked. In many cases, the site is simply being delivered through an arrangement that was never designed for China-based traffic in the first place.
Hosting in mainland China can help - but it changes the compliance picture
This is where many companies need to slow down and separate performance decisions from compliance decisions.
If a business wants to host its website in mainland China, an ICP filing or recordal becomes part of the process. Alibaba Cloud states that if the resources used by a website or app are located in the Chinese mainland, filing is required, while resources located outside the Chinese mainland do not require filing. AWS China similarly states that websites providing non-commercial internet information services in its China regions must complete ICP recordal procedures, and that China-region accounts are separate from global AWS accounts. Alibaba Cloud also notes that once a filing is approved, the filing number must be added to the website.
That does not mean every international business should immediately migrate its site into mainland China. It does mean that “we should host locally for speed” is not just a technical choice. It can become a legal, operational, and administrative decision as well. For some businesses, that will be worthwhile. For others, a hybrid approach may be more realistic.
The overlooked problem is often third-party dependencies
A second issue is less visible but often just as important: external dependencies.
Google’s web performance documentation says third-party scripts can significantly affect load performance, and recommends keeping them off the critical rendering path where possible. Chrome’s developer documentation makes the same point, noting that third-party code can significantly impact page load performance.
This matters in any market. In mainland China, it matters more because a site may depend on multiple external services before the page can fully render. If some of those services are slow, unavailable, or poorly routed for mainland users, the whole website can appear broken even when the main server is technically reachable. The Marketing to China article points in this direction when it notes that a site may be online but still load poorly because of page weight and multiple components.
From a business standpoint, this is an important distinction. A company may think it has a “China access” problem, when in reality it has a dependency problem: fonts, maps, video embeds, analytics tools, tag managers, or other external assets are doing more damage than the main site itself.
A China-ready website is usually a system, not a translation exercise
It is also worth being realistic about what “optimising for China” involves.
Cloudflare’s China Network documentation makes clear that China delivery is not just about caching static files. It includes network, DNS, security, and compliance considerations, and Cloudflare also notes that not all products are available in its China Network. AWS’s guidance similarly describes separate China-region infrastructure, separate accounts, and routing patterns designed specifically to steer in-China traffic toward in-China endpoints.
In other words, a China-ready setup is usually architectural. It may involve local or partially local delivery, different DNS handling, fewer fragile third-party calls, and a clearer view of which parts of the stack need to work inside mainland China and which do not. That is a more useful way to think about the problem than simply asking whether a site is “blocked.”
Performance should be measured from the market you care about
Another practical point is measurement.
Google’s PageSpeed Insights documentation explains that the tool evaluates website performance using user-centric metrics. That is useful, but for China-facing decisions it is only part of the picture. If a business cares about mainland China users, it needs visibility into how the site behaves from that environment, not just how it performs from somewhere else. The Marketing to China article also stresses the importance of regular monitoring and performance testing for websites operating in China.
This is easy to underestimate. Teams often review a site from their own office, their own network, and their own devices, then assume the experience is broadly the same elsewhere. With China, that assumption can be expensive. A site can look fine internally and still create friction for actual users in-market.
What this means in practice
If an international website is slow or unreliable in mainland China, the most useful first step is usually not to jump straight to a rebuild. It is to diagnose the problem more carefully.
A sensible review usually starts with four questions:
Is China traffic being served entirely from outside mainland China?
Which third-party scripts or assets sit on the critical path?
Does the business actually need mainland hosting, and if so, is it prepared for ICP filing and related compliance steps?
Is the team measuring the website from the user’s real environment, or only from overseas?
Key takeaway
The main lesson is simple: a website that feels blocked or broken in China is not always suffering from one dramatic failure. Quite often, it is the result of ordinary web decisions made for global traffic that do not hold up well under China-specific conditions.
That is why the most useful response is usually not a quick assumption, but a more disciplined diagnosis. Businesses that separate network design, compliance requirements, and third-party dependency issues tend to get to a clearer answer faster - including the answer that no full mainland rebuild is needed.
A practical audit approach: where to start
For NZ and AU businesses that want to assess why their website is underperforming for China-based users, a structured audit is more useful than a general optimisation project. The audit should answer four questions in sequence.
First: is China traffic being served entirely from infrastructure outside mainland China? If the web server, CDN, and supporting services are all hosted outside China, the site is being delivered across cross-border network boundaries for every user in mainland China. This is the most common root cause of slow or unreliable performance in the market.
Second: which third-party scripts or assets are on the critical rendering path? A site that loads quickly in New Zealand or Australia but includes external calls to Google Analytics, Google Fonts, YouTube embeds, Facebook scripts, or other blocked or slow-loading services will stall for mainland China users before those calls resolve. A technical audit that maps all third-party dependencies and tests whether they load from within mainland China is the most direct way to identify these blocking elements.
Third: does the site require a mainland China hosting arrangement - and if so, is the business prepared for ICP filing requirements? An ICP recordal is required for websites hosted on servers in mainland China. This is an administrative process managed through the hosting provider, but it has a processing timeline and ongoing maintenance requirements that should be factored into the architecture decision.
Fourth: is the business measuring website performance from within mainland China rather than from the home market? A site that appears fast and functional from a New Zealand or Australian office can perform poorly for mainland users without anyone in the business being aware of it. Available tools for China-specific performance testing include web performance monitoring services with mainland China probe locations, which can provide a reasonable proxy for the user experience from within the market.
Implementation options and practical trade-offs
There is no universal answer to how a NZ or AU business should address poor China website performance. The appropriate approach depends on the site's architecture, the nature of the traffic being served, and the compliance obligations that apply to the business's China market activities.
For businesses whose China activity is primarily B2B - using the website for supplier credibility and buyer communication rather than direct consumer engagement - a lightweight, third-party-clean landing page optimised for mainland China performance may be the most practical solution, without requiring a full mainland hosting arrangement.
For businesses running direct-to-consumer e-commerce with significant China-based traffic, a more comprehensive approach - including CDN infrastructure with mainland China points of presence, or a China-specific hosting arrangement with ICP recordal - is likely necessary to deliver the user experience that Chinese consumers expect.
In both cases, the most common improvement with the lowest implementation cost is identifying and removing blocking third-party dependencies from the critical rendering path. This alone can produce a meaningful improvement in perceived performance for mainland China users without requiring architectural changes or compliance decisions.
A article from Marketing to China argues that when an international website performs poorly in mainland China, two common explanations are cross-border network constraints and China’s internet controls. That is a useful starting point. But in practice, the issue is often less about one single cause and more about how several technical and operational decisions interact.
For many businesses, the confusing part is that the website is not necessarily “down.” It may load partially, stall on certain elements, work inconsistently by city or network, or feel slow enough that users give up before the page is usable. That distinction matters, because the fix depends on what is actually failing.
It is not always a block. Sometimes it is an architecture problem.
One reason international websites struggle in mainland China is that traffic often has to cross network boundaries before it reaches the site’s server or supporting services. AWS explicitly describes architectures designed to keep China-origin traffic inside China in order to minimize latency and improve performance for users there. Cloudflare makes a similar point in its China Network documentation, which highlights in-mainland data centers and in-China authoritative DNS and nameservers to improve time to first byte.
That is why a website can work well in Europe, North America, or Southeast Asia and still feel unreliable from mainland China. The issue is not always that the entire site has been blocked. In many cases, the site is simply being delivered through an arrangement that was never designed for China-based traffic in the first place.
Hosting in mainland China can help - but it changes the compliance picture
This is where many companies need to slow down and separate performance decisions from compliance decisions.
If a business wants to host its website in mainland China, an ICP filing or recordal becomes part of the process. Alibaba Cloud states that if the resources used by a website or app are located in the Chinese mainland, filing is required, while resources located outside the Chinese mainland do not require filing. AWS China similarly states that websites providing non-commercial internet information services in its China regions must complete ICP recordal procedures, and that China-region accounts are separate from global AWS accounts. Alibaba Cloud also notes that once a filing is approved, the filing number must be added to the website.
That does not mean every international business should immediately migrate its site into mainland China. It does mean that “we should host locally for speed” is not just a technical choice. It can become a legal, operational, and administrative decision as well. For some businesses, that will be worthwhile. For others, a hybrid approach may be more realistic.
The overlooked problem is often third-party dependencies
A second issue is less visible but often just as important: external dependencies.
Google’s web performance documentation says third-party scripts can significantly affect load performance, and recommends keeping them off the critical rendering path where possible. Chrome’s developer documentation makes the same point, noting that third-party code can significantly impact page load performance.
This matters in any market. In mainland China, it matters more because a site may depend on multiple external services before the page can fully render. If some of those services are slow, unavailable, or poorly routed for mainland users, the whole website can appear broken even when the main server is technically reachable. The Marketing to China article points in this direction when it notes that a site may be online but still load poorly because of page weight and multiple components.
From a business standpoint, this is an important distinction. A company may think it has a “China access” problem, when in reality it has a dependency problem: fonts, maps, video embeds, analytics tools, tag managers, or other external assets are doing more damage than the main site itself.
A China-ready website is usually a system, not a translation exercise
It is also worth being realistic about what “optimising for China” involves.
Cloudflare’s China Network documentation makes clear that China delivery is not just about caching static files. It includes network, DNS, security, and compliance considerations, and Cloudflare also notes that not all products are available in its China Network. AWS’s guidance similarly describes separate China-region infrastructure, separate accounts, and routing patterns designed specifically to steer in-China traffic toward in-China endpoints.
In other words, a China-ready setup is usually architectural. It may involve local or partially local delivery, different DNS handling, fewer fragile third-party calls, and a clearer view of which parts of the stack need to work inside mainland China and which do not. That is a more useful way to think about the problem than simply asking whether a site is “blocked.”
Performance should be measured from the market you care about
Another practical point is measurement.
Google’s PageSpeed Insights documentation explains that the tool evaluates website performance using user-centric metrics. That is useful, but for China-facing decisions it is only part of the picture. If a business cares about mainland China users, it needs visibility into how the site behaves from that environment, not just how it performs from somewhere else. The Marketing to China article also stresses the importance of regular monitoring and performance testing for websites operating in China.
This is easy to underestimate. Teams often review a site from their own office, their own network, and their own devices, then assume the experience is broadly the same elsewhere. With China, that assumption can be expensive. A site can look fine internally and still create friction for actual users in-market.
What this means in practice
If an international website is slow or unreliable in mainland China, the most useful first step is usually not to jump straight to a rebuild. It is to diagnose the problem more carefully.
A sensible review usually starts with four questions:
Is China traffic being served entirely from outside mainland China?
Which third-party scripts or assets sit on the critical path?
Does the business actually need mainland hosting, and if so, is it prepared for ICP filing and related compliance steps?
Is the team measuring the website from the user’s real environment, or only from overseas?
Key takeaway
The main lesson is simple: a website that feels blocked or broken in China is not always suffering from one dramatic failure. Quite often, it is the result of ordinary web decisions made for global traffic that do not hold up well under China-specific conditions.
That is why the most useful response is usually not a quick assumption, but a more disciplined diagnosis. Businesses that separate network design, compliance requirements, and third-party dependency issues tend to get to a clearer answer faster - including the answer that no full mainland rebuild is needed.
A practical audit approach: where to start
For NZ and AU businesses that want to assess why their website is underperforming for China-based users, a structured audit is more useful than a general optimisation project. The audit should answer four questions in sequence.
First: is China traffic being served entirely from infrastructure outside mainland China? If the web server, CDN, and supporting services are all hosted outside China, the site is being delivered across cross-border network boundaries for every user in mainland China. This is the most common root cause of slow or unreliable performance in the market.
Second: which third-party scripts or assets are on the critical rendering path? A site that loads quickly in New Zealand or Australia but includes external calls to Google Analytics, Google Fonts, YouTube embeds, Facebook scripts, or other blocked or slow-loading services will stall for mainland China users before those calls resolve. A technical audit that maps all third-party dependencies and tests whether they load from within mainland China is the most direct way to identify these blocking elements.
Third: does the site require a mainland China hosting arrangement - and if so, is the business prepared for ICP filing requirements? An ICP recordal is required for websites hosted on servers in mainland China. This is an administrative process managed through the hosting provider, but it has a processing timeline and ongoing maintenance requirements that should be factored into the architecture decision.
Fourth: is the business measuring website performance from within mainland China rather than from the home market? A site that appears fast and functional from a New Zealand or Australian office can perform poorly for mainland users without anyone in the business being aware of it. Available tools for China-specific performance testing include web performance monitoring services with mainland China probe locations, which can provide a reasonable proxy for the user experience from within the market.
Implementation options and practical trade-offs
There is no universal answer to how a NZ or AU business should address poor China website performance. The appropriate approach depends on the site's architecture, the nature of the traffic being served, and the compliance obligations that apply to the business's China market activities.
For businesses whose China activity is primarily B2B - using the website for supplier credibility and buyer communication rather than direct consumer engagement - a lightweight, third-party-clean landing page optimised for mainland China performance may be the most practical solution, without requiring a full mainland hosting arrangement.
For businesses running direct-to-consumer e-commerce with significant China-based traffic, a more comprehensive approach - including CDN infrastructure with mainland China points of presence, or a China-specific hosting arrangement with ICP recordal - is likely necessary to deliver the user experience that Chinese consumers expect.
In both cases, the most common improvement with the lowest implementation cost is identifying and removing blocking third-party dependencies from the critical rendering path. This alone can produce a meaningful improvement in perceived performance for mainland China users without requiring architectural changes or compliance decisions.
