acquia.com website review

43 files are served with short cache lifetimes, so returning visitors download them again (699 KiB).

7 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.8 s.

About 634 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.1 s faster on a phone.

About 252 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.2 s faster on a phone.

Your mobile performance score is 38 (desktop: 59). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

A phone's processor spends 4.6 s on main-thread work while loading, 1.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

The page has 3,768 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

8 third-party services load with your homepage (Google CDN, Google Tag Manager and Unpkg and others), adding 1.5 MB and 1.3 s of main-thread time.

Google CDN costs a phone 507 ms of main-thread work and 733 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

Google Tag Manager costs a phone 473 ms of main-thread work and 403 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

19 long tasks block the main thread while loading, the longest for 345 ms. During a long task the page ignores taps.

Polyfills for old browsers add 20 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).

1 image could be 9 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

2 KiB could be saved by minifying JavaScript.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

Your largest element takes 39.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Home”.

The page becomes fully interactive after 40.4 s. Good is under 3.8 s.

The first text or image appears after 4.2 s on a phone. Good is under 1.8 s.

Visually, the page fills in at 8.0 s (Speed Index). Good is under 3.4 s.

Scripts block taps and scrolling for 949 ms in total while the page loads. Good is under 200 ms.

Real visitors wait 2.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.

Real visitors wait 911 ms for your server to start answering (75th percentile). Good is under 800 ms.

4 images have no width and height attributes, so the layout jumps as each one loads.

Your homepage downloads 9.7 MB in 94 requests on a phone: images 5.9 MB (24), other files 1.7 MB (31) and scripts 1.4 MB (26). Under 2 MB keeps phones on slow connections fast.

2 images weigh 5.8 MB together. On a phone connection a single image that size takes seconds.

2 images are downloaded at several times the size a phone draws them, for example Rectangle 31_0.svg at 1,627 px wide, shown at 278 px. Resized copies would save about 4.3 MB.

3 images further down the page (5.8 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

By the Sustainable Web Design model, a visit to your homepage emits about 2.75 g of CO₂e: 330.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

11 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

Interactive controls must not be nested: 3 elements on the page fail this check, rated serious by axe-core.

Some lists contain elements other than list items, which screen readers announce wrongly.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

5 elements hidden from screen readers can still receive keyboard focus.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

Headings skip levels (h2 → h6), which makes the page harder to scan with a screen reader.

Your title is 69 characters, so Google will cut it off around 60: “Digital Experience Platform for Content, Community, Commerce | Acquia”.

The homepage links to 223 pages on acquia.com and 79 external pages.

/request-a-demo/live-demo-form is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/fr and /jp use the same meta description. A description written for each page earns more clicks.

We fetched 15 pages linked from your homepage (of 84 found) and read each the way a search engine does.

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=97204369&tm=gtm002&Ver=2&mid=14e19751-b96f-4cb9-ac90-bb1f3af8af57&bo=1&sid=f86a0c10ca9711f1ae48850cd0ffada0&vid=f86a2950ca9711f1bd51e78049ccac2b&vids=1&msclkid=N&gtm_t.

5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

acquia.com is registered until Dec 2026. Make sure auto-renew is on and the card on file is current.

acquia.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

Social proof on the homepage: 17 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

Your longest form asks for 8 fields (7 required). Every extra field lowers completion.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 1,709 words of visible text.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel and 3 mores (measured from a US location before any click). A consent tool (TrustArc) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 30 cookies (measured from a US location before any click).

Loading the homepage contacts 50 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.