Website readiness profile · Snapshot 23 October 2026
americanexpress.com
americanexpress.com's public homepage, certificate and DNS checked against 31 practices and compared with 549 Banking & Finance sites.
- Readiness index
- 75/100
- Ahead of
- 76%
- Practices observed
- 18/27
- Popularity band
- Top 5K
Banking & Finance median 66
of measured Banking & Finance sites
4 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: americanexpress.com. Thin bar: Banking & Finance peer median.
Enable
83/100
Peers 78
Harden
84/100
Peers 64
Accelerate
59/100
Peers 55
Recover
0/100
Peers 21
Priority fixes for americanexpress.com
Ordered by impact and by how common each practice is among peers.
Priority 1 · Accelerate
Modern image formats in use
Observed: The homepage had 12 images and none used WebP or AVIF.
Why it matters: WebP and AVIF are typically much smaller than JPEG or PNG at similar quality, and images are often the heaviest part of a page.
What to do: Serve WebP or AVIF with a JPEG or PNG fallback, either through an image CDN or by generating both formats at build time.
37% of Banking & Finance peers do this. Limit: Based on the homepage HTML delivered to an automated client; scripts that run later were not executed.
Guide: AVIF, WebP, JPEG, and PNG: Choose the Right Image Format
Priority 2 · Accelerate
Offscreen images lazy-loaded
Observed: The homepage had 12 images and none used loading="lazy".
What to do: Add loading="lazy" to images below the fold. Do not lazy-load the main hero image, because that delays the largest visible element.
56% of Banking & Finance peers do this.
Priority 3 · Enable
Structured data present
Observed: The homepage had no JSON-LD structured data.
What to do: Add JSON-LD for your organization and main content types, then test it with Google's Rich Results Test.
49% of Banking & Finance peers do this.
Priority 4 · Accelerate
HTTP/3 advertised
Observed: The homepage did not advertise HTTP/3 through an Alt-Svc header.
What to do: Turn on HTTP/3 at your CDN. Browsers fall back to HTTP/2 automatically, so the risk is low.
22% of Banking & Finance peers do this.
What americanexpress.com already does well
Practices fewer than half of Banking & Finance peers use.
- No render-blocking scripts in <head>Head scripts load without blocking.36% of peers
- Referrer-Policy setReferrer-Policy present.36% of peers
What we saw
- Homepage checked
- https://www.americanexpress.com/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, HTTP/2
- Certificate
- DigiCert, 198-day validity, expiring 2027-03-24
- CDN or edge
- Akamai
- Platform or framework
- Adobe Experience Manager
- DNS operators
- Akamai Edge DNS
- HSTS
- max-age 365 days, includeSubDomains
- DMARC policy
- p=reject
- Homepage HTML
- 896 KB, gzip
- Images on homepage
- 12 (svg 7)
Limits: homepage only, one location, one moment. Header checks reflect the homepage response; other pages may differ.
Stack and providers
Seen in the homepage response, certificate and DNS. Provider pages compare how their customers configure the same checks.
All 31 checks
Select a gap for the method and fix. How each check works
Not observed 9
Observed 18
- HTTP requests move to HTTPS
- HSTS kept for at least a year
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- DMARC policy enforces quarantine or reject
- X-Content-Type-Options: nosniff
- Framing restricted
- Content Security Policy present
- Referrer-Policy set
- HTTP/2 negotiated
- HTML compressed
- No render-blocking scripts in <head>
- Canonical URL declared
- Meta description written
- Mobile viewport configured
- Social preview image set
- Page language declared
- At most one redirect to the homepage
Not measured 4
- security.txt published
- Static files cached for 30 days or more
- robots.txt published
- XML sitemap discoverable
Own americanexpress.com?
Re-run the checks after a change, keep a private action plan in a free workspace, or report a mistake.
Live status for this site: Status Is Down: americanexpress.com. This profile covers configuration only.