TL;DR

Many companies treat hosting and performance as the same problem. They aren't. Moving servers into Mainland China reduces latency, but most of what slows a website down in China sits in the code, not the infrastructure. A site can be hosted in Shanghai and still depend on dozens of external services that are inaccessible or unreliable from inside the country. Going onshore also carries a stack of legal, administrative, and operational requirements that exist independently of the performance question. Chinafy makes existing offshore websites load fast, fully, and reliably in China without requiring teams to migrate.

The hosting-equals-performance assumption

When a global team hears that their website is slow or broken in China, the first instinct is usually to look at hosting. The logic seems intuitive. Visitors are in China, so the server should be too.

Hosting is part of the picture, but only a small part. Teams that go through with a move often find their site faster in some respects and just as broken in others. Embedded videos still spin. Fonts still load five seconds later than they should. Forms still fail to submit. The server location changed; the visitor's experience didn't.

Hosting and web performance answer different questions. Hosting determines where your content is served from. Performance depends on whether everything the page references can actually load.

What onshore hosting actually solves

Putting your origin server inside Mainland China cuts the physical distance between the server and your visitor, which reduces the time it takes for the first byte of data to arrive. According to Chinafy's State of Global Website Performance in China report, time-to-first-byte from Beijing to a US-hosted site runs roughly 4 to 4.5 times higher than from a server inside the region.

A move onshore, or to a nearby region like Hong Kong or Singapore, can close that gap. DNS resolution gets faster. Network hops drop. For simple, mostly static sites that don't depend on external resources, the difference is real and visible.

For most modern websites, that's where the benefit ends.

What onshore hosting leaves untouched

Hosting tells you where the page is served from. It doesn't tell you what's inside the page.

If your site pulls in a YouTube embed, the browser still has to reach YouTube. If your forms run on HubSpot, the browser still has to talk to HubSpot. A reCAPTCHA widget on a Shanghai-hosted site still calls Google. None of those services know or care where the origin lives, and none of them respond reliably from inside Mainland China.

When the browser hits a resource it can't reach, it doesn't skip ahead. It waits, retries, and only gives up once the connection times out. A single unreachable script can hold a page hostage for thirty seconds. Pages that lean on five or six of these resources can compound the delays into a minute or more of dead air.

This is the part of the website that a hosting move doesn't touch. It's also where the most visible damage usually happens. Companies that invest months getting their infrastructure onshore often arrive at a site that is technically faster and still functionally broken.

What going onshore actually involves

Aside from the performance question, it's worth understanding what onshore hosting requires upfront and on an ongoing basis. The full set of obligations is broader than most teams expect when they first explore the option.

To host a website inside Mainland China, the typical prerequisites include:

A registered legal entity in Mainland China. This is usually a Wholly Foreign-Owned Enterprise (WFOE), a joint venture, or a formal partnership with a local entity. Setting one up involves capital requirements, business scope registration, and tax filings, and tends to take several months on its own.

An ICP filing or ICP license. An ICP filing (备案) applies to informational, non-commercial websites. An ICP license (许可证) is required for sites that conduct commercial activity, like e-commerce or paid services. Both are issued by the Ministry of Industry and Information Technology (MIIT) and tied to the registered entity.

Real-name verification of the domain. The domain owner must verify their identity with an approved Chinese registrar. Domains registered through international registrars typically need to be transferred or re-registered.

A Public Security Bureau (PSB) filing. A separate registration with local public security authorities, completed after the ICP is in place.

Hosting with a Chinese cloud provider. Onshore hosting typically means hosting with providers like Alibaba Cloud or Tencent Cloud, who handle ICP verification at the infrastructure level.

Possible MLPS 2.0 classification. The Multi-Level Protection Scheme is a cybersecurity classification standard for systems hosted inside China. Depending on the system's nature and scale, classification, assessment, and remediation may be required.

Once the site is live, the requirements don't end. Ongoing obligations include:

Keeping the entity in good standing, with required filings and tax reporting.

Updating the ICP filing when the site's content category, domain, or hosting setup changes.

Meeting content review and removal obligations.

Adhering to data localization rules under the Personal Information Protection Law (PIPL) if personal data is collected from Chinese users.

Renewing certifications and filings as required.

Coordinating with the local entity for any technical or content changes.

None of these are insurmountable. Plenty of global businesses do go through the process for good reasons. The point is that going onshore is a multi-month, multi-party undertaking with continuing maintenance attached, and a team considering it should weigh that against what they are actually trying to fix.

Disclaimer: This guide is informational and does not constitute legal advice. Chinafy is not a legal or corporate advisory entity, and, given that every business is different, we suggest consulting with your internal legal counsel if you would like advice on any legal or compliance-related concerns, or alternatively we can connect you with one of our partners.

Where most performance issues come from

