Website review, no card needed

ah.nl logo

ah.nl website review

Visit site (opens in a new tab)Reviewed 18 October 202627 issues · 80 checks

This review found 27 issues worth fixing on ah.nl, 8 of them high impact, across 80 checks. The most urgent: fails Core Web Vitals for real visitors. 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
2.5 s2.0 sApr 25Oct 102.3 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20262.1 s
May 2, 20262.1 s
May 9, 20262.1 s
May 16, 20262.2 s
May 23, 20262.2 s
May 30, 20262.2 s
Jun 6, 20262.2 s
Jun 13, 20262.1 s
Jun 20, 20262.2 s
Jun 27, 20262.3 s
Jul 4, 20262.4 s
Jul 11, 20262.4 s
Jul 18, 20262.3 s
Jul 25, 20262.2 s
Aug 1, 20262.1 s
Aug 8, 20262.1 s
Aug 15, 20262.1 s
Aug 22, 20262.2 s
Aug 29, 20262.2 s
Sep 5, 20262.3 s
Sep 12, 20262.2 s
Sep 19, 20262.2 s
Sep 26, 20262.2 s
Oct 3, 20262.3 s
Oct 10, 20262.3 s
Real-visitor tap response (INP)75th percentile, phones
123 ms115 msApr 25Oct 10122 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 2026119 ms
May 2, 2026120 ms
May 9, 2026120 ms
May 16, 2026120 ms
May 23, 2026119 ms
May 30, 2026118 ms
Jun 6, 2026118 ms
Jun 13, 2026118 ms
Jun 20, 2026119 ms
Jun 27, 2026121 ms
Jul 4, 2026121 ms
Jul 11, 2026121 ms
Jul 18, 2026120 ms
Jul 25, 2026119 ms
Aug 1, 2026116 ms
Aug 8, 2026117 ms
Aug 15, 2026119 ms
Aug 22, 2026120 ms
Aug 29, 2026121 ms
Sep 5, 2026121 ms
Sep 12, 2026120 ms
Sep 19, 2026120 ms
Sep 26, 2026120 ms
Oct 3, 2026121 ms
Oct 10, 2026122 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 ah.nl (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. ah.nl at 0.6 s0.6 s
  2. ah.nl at 1.1 s1.1 s
  3. ah.nl at 1.7 s1.7 s
  4. ah.nl at 2.3 s2.3 s
  5. ah.nl at 2.8 s2.8 s
  6. ah.nl at 3.4 s3.4 s
  7. ah.nl at 4.0 s4.0 s
  8. ah.nl at 4.5 s4.5 s

Speed

5 to fix70
  • Mobile performance score: 70

    70/100

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

  • Render-blocking requests

    900 ms

    12 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.

  • Reduce unused JavaScript

    450 ms · 333 KiB

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

  • Improve image delivery

    515 KiB

    19 images could be 515 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 1,852 HTML elements

    The page has 1,852 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • 5 long tasks on the main thread

    5 long tasks block the main thread while loading, the longest for 205 ms. During a long task the page ignores taps.

  • Legacy JavaScript

    14 KiB

    Polyfills for old browsers add 14 KiB JavaScript that modern phones do not need.

  • Reduce unused CSS

    11 KiB

    About 11 KiB of CSS is downloaded but never applied on this page.

  • Use efficient cache lifetimes

    2 KiB

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

  • 1 third-party service on the page

    1 third-party service load with your homepage (grafana.net), adding 1 KiB and 0 ms of main-thread time.

2 checks passed
  • Main-thread work: 1.9 s

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

  • Server response: 145 ms

    145 ms

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

Core Web Vitals

8 to fix100
  • Fails Core Web Vitals for real visitors

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

  • Time to Interactive: 11.3 s

    11.3 s

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

  • Speed Index: 7.1 s

    7.1 s

    Visually, the page fills in at 7.1 s (Speed Index). Good is under 3.4 s.

  • Largest Contentful Paint: 4.5 s

    4.5 s

    Your largest element takes 4.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Dank voor je begrip en vertrouwen”.

  • Real-user TTFB: 979 ms

    979 ms

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

  • First Contentful Paint: 2.4 s

    2.4 s

    The first text or image appears after 2.4 s on a phone. Good is under 1.8 s.

  • Total Blocking Time: 210 ms

    210 ms

    Scripts block taps and scrolling for 210 ms in total while the page loads. Good is under 200 ms.

  • 4 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +2%

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

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

    +10%

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

5 checks passed
  • Real-user LCP: 2.3 s

    2.3 s

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

  • Real-user INP: 164 ms

    164 ms

    Real visitors wait 164 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: 1.5 s

    1.5 s

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

  • Cumulative Layout Shift: 0.059

    0.059

    The layout barely moves while loading (CLS 0.059, good is under 0.1).

Images and page weight

2 to fix75
  • Page weight: 2.1 MB in 115 requests

    2.1 MB

    Your homepage downloads 2.1 MB in 115 requests on a phone: images 1.1 MB (66), scripts 790 KiB (21) and stylesheets 102 KiB (13). Under 2 MB keeps phones on slow connections fast.

  • 2 images far larger than shown

    37 KiB

    2 images are downloaded at several times the size a phone draws them, for example ahonline:largeSpotlightCardShortCoverImage at 843 px wide, shown at 250 px. Resized copies would save about 37 KiB.

  • 4 images below the first screen load straight away

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

  • 1 image in older formats

    1 image (107 KiB) is 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.

  • About 0.6 g of CO₂ per visit

    0.60 g

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

Accessibility

3 to fixGoogle 9696
  • 5 text elements with low contrast

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

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 62 links without text

    62 visible links have no text or label, so screen readers cannot say where they go.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (14 elements).

2 checks passed
  • Every image has alt text

    All 68 images in the HTML carry an alt attribute.

  • 47 automated accessibility rules passed

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

SEO

1 to fixGoogle 9290
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • 233 internal links, 41 external

    The homepage links to 233 pages on ah.nl and 41 external pages.

7 checks passed
  • Meta description: 153 characters

    Your meta description is 153 characters: “Gezonder, makkelijker en voordeliger eten? Ontdek Albert Heijn: inspiratie, Bonusaanbiedingen en gemak: in de winkel én…”.

  • Title: 58 characters

    Your title is a healthy 58 characters: “Albert Heijn: boodschappen doen bij de grootste supermarkt”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: Organization and WebSite.

  • 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.ah.nl/sitemaps/entities/allerhande/recipes.xml.

AI search readiness

100
  • No llms.txt

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

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

  • Organization data: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.

  • Text is in the HTML

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

Other pages

1 to fix95
  • 2 links to non-canonical URLs

    Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.ah.nl/premium, whose canonical is https://www.ah.nl/meta.canonical.OMNI. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 2 pages slow to respond

    https://www.ah.nl/acties and https://www.ah.nl/bezorgbundel took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

    5 pages of 15 loaded without an error (the rest turned automated requests away).

  • Every page has a meta description

    All 5 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • 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 5 pages that loaded have a <title>.

Best practices

Google 96100
  • Missing source maps

    Large scripts ship without source maps.

3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

    76 of 78 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

7 to fix44
  • 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 calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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

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

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

  • 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 378 words of copy

    The homepage carries about 378 words of visible text.

1 checks passed
  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

Privacy and tracking

  • 14 cookies set on arrival

    14

    Opening the homepage sets 14 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 ah.nl, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Company

Founded
1887
Headquarters
Zaandam

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 27 issues on ah.nl, including 13 speed issues, 1 SEO issue and 7 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
ah.nl website review: scores and fixes | Programmable