keukensale.com website review

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

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

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

8 third-party services load with your homepage (Google Tag Manager, cookieconsent.io and Hotjar and others), adding 885 KiB and 700 ms of main-thread time.

Google Tag Manager costs a phone 473 ms of main-thread work and 702 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

About 368 KiB of JavaScript is downloaded but never used on this page.

A phone's processor spends 2.3 s on main-thread work while loading, 808 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

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

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

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

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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.

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

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

Your largest element takes 5.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Keukensale - KSC_Website_Okt_26_864 x 1080”.

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

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

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

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

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

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

Your homepage downloads 2.6 MB in 113 requests on a phone: images 1.2 MB (41), scripts 1.1 MB (50) and stylesheets 113 KiB (7). Under 2 MB keeps phones on slow connections fast.

ksc-website-banners-inspiratie-magazine-864x1080-1-568x710.p is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

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

Some lists contain elements other than list items, which screen readers announce wrongly.

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

Links must have discernible text: 10 elements on the page fail this check, rated serious by axe-core.

6 tap targets are too small or too close together to hit reliably with a finger.

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

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

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

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

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

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

The homepage links to 224 pages on keukensale.com and 16 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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.

/zoeken and /winkelwagen are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

/zoeken has no meta description, so Google writes the search snippet from whatever text it finds.

/zoeken has no <h1> headline, so visitors and search engines get no clear main topic.

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

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

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://edge.cookieconsent.io/prod/css/cookie-consent.css' from origin 'https://www.keuken…”.

3 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

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

2 links go through two or more redirects, for example https://www.keukensale.com/keukenapparatuur/koelkasten/.

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

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

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

keukensale.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

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

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

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

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

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

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

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.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Hotjar (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

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

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.

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