zusje.nl website review

About 607 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.1 s faster on a phone.

4 images could be 1.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.6 s faster on a phone.

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

About 123 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.

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

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

8 third-party services load with your homepage (Google CDN, iubenda and Other Google APIs/SDKs and others), adding 1,000 KiB and 620 ms of main-thread time.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 650 ms).

Google CDN costs a phone 420 ms of main-thread work and 734 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.

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

Polyfills for old browsers add 10 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.

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

6 KiB could be saved by minifying JavaScript.

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

8 KiB could be saved by minifying CSS.

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

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

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

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

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

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

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

4 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-24, real Chrome visitors' largest content (lcp) went from 1.3 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 7.2 MB in 77 requests on a phone: images 4.3 MB (19), scripts 1.4 MB (30) and fonts 579 KiB (8). Under 2 MB keeps phones on slow connections fast.

5 images weigh 2.8 MB together. On a phone connection a single image that size takes seconds.

8 images (3.0 MB) 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.

Tapasbon-1024x1024.png 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 2.05 g of CO₂e: 246.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

5 elements hidden from screen readers can still receive keyboard focus.

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 on the page fails this check, rated moderate by axe-core.

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

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

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

No meta description, so Google writes its own snippet from whatever text it finds.

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

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 37 pages on zusje.nl and 5 external pages.

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.

/, https://zusje.nl/en and https://zusje.nl/de all use the title “Zusje - Bourgondisch genieten…”. Search engines can't tell which page to show for a search, so each competes with the others.

https://zusje.nl/tapas-menu, https://zusje.nl/genieten-bij-zusje, https://zusje.nl/onze-zusjes, https://zusje.nl/winkel, https://zusje.nl/veelgestelde-vragen and https://zusje.nl/zusje-en-meer and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://zusje.nl/tapas-menu, whose canonical is https://zusje.nl/tapas-menu/menukaart. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://zusje.nl/en and https://zusje.nl/de have no <h1> headline, so visitors and search engines get no clear main topic.

https://zusje.nl/winkel took over 3 s to send its HTML from our server.

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

8 of 36 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 “Failed to load resource: net::ERR_FAILED”.

Large scripts ship without source maps.

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

Your longest form asks for 8 fields (1 required). Every extra field lowers completion.

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

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 276 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

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

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

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