Feedback

Adobe Experience Manager speed statistics: 434 websites measured

By Christian Schreiber · Updated

Adobe Experience Manager is the CMS of many large enterprises, often combined with Adobe Analytics, Target and a tag manager. The platform itself is rarely the slowest part. Personalization, testing and tracking layered on top of it usually are.

By Core Web Vitals pass rate, Adobe Experience Manager ranks last of six platforms with their own page, behind Contentful. Clearest advantage over all measured websites: Time to First Byte (median), 645 ms against 693 ms. Largest gap: Pass all three Core Web Vitals, 34% against 48%.

Core Web Vitals on Adobe Experience Manager

34% of the 434 measured Adobe Experience Manager websites pass all three Core Web Vitals with real-user data. Across all measured websites the figure is 48%.

MetricGoodMedianMiddle halfThreshold
LCP 55% 2336 ms 1765 ms – 3227 ms 2500 ms
INP 66% 154 ms 108 ms – 250 ms 200 ms
CLS 64% 0.07 0.01 – 0.16 0.10

Median mobile Lighthouse score: 39. Why lab score and field data diverge is explained in the Website Speed Statistics.

Who runs Adobe Experience Manager in this sample

Adobe Experience Manager sites in this sample belong mostly to large enterprises: banks, insurers, manufacturers, telecom providers and consumer brands. They are typically multilingual, maintained by several teams and connected to Adobe Analytics, Target or other marketing tools, which shapes the numbers more than the CMS itself.

How to read your own Adobe Experience Manager values

Compare your values with the median of this sample rather than with all websites, since enterprise sites carry tooling that smaller sites never load. LCP is the most telling metric here, because testing and personalization layers act before the main content appears. If several country sites run on the same instance, test more than one: they often differ in tags and content even with the same templates.

Adobe Experience Manager by region

Field data of Adobe Experience Manager websites per region.

RegionWebsitesPass all threeLCP p50INP p50CLS p50
Worldwide 434 34% 2336 ms 154 ms 0.07
DACH 56 55% 1666 ms 124 ms 0.05

From 30 websites per region.

More metrics: TTFB, FCP, TBT and Speed Index

Thresholds and sources: Website Speed Statistics.

MetricSourceGoodAdobe Experience Manager medianAll websites medianThreshold
Time to First Byte Field data 68% 645 ms 693 ms 800 ms
First Contentful Paint Field data 52% 1780 ms 1545 ms 1800 ms
Total Blocking Time Lab 18% 764 ms 680 ms 200 ms
Speed Index Lab 1% 9756 ms 8657 ms 3400 ms

Page weight and third-party code

A Adobe Experience Manager home page transfers 4.6 MB at the median, of which 1.8 MB is JavaScript. 99% load third-party code, from a median of five providers.

ProviderShareMain thread (median)
Google Tag Manager 59% 493 ms
Adobe Tag Manager 50% 155 ms
Meta (Facebook) 32% 266 ms
OneTrust (Optanon) 31% 117 ms
Google CDN 14% 339 ms
TikTok 10% 188 ms

Most common lab findings

FindingShareSaving (median)
Render-blocking resources 97% 7854 ms
Unused JavaScript 96% 2360 ms
Unused CSS 86% 600 ms
Images not properly sized 80% 1549 ms
Images not in next-gen formats 56% 2205 ms

Typical Adobe Experience Manager performance bottlenecks

A/B testing and personalization scripts that hide the page until they have run delay the LCP directly. Several tag managers and analytics libraries on the same page add main-thread work and hurt INP. Auditing which tags still serve a purpose tends to bring more than changes to the CMS.

Related guides: Largest Contentful Paint (LCP) · Interaction to Next Paint (INP) · Eliminate render-blocking resources

Adobe Experience Manager by industry in this sample

Other platforms

How does your Adobe Experience Manager site compare?

Run a free test and put your values next to the Adobe Experience Manager median.

Test your website