chase.com website review

Not measured in this review.

• Fails Core Web Vitals for real visitors

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

• Real-user INP: 328 ms

  328 ms

  Real visitors wait 328 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

• Tap response (INP) got 10% slower for real visitors

  +10%

  Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' tap response (inp) went from 297 ms to 328 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

• Largest content (LCP) got 12% slower for real visitors

  +12%

  Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' largest content (lcp) went from 1.9 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

• About 0.3 g of CO₂ per visit

  0.26 g

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

• No structured data

  No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

• No social preview image

  No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

• No X (Twitter) card tag

  No twitter:card tag. X falls back to Open Graph, which is incomplete here.

• 87 internal links, 37 external

  The homepage links to 87 pages on chase.com and 37 external pages.

• No Organization structured data

  There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

• No llms.txt

  There is no /llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

• 1 linked page hidden from search

  /digital/resources/search-results.html is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  Elements (1)

• 2 links to non-canonical URLs

  Your homepage links to 2 pages by a URL that isn't their canonical one, for example /meeting-scheduler/getstarted, whose canonical is /microsites/meeting-scheduler/getstarted. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  Elements (2)

• 2 pages without an H1

  /meeting-scheduler/getstarted and /locator have no <h1> headline, so visitors and search engines get no clear main topic.

• 15 internal pages checked

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

• 1 JavaScript error while loading

  1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

• No X-Content-Type-Options

  X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

• 1 link through redirect chains

  1 link go through two or more redirects, for example https://www.chase.com/personal/investments/online-investing/sdi.

• No Referrer-Policy

  No Referrer-Policy header, so full URLs can leak to the sites you link to.

• Deprecated X-XSS-Protection

  X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

• No security.txt

  There is no /.well-known/security.txt telling researchers how to report a security problem to you.

• DNSSEC is off

  chase.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

• No call to action on the first screen

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

• No social proof

  No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

• No analytics detected

  No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

• No direct contact details

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

• About 799 words of copy

  The homepage carries about 799 words of visible text.

• No DKIM key on the usual selectors

  We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

• Email authentication score: 90/100

  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.

• 13 cookies set on arrival

  13

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

• No consent tool detected

  No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

• 7 other companies contacted

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