STATUS IS UPREADINESS PROFILE

Website readiness profile · Snapshot 23 October 2026

citi.com

citi.com's public homepage, certificate and DNS checked against 31 practices and compared with 549 Banking & Finance sites.

Readiness index
74/100

Banking & Finance median 66

Ahead of
74%

of measured Banking & Finance sites

Practices observed
20/29

2 of 31 could not be measured

Popularity band
Top 10K

Chrome UX Report top-sites list

Measured 2026-10-23 12:10:13 UTC from one location. How we measure

Readiness by lane

Green: citi.com. Thin bar: Banking & Finance peer median.

Enable

87/100

Peers 78

Harden

75/100

Peers 64

Accelerate

50/100

Peers 55

Recover

100/100

Peers 21

Priority fixes for citi.com

Ordered by impact and by how common each practice is among peers.

  1. Priority 1 · Harden

    TLS 1.3 negotiated

    Observed: The TLS connection negotiated TLSv1.2.

    Why it matters: TLS 1.3 removes legacy cipher suites and completes the handshake in fewer round trips, so it is both safer and faster for new connections.

    What to do: Enable TLS 1.3 on your CDN or server. Keep TLS 1.2 available for older clients unless you have checked your audience.

    86% of Banking & Finance peers do this. Limit: Certificate and protocol were observed from one vantage point; CDNs can present different certificates by region.

  2. Priority 2 · Accelerate

    Static files cached for 30 days or more

    Observed: A same-site stylesheet or script was cacheable for no max-age, short of the 30-day benchmark.

    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.

  3. Priority 3 · Accelerate

    No render-blocking scripts in <head>

    Observed: The homepage <head> loaded 1 external script 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.

  4. Priority 4 · Enable

    Social preview image set

    Observed: The homepage had no og:image, so shared links may show without a preview image.

    What to do: Add Open Graph tags, including og:image with a 1200 x 630 image.

    59% of Banking & Finance peers do this.

What citi.com already does well

Practices fewer than half of Banking & Finance peers use.

  • CAA records limit who can issue certificatesCAA limits issuance to digicert.com, globalsign.com.20% of peers
  • Nameservers spread across providersNameservers spread across more than one operator.21% of peers
  • Referrer-Policy setReferrer-Policy present.36% of peers

What we saw

Homepage checked
https://www.citi.com/
Homepage response
HTTP 200
TLS
TLSv1.2, HTTP/2
Certificate
DigiCert, 390-day validity, expiring 2026-12-07
CDN or edge
Akamai
Platform or framework
Adobe Experience Manager, Angular
DNS operators
2 self-run or other nameserver domains
HSTS
max-age 730 days, includeSubDomains
DMARC policy
p=reject
Homepage HTML
248 KB, gzip
Images on homepage
0

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

Observed 20

  • HTTP requests move to HTTPS
  • HSTS kept for at least a year
  • Certificate has more than 14 days left
  • CAA records limit who can issue certificates
  • 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
  • robots.txt published
  • XML sitemap discoverable
  • Canonical URL declared
  • Meta description written
  • Mobile viewport configured
  • Structured data present
  • Page language declared
  • At most one redirect to the homepage
  • Nameservers spread across providers

Not measured 2

  • Modern image formats in use
  • Offscreen images lazy-loaded

Own citi.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: citi.com. This profile covers configuration only.

Compare with other Banking & Finance sites