Website review, no card needed

santander.nl logo

santander.nl website review

Visit site (opens in a new tab)Reviewed 25 October 202629 issues · 81 checks

This review found 29 issues worth fixing on santander.nl, 5 of them high impact, across 81 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
712 ms637 msMay 2Oct 17678 ms
Show as table
DateReal-visitor load time (LCP)
May 2, 2026646 ms
May 9, 2026647 ms
May 16, 2026656 ms
May 23, 2026664 ms
May 30, 2026669 ms
Jun 6, 2026695 ms
Jun 13, 2026690 ms
Jun 20, 2026682 ms
Jun 27, 2026703 ms
Jul 4, 2026686 ms
Jul 11, 2026700 ms
Jul 18, 2026694 ms
Jul 25, 2026677 ms
Aug 1, 2026676 ms
Aug 8, 2026670 ms
Aug 15, 2026668 ms
Aug 22, 2026659 ms
Aug 29, 2026658 ms
Sep 5, 2026654 ms
Sep 12, 2026651 ms
Sep 19, 2026654 ms
Sep 26, 2026656 ms
Oct 3, 2026668 ms
Oct 10, 2026683 ms
Oct 17, 2026678 ms
Real-visitor tap response (INP)75th percentile, phones
90 ms77 msMay 2Oct 1778 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 202686 ms
May 9, 202686 ms
May 16, 202686 ms
May 23, 202685 ms
May 30, 202685 ms
Jun 6, 202687 ms
Jun 13, 202687 ms
Jun 20, 202687 ms
Jun 27, 202688 ms
Jul 4, 202687 ms
Jul 11, 202688 ms
Jul 18, 202687 ms
Jul 25, 202687 ms
Aug 1, 202687 ms
Aug 8, 202685 ms
Aug 15, 202682 ms
Aug 22, 202679 ms
Aug 29, 202679 ms
Sep 5, 202679 ms
Sep 12, 202679 ms
Sep 19, 202679 ms
Sep 26, 202678 ms
Oct 3, 202678 ms
Oct 10, 202678 ms
Oct 17, 202678 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of santander.nl (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. santander.nl at 0.4 s0.4 s
  2. santander.nl at 0.8 s0.8 s
  3. santander.nl at 1.1 s1.1 s
  4. santander.nl at 1.5 s1.5 s
  5. santander.nl at 1.9 s1.9 s
  6. santander.nl at 2.3 s2.3 s
  7. santander.nl at 2.6 s2.6 s
  8. santander.nl at 3.0 s3.0 s

Speed

5 to fix73
  • Render-blocking requests

    1.6 s

    10 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.

  • Mobile performance score: 73

    73/100

    Your mobile performance score is 73 (desktop: 99). Pages that score under 90 lose visitors before the first paint.

  • Reduce unused JavaScript

    300 ms · 59 KiB

    About 59 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

  • Use efficient cache lifetimes

    300 ms · 56 KiB

    2 files are served with short cache lifetimes, so returning visitors download them again (56 KiB).

  • Improve image delivery

    300 ms · 52 KiB

    2 images could be 52 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.

  • Reduce unused CSS

    150 ms · 32 KiB

    About 32 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 50 ms. During a long task the page ignores taps.

  • Minify JavaScript

    13 KiB

    13 KiB could be saved by minifying JavaScript.

  • Phones get a much slower page than desktops

    Desktop scores 99 but mobile only 73. A gap that wide usually means heavy scripts and images that hit phones hardest.

  • 1 third-party service on the page

    1 third-party service load with your homepage (Trust Pilot), adding 9 KiB and 5 ms of main-thread time.

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

2 checks passed
  • Main-thread work: 0.3 s

    A phone's processor spends 0.3 s on main-thread work while loading, 65 ms of it running JavaScript. That is comfortably low.

  • Server response: 53 ms

    53 ms

    Your server sent the HTML in 53 ms, well inside Google's 600 ms guideline.

Core Web Vitals

4 to fix100
  • Largest Contentful Paint: 4.4 s

    4.4 s

    Your largest element takes 4.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

  • Cumulative Layout Shift: 0.207

    0.207

    The layout shifts by 0.207 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Time to Interactive: 4.4 s

    4.4 s

    The page becomes fully interactive after 4.4 s. Good is under 3.8 s.

  • 7 images without width and height

    7 images have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) held steady for real visitors

    -9%

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

  • Largest content (LCP) held steady for real visitors

    +5%

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

