2025-26 benchmark report

AEM Site
Performance in China

We tested 106 AEM websites from Beijing, Singapore, Virginia (US), and London (UK). Many failed or slowed significantly when tested from Beijing. These are the results.

41%
of AEM sites didn't load within 30 seconds in Beijing
2.7x
slower loading in Beijing if the site even loads at all
98%
of AEM sites that loaded in all regions started rendering slower in Beijing
key findings

The AEM Performance Gap

The same AEM sites that loaded in Singapore, the US and the UK consistently failed or slowed down when tested from Beijing.

Most AEM sites didn't finish loading from Beijing

Among sites that loaded successfully in Singapore, the US and the UK, 38% failed to complete the test from China. These are sites running on enterprise-grade infrastructure. The failures point to cross-border delivery issues, not problems with AEM itself.

25k+

Enterprise infrastructure didn't prevent the failures

AEM sites typically run on Adobe's managed cloud with global CDNs and edge delivery. They still timed out or stalled from Beijing. Hosting and CDN coverage alone does not guarantee reliable delivery inside China.

25k+

Median load time was 7x the 3-second threshold

User experience research typically cites 3 seconds as the threshold for acceptable load time. The median AEM site tested from Beijing took 21.7 seconds to fully load.

25k+

Singapore, US and UK results confirm the gap is China-specific

Tests from Singapore, Virginia and London produced similar performance patterns, with success rates between 82–89%. The drop to 59% observed in Beijing is caused by China's unique internet environment affecting cross-border traffic.

25k+

High variability in China

Results from Beijing showed far greater spread between median and extreme values than Singapore, the US or UK. This means a higher likelihood of stalled requests, incomplete page loads, or unstable connections.

25k+

Even sites that loaded were consistently slower

When AEM sites successfully loaded across all regions, rendering still began later in Beijing 98% of the time and full page completion took 2.7x longer. This pattern appeared across nearly every comparable site, not just outliers.

2 in 5

AEM websites tested from Beijing timed out before finishing

Global performance comparison

AEM Website Performance by Geography

The same websites, tested from four locations.
Singapore
12.7s
Average load time
Virginia, United States
11.0s
Average load time
London, United Kingdom
9.8s
Average load time
Beijing, China
20.7s
Average load time
💡
key insight

Speed is only part of the picture. China website performance also means accessibility, deliverability, and stability over time. A page might partially load, but if key resources fail (videos, scripts, third-party tools), the user experience is still broken.

Success Rate by Region

Using a 30-second success threshold, AEM sites tested from Beijing failed at 3–4x the rate of Singapore, the US and UK.
Singapore
82%
success
Success 82%
Fail 18%
Virginia, United States
89%
success
Success 89%
Fail 11%
London, United Kingdom
87%
success
Success 87%
Fail 13%
Beijing, China
59%
success
Success 59%
Fail 41%
💡
key insight

When tested from Beijing, 41% of AEM site tests either exceed 30 seconds or fail to complete, compared with 11–18% in other regions. Beijing produced 3–4x the failure rate of Singapore, the US and the UK. And the sites that did load took significantly longer to become usable.

Nearly 7 in 8 AEM websites either took longer than 10 seconds to load or failed to complete the test from Beijing.

Performance Metrics Breakdown

How the same AEM websites performed across four key metrics.
Time to First Byte (TTFB)
Beijing 2.8-4.9x slower than other global locations
🇸🇬
0.5s
🇺🇸
0.3s
🇬🇧
0.3s
🇨🇳
1.4s
2.8-4.9x slower
Render Start
Beijing 2.0-2.7x slower than other global locations
🇸🇬
2.3s
🇺🇸
1.7s
🇬🇧
1.8s
🇨🇳
4.6s
2.0-2.7x slower
Load Time
Beijing 2.3-3.2x slower than other global locations
🇸🇬
9.5s
🇺🇸
7.9s
🇬🇧
6.9s
🇨🇳
21.7s
2.3-3.2x slower
Number of requests
25-46% fewer requests in Beijing than other global locations
🇸🇬
129
🇺🇸
158
🇬🇧
114
🇨🇳
86
💡
key insight

Fewer requests from Beijing doesn't mean lighter pages. It means many pages never finished loading. Requests stalled, timed out, or failed before the page could complete.

