A European site seen from China has a known set of difficulties: distance, an international link that is not always steady, and a filing required to host locally. The same physics applies the other way. A site hosted in China and opened from Europe crosses the same distance and the same cross-border link, in the opposite direction. Its owner rarely sees it, because everyone who tests it sits in the office next to the server. The buyer in Europe sees it every time.
Where the time actually goes
Opening a page is not one request. The browser first finds the server's address, then opens a connection, then negotiates the secure channel, and only then asks for the page. Each of these steps is a round trip, and each round trip costs the full distance between visitor and server. After the page arrives, it asks for its stylesheets, scripts, fonts and images, often from several different places. A server that responds quickly to a visitor next to it is not a fast server for everyone: it is a close one.
- Distance to the server. A page hosted in Asia and opened in Europe pays the distance for every step before the first byte arrives. Hosting close to the buyers removes most of it.
- The cross-border route. Traffic between China and Europe does not always take the same path, and its quality varies with the hour and the provider. The variation is the problem: it is difficult to reproduce, so it is rarely fixed.
- Heavy images and video. Product photographs exported at full size from a design file, and a background video that starts on arrival, are the most common reasons for a slow first screen, wherever the server is.
- Scripts from other places. Chat widgets, analytics, maps, font libraries and tag managers each add a connection to another host, and some of those hosts are slow or unreachable from Europe.
- Mobile networks. A European buyer is as likely to open the link on a phone in a train as at a desk. A page tested only on office fibre hides every problem a phone shows.
What a CDN does, and what it does not
A content delivery network keeps copies of your files on servers in many places and serves each visitor from the nearest one. For images, stylesheets, scripts and fonts it changes the picture completely: the file no longer travels from the origin, it comes from a node in the visitor's country. It does not help with content that is generated for each visitor, such as a basket, an account or a search result, unless that content is also cached or generated at the edge. It also needs a node near your target markets. A network with strong coverage in Asia and a thin one in Europe will not solve a problem that sits in Europe, so check the provider's coverage in the countries you sell to, not its global claims.
| Situation | What is slow | Lever |
|---|---|---|
| Server in China, buyers in Europe | Every page, from the first byte | Host in Europe, or place a CDN with European nodes in front |
| Server in Europe, heavy images | The first screen, on mobile | Resize and compress images; load below-the-fold ones later |
| Many third-party scripts | Waiting on another host before the page is usable | Remove what nobody reads; load the rest after the content |
| Dynamic pages, no cache | Time to first byte stays long even with a CDN | Cache what is the same for everyone; move the origin closer |
Third-party scripts from the Chinese stack
A site built for China often carries tools that make sense there: an analytics script from a Chinese provider, a map from a Chinese service, a chat window, a social login, fonts served from a Chinese network. Opened from Europe, each of them either loads slowly from far away or does not load at all, and a page that waits for the script before displaying can freeze. The same tools also raise a legal question once the visitor is in Europe, since they send data to a server outside the Union and most of them need consent before they run. The simplest approach is to keep a European version of the page free of tools that serve no European purpose, and to load the necessary ones after the content, behind the consent banner.
How to measure from the buyer's side
- Test from Europe, not from the office. Use a testing service that lets you choose a location in the target country, and run it on a simulated mobile connection as well as a fast one.
- Read three measures rather than a single score: the time to the first byte, which tells you about the server and the distance; the time until the main content is visible; and how soon the page responds to a tap or a click.
- Open the list of requests and sort it by host. Note every domain that is not yours, and ask for each one whether anybody uses it.
- Repeat the test at different hours of the day and from a second country. A result that changes with the hour points to the route and not to the page.
- Ask a contact in Europe to open the site on a phone and tell you what they saw. It takes a minute and finds problems that no tool describes.
Moving the site is not always the first step. If the images are far too large and the page loads a dozen tools nobody uses, a European host will make a heavy page arrive a little sooner and no lighter. Start by weighing the page, then remove, then bring the files closer with a CDN, and move the origin to Europe last. Hosting in the Union has a second advantage that has nothing to do with speed: the data of your European visitors and customers stays under the rules that apply to them, which simplifies the privacy notice. Whether you also keep a China version on a local host is a separate decision, and the two can coexist.