The bulk of performance problems for global websites in China happen at the application layer rather than the infrastructure layer. The application layer is where the page's code sits, and where decisions about which external services to depend on are baked in.

Modern websites pull in a long list of these dependencies: fonts, analytics, tag managers, video players, social embeds, marketing automation widgets, JavaScript libraries on external CDNs. There are hundreds, if not thousands, of resources with known compatibility issues in China, and the list shifts. Resources that worked last quarter may not work this one. Behavior varies across regions inside China and across days as network conditions fluctuate.

A hosting move doesn't change any of that. The page is still asking for the same external resources. The visitor's browser still has to make those requests. If the requests can't complete, the page can't render properly. The request originates inside China, but the destination is still wherever the resource lives.

Why offshore websites can still perform well in China

If hosting inside China isn't the path to good performance, what is?

An offshore website that has been optimized at the code level, and delivered through infrastructure built for the region, can reach near-native onshore speeds. The work involves ongoing identification of the specific external resources that fail in China, then replacing or handling them accordingly, and layering on a CDN with PoPs close to the country.

This matters for a few reasons. It avoids the onshore setup process entirely if that's not a business requirement. No new entity, no ICP, no domain transfer, no Chinese cloud provider, no separate site to maintain. It also means the global version of the site stays exactly as it is. Teams don't have to manage two versions of the same product or rebuild for a single market.

Chinafy's approach is built on this principle. By handling both the application-layer compatibility issues and the infrastructure delivery in one solution, offshore websites can reach near-native onshore performance in China without the regulatory and operational overhead of a full onshore setup.

When does onshore hosting make sense?

There are legitimate reasons to host onshore. If your business stores or processes personal data from Chinese users at scale, data localization rules under PIPL may apply depending on your industry. Some teams also choose onshore as part of a wider market entry plan that includes a local domain, a Mandarin-language site, and tighter integration with platforms like WeChat or Baidu.

Onshore hosting is more of a business and compliance decision than a performance decision. Going onshore won't automatically make your website work well in China, and staying offshore doesn't condemn it to working poorly.

If the trigger for considering a move is purely that the site isn't loading well in China, it's worth diagnosing whether the issue actually originates in hosting or somewhere else. In most cases, the answer is the latter.

How Chinafy helps

Chinafy optimizes websites for China at both the infrastructure and code level, without requiring teams to rebuild, rehost, or migrate. On the code side, Chinafy identifies and handles the external services that fail or underperform in China by handling them in unique ways. These optimizations are maintained and updated as conditions in China change, so performance doesn't drift over time. On the infrastructure side, every plan includes a fully managed CDN stack with near-China and onshore nodes purpose-built for the region.

Your existing global site continues to work exactly as it does today for everyone outside China, while visitors inside China get a version optimized to load fast, fully, and functionally.

If you're weighing onshore against optimizing what you already have, get in touch with Chinafy for a free evaluation of your site. We can also connect you with partners if you have questions about ICP licensing, entity setup, or other onshore requirements.

FAQs

Will hosting my website in China make it load faster?

Onshore hosting reduces latency by placing your servers closer to visitors in China. Latency is one piece of the performance picture, but not necessarily the dominant one. If your site relies on external services that are slow or blocked in China, like fonts, embedded videos, or marketing scripts, those will continue to cause delays no matter where the origin server is located.

Do I need an ICP license to make my website work in China?

No. An ICP filing or license is required if you want to use infrastructure inside Mainland China. You also don't need to host onshore to reach near-native onshore performance. Chinafy works with offshore-hosted sites and delivers an optimized variant to visitors in China without requiring an ICP.

What's involved in setting up onshore hosting in China?

At a minimum, you need a registered legal entity in Mainland China, an ICP filing or license tied to that entity, real-name verification of your domain through an approved Chinese registrar, a Public Security Bureau filing, and a hosting arrangement with a Chinese cloud provider. Depending on the system, you may also need to address MLPS 2.0 classification. Once the site is live, you have to maintain the entity, keep filings up to date, and meet ongoing content and data obligations.

What's the difference between a CDN and onshore hosting?

A CDN caches and delivers static content from distributed servers, which speeds up infrastructure-layer delivery. Onshore hosting puts your origin server inside Mainland China, which also speeds up that layer. Neither one addresses the application-layer issues caused by external services that fail in China. For a closer comparison, see Chinafy vs. CDN.

Can I stay offshore and still have a fast website in China?

Yes. With the right code-level optimization and infrastructure in place, an offshore website can reach near-native onshore performance. Chinafy handles both layers in one solution, so the global site stays as it is and visitors in China see a version built to work in the region.

My website is already hosted in China but it still loads slowly. Why?

More common than most teams expect. Onshore hosting solves for server proximity, but if the site still calls external resources that are slow or blocked in China, those calls will still stall the page. Hosting moves don't reach into the code where the underlying compatibility issues sit.