nerdwallet.com website review

Not measured in this review.

• Tap response (INP) held steady for real visitors

  +4%

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

• About 0.4 g of CO₂ per visit

  0.40 g

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

• 4 text elements with low contrast

  4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  Elements (3)

• Elements must only use permitted ARIA attributes (1 element)

  Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.

  Elements (1)

• Scrollable region must have keyboard access (1 element)

  Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  Elements (1)

• 1 tap target too small

  1 tap target is too small or too close together to hit reliably with a finger.

  Elements (1)

• 2 images without alt text

  2 images have no alt text, which hurts accessibility and image search.

  View source

• 3 form fields without a label

  3 form fields have no label, so screen readers announce an empty box and autofill guesses.

  View source

• Title is short (27 characters)

  Your title is only 27 characters: “NerdWallet: Finance smarter”. Between 30 and 65 characters leaves room to say what you do and for whom.

  View source

• 407 internal links, 32 external

  The homepage links to 407 pages on nerdwallet.com and 32 external pages.

• No llms.txt

  There is no https://www.nerdwallet.com/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.

• Opted out of AI training for 1 crawler

  robots.txt blocks Google-Extended, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

• Your server turned our page checks away

  15 pages we tried to fetch timed out or refused automated requests, so these checks couldn't run. Some firewalls do this to every bot, including search engine crawlers they don't recognise.

• Local business without LocalBusiness data

  Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  View source

• No phone number on the homepage

  A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

• 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.

• No opening hours

  The homepage shows no opening hours. If customers visit or call, show when.

• No map or directions link

  There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

• About 1,959 words of copy

  The homepage carries about 1,959 words of visible text.

• 2 trackers load before any consent

  2

  Before a visitor clicks anything, the page loads Google Ads and Google Tag Manager (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

• 17 cookies set on arrival

  17

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

• 5 other companies contacted

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