under the hood

Why AEM sites underperform in China

Every page load depends on three layers of infrastructure. AEM gives you more control than most platforms but the China performance gap persists.
www.yoursite.com
Page request from a visitor in mainland China
Your domain
Configurable
AEM platform & Adobe ecosystem
Partially configurable
Third-party resources
China expertise required
Every page load depends on three categories of domains. AEM teams control more of the stack than other platforms, but the layers that often cause failures in China sit outside that control.
Your domain
This is the only layer that the organization directly controls. DNS, routing, and TLS configuration sit here. Optimization for China is activated at this layer via a DNS change and no changes to AEM itself are required.
AEM platform & Adobe ecosystem
AEM publish instances, dispatchers, and the Fastly CDN are hosted outside China. Organizations running AEM as a Cloud Service cannot relocate or reroute this infrastructure. Adobe Experience Cloud services like Analytics, Target, Launch, and Fonts add further external dependencies that each resolve and load independently from outside the region.
Third-party resources
The average enterprise AEM site loads 50–150+ third-party resources per page, each with sub-dependencies. Enterprise marketing stacks tend to be heavy with personalization tools, A/B testing platforms, consent managers, tag managers, and analytics layers that all add cross-border requests. These are not easily removed without breaking global functionality, nor easily replaced without China-specific knowledge, as each resource's behavior in China evolves over time.
IN practice

An AEM and Chinafy Case Study

Chinafy addressed the key incompatibilities facing this AEM site and took it from failing to load in China, timing out at over 40 seconds, to loading faster than the median loading time for AEM sites tested in Virginia, London and Singapore.
Original site, Guangzhou
40+s
Page content failed to fully load
Chinafy-optimized site, Guangzhou
~5s
Fully loaded, all content intact

Mandai Wildlife Reserves is a world-leading zoo-management company headquartered in Singapore. Their AEM-powered site loaded normally for visitors globally, but from China, the experience was significantly different. Third-party resources the site depended on, including images, scripts, and tracking tools, were either loading slowly or failing entirely.

Chinafy was added as a bolt-on to their existing AEM setup. No rebuild, no rehosting, no code rewrites. The optimization addressed both infrastructure-based and code-level incompatibilities, including the Adobe ecosystem services and third-party resources the site relied on.

Load time
40s+ - 10s
Page content
40s+ - ~5s
Speed improvement
4x
Platform
Adobe Experience Manager (AEM)
about this report

How We Tested

Global websites consistently underperform in China, and this pattern isn't specific to one industry, tech stack, or region. But the gap is solvable.
106
websites tested
Beijing, China
Singapore
Virginia, US
London, UK
test locations
WebPageTest by Catchpoint
test runner
Chrome
browser
Cable
network
FAQ

How to interpret this report

If you have any further questions, don't hesitate to get in touch via our Get Started form.
What metrics do you track for web performance?
How should performance results for China get interpreted?
What signals matter most for users in Mainland China?
How should teams assess China web performance?
What does Page Load measure?
Why a standard CDN often fails in China?
Why do these metrics matter together?
 What does a Page Load timeout mean?
What role does Chinafy play?
glossary

Website Performance Metrics

Global websites consistently underperform in China, and this pattern isn't specific to one industry, tech stack, or region.
TTFB

The time from the initial request until the first byte of the response is received. Reflects backend processing network latency, and server responsiveness.

Render Start

The point in time when the browser first begins to display any visual content (text, images, background) on the screen.

visually complete

The time when all visible page content has finished rendering and no further visual changes occur above the fold.

load time

The time until the browser fires the onLoad event, indicating that all synchronous page resources have finished loading.

speed index

A calculated score that measures how quickly visible content is displayed during page load. Lower scores indicate faster visual progression.

requests

The total number of network requests made to load the page, including HTML, CSS< JavaScript, images, fonts, and third-party resources.

Bytes

The total amount of data transferred to load the page, typically measured in kilobytes or megabytes.

Lighthouse (LCP/TBT/CLS)

Largest Contentful Paint measures perceived load speed, Total Blocking Time measures interactivity, and Cumulative Layout Shift measures visual stability.

next steps

Want to see how your AEM website performs in China?

Get a free site analysis with specific recommendations to get it loading fast and fully for visitors in China.