Website readiness profile · Snapshot 23 October 2026
wellsfargo.com
wellsfargo.com's public homepage, certificate and DNS checked against 31 practices and compared with 549 Banking & Finance sites.
- Readiness index
- 71/100
- Ahead of
- 64%
- Practices observed
- 20/31
- Popularity band
- Top 5K
Banking & Finance median 66
of measured Banking & Finance sites
0 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: wellsfargo.com. Thin bar: Banking & Finance peer median.
Enable
95/100
Peers 78
Harden
75/100
Peers 64
Accelerate
38/100
Peers 55
Recover
100/100
Peers 21
Priority fixes for wellsfargo.com
Ordered by impact and by how common each practice is among peers.
Priority 1 · Accelerate
Static files cached for 30 days or more
Observed: A same-site stylesheet or script was cacheable for 1800 seconds, short of the 30-day benchmark.
Why it matters: Returning visitors and later page views reuse cached files instead of downloading them again.
What to do: Give versioned (fingerprinted) CSS, JavaScript, fonts and images Cache-Control: public, max-age=31536000, immutable, and change the file name whenever the content changes.
43% of Banking & Finance peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.
Priority 2 · Accelerate
Modern image formats in use
Observed: The homepage had 15 images and none used WebP or AVIF.
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.
Guide: AVIF, WebP, JPEG, and PNG: Choose the Right Image Format
Priority 3 · Accelerate
No render-blocking scripts in <head>
Observed: The homepage <head> loaded 3 external scripts without async or defer.
What to do: Add defer to scripts that need the DOM, async to independent ones such as analytics, or move them to the end of the body.
36% of Banking & Finance peers do this.
Guide: Control Third-Party Scripts Before They Control Your Page
Priority 4 · Accelerate
Offscreen images lazy-loaded
Observed: The homepage had 15 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.
What wellsfargo.com already does well
Practices fewer than half of Banking & Finance peers use.
- Nameservers spread across providersNameservers spread across Akamai Edge DNS and Vercara UltraDNS.21% of peers
- Structured data presentJSON-LD structured data found.49% of peers
What we saw
- Homepage checked
- https://www.wellsfargo.com/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, HTTP/2
- Certificate
- DigiCert, 198-day validity, expiring 2027-03-10
- CDN or edge
- Akamai
- DNS operators
- Akamai Edge DNS, Vercara UltraDNS
- HSTS
- max-age 365 days, includeSubDomains
- DMARC policy
- p=reject
- Homepage HTML
- 121 KB, gzip
- Images on homepage
- 15 (png 8, jpg 5)
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 11
- Certificate lifetime of 100 days or less
- CAA records limit who can issue certificates
- DNSSEC signed
- security.txt published
- Referrer-Policy set
- HTTP/3 advertised
- Static files cached for 30 days or more
- Modern image formats in use
- Offscreen images lazy-loaded
- No render-blocking scripts in <head>
- Reachable over IPv6
Observed 20
- 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
- HTTP/2 negotiated
- HTML compressed
- robots.txt published
- XML sitemap discoverable
- Canonical URL declared
- Meta description written
- Mobile viewport configured
- Structured data present
- Social preview image set
- Page language declared
- At most one redirect to the homepage
- Nameservers spread across providers
Own wellsfargo.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: wellsfargo.com. This profile covers configuration only.