Website readiness profile · Snapshot 23 October 2026
cash.app
cash.app's public homepage, certificate and DNS checked against 31 practices and compared with 157 Online Payment & Wallets sites.
- Readiness index
- 85/100
- Ahead of
- 92%
- Practices observed
- 23/30
- Popularity band
- Top 10K
Online Payment & Wallets median 64
of measured Online Payment & Wallets sites
1 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: cash.app. Thin bar: Online Payment & Wallets peer median.
Enable
95/100
Peers 72
Harden
86/100
Peers 63
Accelerate
76/100
Peers 61
Recover
0/100
Peers 6
Priority fixes for cash.app
Ordered by impact and by how common each practice is among peers.
Priority 1 · Accelerate
Offscreen images lazy-loaded
Observed: The homepage had 6 images and none used loading="lazy".
Why it matters: Images below the fold are only downloaded when the visitor scrolls near them, which frees bandwidth for what is visible first.
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.
63% of Online Payment & Wallets peers do this. Limit: Based on the homepage HTML delivered to an automated client; scripts that run later were not executed.
Priority 2 · 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.
On Cloudflare: Enable HTTP/3 (with QUIC) under Speed > Optimization > Protocol Optimization.
35% of Online Payment & Wallets peers do this.
Priority 3 · Harden
CAA records limit who can issue certificates
Observed: No CAA record was found for cash.app, so any public certificate authority may issue for it.
What to do: Publish CAA records naming every CA you actually use, including the CAs your CDN uses for managed certificates. Add an iodef contact if you want reports.
On Cloudflare: Cloudflare documents which CAs its managed certificates need; include them in your CAA records.
18% of Online Payment & Wallets peers do this.
Priority 4 · Harden
DNSSEC signed
Observed: No DS record was found for cash.app at its parent zone, so its DNS answers are not DNSSEC-signed.
What to do: Enable DNSSEC at your DNS provider, then add the DS record at your registrar. Plan provider moves carefully: a stale DS record can make the domain fail to resolve.
On Cloudflare: Enable DNSSEC in DNS > Settings and add the DS record at the registrar.
8.3% of Online Payment & Wallets peers do this.
Guide: Website Uptime Readiness: Prepare Before Traffic Arrives
What cash.app already does well
Practices fewer than half of Online Payment & Wallets peers use.
- security.txt publishedsecurity.txt with a contact found.6.6% of peers
- Structured data presentJSON-LD structured data found.38% of peers
- Certificate lifetime of 100 days or lessShort-lived 90-day certificate from Google Trust Services, already inside the 2027 limit.44% of peers
What we saw
- Homepage checked
- https://cash.app/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, HTTP/2
- Certificate
- Google Trust Services, 90-day validity, expiring 2026-12-04
- CDN or edge
- Cloudflare
- Platform or framework
- Next.js
- DNS operators
- Amazon Route 53
- HSTS
- max-age 365 days, includeSubDomains, preload
- DMARC policy
- p=reject
- Homepage HTML
- 477 KB, gzip
- Images on homepage
- 6 (webp 6)
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 7
Observed 23
- HTTP requests move to HTTPS
- HSTS kept for at least a year
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- Certificate lifetime of 100 days or less
- security.txt published
- DMARC policy enforces quarantine or reject
- X-Content-Type-Options: nosniff
- Framing restricted
- Content Security Policy present
- HTTP/2 negotiated
- HTML compressed
- Modern image formats in use
- No render-blocking scripts in <head>
- 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
Not measured 1
- Static files cached for 30 days or more
Own cash.app?
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: cash.app. This profile covers configuration only.