9 checks passed
  • Passes Core Web Vitals for real visitors

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

  • Real-user LCP: 0.7 s

    0.7 s

    Real visitors wait 0.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 77 ms

    77 ms

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

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 0.6 s

    0.6 s

    Real visitors see the first content after 0.6 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 308 ms

    308 ms

    Real visitors wait 308 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • First Contentful Paint: 1.7 s

    1.7 s

    The first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.

  • Speed Index: 3.0 s

    3.0 s

    Visually, the page fills in at 3.0 s (Speed Index), inside the 3.4 s “good” threshold.

  • Total Blocking Time: 0 ms

    0 ms

    Scripts block the page for only 0 ms while loading. Good is under 200 ms.

Images and page weight

100
  • 2 images in older formats

    2 images (135 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

  • 2 images below the first screen load straight away

    2 images further down the page (135 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 0.2 g of CO₂ per visit

    0.21 g

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

2 checks passed
  • Page weight: 759 KiB in 38 requests

    759 KiB

    Your homepage downloads 759 KiB in 38 requests on a phone: images 334 KiB (16), fonts 197 KiB (4) and scripts 140 KiB (10). That is a lean page.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

7 to fixGoogle 8791
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 6 text elements with low contrast

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

  • All page content should be contained by landmarks (2 elements)

    All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Headings should not be empty (4 elements)

    Headings should not be empty: 4 elements on the page fail this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 9 images in the HTML carry an alt attribute.

  • 42 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 6 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 10082
  • Title is short (16 characters)

    Your title is only 16 characters: “Home | Santander”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

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

  • Meta description is short (17 characters)

    Your meta description is only 17 characters: “Santander website”. 70 to 160 characters is enough to sell the click.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 36 internal links, 8 external

    The homepage links to 36 pages on santander.nl and 8 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “Wij helpen u graag met verantwoorde voertuigfinancieringen”.

  • Canonical URL set

    The canonical URL is https://www.santander.nl/.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.santander.nl/sitemap.xml.

AI search readiness

1 to fix88
  • 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 https://www.santander.nl/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.

2 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Text is in the HTML

    Your server sends the page's text in the HTML (784 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix76
  • 2 pages point its canonical at the homepage

    https://www.santander.nl/betrouwbaar and https://www.santander.nl/persoonlijk-contact declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.

  • 5 pages share 2 titles

    /, https://www.santander.nl/betrouwbaar and https://www.santander.nl/persoonlijk-contact all use the title “Home | Santander”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 7 pages without a meta description

    https://www.santander.nl/mijn-rekening, https://www.santander.nl/over-ons, https://www.santander.nl/werken-bij-santander, https://www.santander.nl/appstoreblx, https://www.santander.nl/over-ons/actueel-nieuws/santander-consumer-finance-en-openbank and https://www.santander.nl/veelgestelde-vragen/over-santander/fusie-met-openbank and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://www.santander.nl/betrouwbaar and https://www.santander.nl/persoonlijk-contact use the same meta description. A description written for each page earns more clicks.

  • 15 internal pages checked

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

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10093
  • 7 small tap targets

    7 of 27 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix75
  • Thin social proof

    Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

  • About 440 words of copy

    The homepage carries about 440 words of visible text.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Contact” and “Download Santander app”.

  • 4 calls to action

    The homepage has 4 calls to action, for example “Persoonlijk contact”, “Contact” and “Download Santander app”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

Privacy and tracking

  • 2 cookies set on arrival

    2

    Opening the homepage sets 2 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.

  • 1 other company contacted

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at santander.nl, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
U-{diag-tag-version-2}-{1272}-{Home}-{20260729-034018}-{1180
Framework
Vue.js

Company

Founded
2004
Headquarters
Utrecht

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 29 issues on santander.nl, including 9 speed issues, 4 SEO issues and 3 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25