By adding a CDN to your website it will further boost the speed of your website loading time after the initial HTML has loaded because the other resource that make up your page are able to be served directly from the CDN, including images, fonts and stylesheets.
When talking about web hosting solutions for China, its often recommended to setup a second website or mirror hosting in Hong Kong if you can't get an ICP. While often recommended by some, we strongly discourage it in favour of better solutions.
Users in China who are physically located close to Hong Kong will have a relatively fast experience from your Hong Kong web hosting but for the rest of China it will be prone to chronic network congestion issues, generally slow speeds, high latency and high packet loss.
For companies who cannot get an ICP, this is our recommended solution which combines the geographical benefits while eliminating a multitude of issues with the setups described above.
We offer specialised software engineering services to build your website in a way that doesn't need a centralised web server therefore enabling your website to be deployed to hundreds of data centers globally.
By deploying your website to multiple locations around China, users will be automatically routed to the fast one at any given time. Users experiencing network congestion on their south will have their traffic automatically routed to a data center on their north or east. Latency is significantly reduced because users anywhere in China will connect to a data center closest to them; if they are in the south then one along the southern border; if they are on the north then one along the northern border; and so on for east and west. Users in central China will be routed in the direction with the least network congestion and lowest latency.
For companies that are eligible for an ICP, we are able to take the above solution one step further by also deploying your website to over 167 data centers throughout mainland China. With over 350 data centers globally your website will be ultra fast from anywhere on earth and be able to instantaneously scale to an unlimited number of active users.
Users in China being served by a data center in their same city will have exponentially faster performance.
Our hosting solution actually uses a lot of the same physical infrastructure as the major CDN's and all the same data centers. Ultimately the difference comes down to the software level where we write code that gets deployed to every data center in the network.
Typically a CDN is placed between your users and the website to accelerate traffic and increase capacity by serving static content. We take this one step further with our specialised software engineering services to build your website entirely into the massively distributed infrastructure operated by the major cloud providers including AWS, GCP, Cloudflare, Alibaba, Oracle and Akamai.
With our solution, every request-response cycle is handled entirely in the very same data center that the user was routed to. Theres no need for requests to be relayed down stream to other data centers or to communicate with an external database services.
This doesn't mean you'll have a static content website, quite the opposite, there is exponentially more compute resources available to process hyper dynamic and localised content at a granular per-user basis. This is precisely because our software architecture distributes your website across hundreds or even many thousands of physical servers globally instead of being limited to the resources of one physical web server.
Furthermore, we utilise multiple TCP and HTTP techniques at a low level to boost the performance, and mitigate packet loss. And at a higher level we optimise the loading performance of the page resources and Javascript.
Listed below are test results from multiple cities in mainland China to show a comparison in TTFB and Full Page Loading Time for each of the 5 solutions described in this page. The tests are conducted on a website with no render blocking, no blocked resources, a 10 milliseconds server response time on the root document, and 60 resources with a total payload of 3 megabytes.
Select a city below to show the speed results for users in that location.
TTFB (min) | TTFB (max) | Load Time (min) | Load Time (max) | |
---|---|---|---|---|
Centralised | 770 ms | 1,022 ms | 19.66 seconds | 23.36 seconds |
Centralised + CDN | 180 ms | 240 ms | 0.53 seconds | 0.98 seconds |
Hong Kong Site/Mirror | 38 ms | 90 ms | 0.55 seconds | 1.14 seconds |
Decentralised (no ICP) | 38 ms | 90 ms | 0.31 seconds | 0.67 seconds |
Decentralised (with ICP) | 20 ~ 30 ms | 0.11 seconds | 0.37 seconds |
TTFB (min) | TTFB (max) | Load Time (min) | Load Time (max) | |
---|---|---|---|---|
Centralised | 858 ms | 1,150 ms | 21.94 seconds | 26.23 seconds |
Centralised + CDN | 264 ms | 345 ms | 2.01 seconds | 2.69 seconds |
Hong Kong Site/Mirror | 158 ms | 274 ms | 2.87 seconds | 4.19 seconds |
Decentralised (no ICP) | 150 ms | 230 ms | 1.49 seconds | 2.05 seconds |
Decentralised (with ICP) | 20 ~ 30 ms | 0.11 seconds | 0.37 seconds |
TTFB (min) | TTFB (max) | Load Time (min) | Load Time (max) | |
---|---|---|---|---|
Centralised | 858 ms | 1,150 ms | 21.94 seconds | 26.23 seconds |
Centralised + CDN | 264 ms | 345 ms | 2.01 seconds | 2.69 seconds |
Hong Kong Site/Mirror | 158 ms | 274 ms | 2.87 seconds | 4.19 seconds |
Decentralised (no ICP) | 150 ms | 230 ms | 1.49 seconds | 2.05 seconds |
Decentralised (with ICP) | 20 ~ 30 ms | 0.11 seconds | 0.37 seconds |
TTFB (min) | TTFB (max) | Load Time (min) | Load Time (max) | |
---|---|---|---|---|
Centralised | 762 ms | 1,070 ms | 19.46 seconds | 23.98 seconds |
Centralised + CDN | 298 ms | 352 ms | 1.85 seconds | 2.23 seconds |
Hong Kong Site/Mirror | 226 ms | 310 ms | 4.18 seconds | 5.14 seconds |
Decentralised (no ICP) | 134 ms | 178 ms | 1.32 seconds | 1.63 seconds |
Decentralised (with ICP) | 20 ~ 30 ms | 0.11 seconds | 0.37 seconds |
TTFB (min) | TTFB (max) | Load Time (min) | Load Time (max) | |
---|---|---|---|---|
Centralised | 806 ms | 1,026 ms | 20.60 seconds | 23.82 seconds |
Centralised + CDN | 285 ms | 315 ms | 1.78 seconds | 1.91 seconds |
Hong Kong Site/Mirror | 214 ms | 298 ms | 3.95 seconds | 4.91 seconds |
Decentralised (no ICP) | 130 ms | 142 ms | 1.28 seconds | 1.36 seconds |
Decentralised (with ICP) | 20 ~ 30 ms | 0.11 seconds | 0.37 seconds |
TTFB (min) | TTFB (max) | Load Time (min) | Load Time (max) | |
---|---|---|---|---|
Centralised | 734 ms | 830 ms | 18.73 seconds | 20.14 seconds |
Centralised + CDN | 214 ms | 245 ms | 0.86 seconds | 1.14 seconds |
Hong Kong Site/Mirror | 142 ms | 154 ms | 2.56 seconds | 2.70 seconds |
Decentralised (no ICP) | 62 ms | 94 ms | 0.56 seconds | 0.78 seconds |
Decentralised (with ICP) | 20 ~ 30 ms | 0.11 seconds | 0.37 seconds |
Being able to scale is a must for the Chinese and Global market. Our massively distributed software engineering and edge network gives your project the advantage of a no-cache no-compromise, fully dynamic response at scale, perfect for e-commerce.