hetlandvanooit.be website review

23 files are served with short cache lifetimes, so returning visitors download them again (3.1 MB).

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

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

Google Tag Manager costs a phone 1.1 s of main-thread work and 591 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

Your mobile performance score is 35. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

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

8 third-party services load with your homepage (Google Tag Manager, helloretailcdn.com and Klaviyo and others), adding 2.1 MB and 2.3 s of main-thread time.

helloretailcdn.com costs a phone 512 ms of main-thread work and 92 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.

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

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

Klaviyo costs a phone 317 ms of main-thread work and 343 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.

cloudfront.net costs a phone 5 ms of main-thread work and 681 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 74 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.

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

18 KiB could be saved by minifying JavaScript.

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.

Your largest element takes 30.1 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 30.2 s. Good is under 3.8 s.

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

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

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

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

Your homepage downloads 7.7 MB in 241 requests on a phone: images 5.3 MB (32), scripts 1.4 MB (86) and other files 767 KiB (109). Under 2 MB keeps phones on slow connections fast.

avatar.png weighs 1.8 MB. On a phone connection a single image that size takes seconds.

2 images are downloaded at several times the size a phone draws them, for example avatar.png at 1,254 px wide, shown at 56 px. Resized copies would save about 1.7 MB.

5 images (2.1 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.

76_2016_20J1817-07_10_c35ceaf1-af50-47d3-8050-168ec57d76c0.w 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).

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

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

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

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

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

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

Your title is only 27 characters: “Het Land van Ooit - Webshop”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

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

The homepage links to 602 pages on hetlandvanooit.be and 25 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://hetlandvanooit.be/collections/kleding and https://hetlandvanooit.be/collections/babies all use the title “Kleding – Het Land van Ooit - Webshop”. Search engines can't tell which page to show for a search, so each competes with the others.

https://hetlandvanooit.be/pages/nieuw-in-stock, https://hetlandvanooit.be/pages/speelgoedpagina, https://hetlandvanooit.be/blogs/events/demodagen-2026, https://hetlandvanooit.be/collections/kleding and https://hetlandvanooit.be/collections/babies have no meta description, so Google writes the search snippet from whatever text it finds.

https://hetlandvanooit.be/pages/geboortelijst-aanleggen, https://hetlandvanooit.be/pages/nieuw-in-stock, https://hetlandvanooit.be/pages/speelgoedpagina and https://hetlandvanooit.be/blogs/events/demodagen-2026 have no <h1> headline, so visitors and search engines get no clear main topic.

https://hetlandvanooit.be/collections/truien-cardigans, https://hetlandvanooit.be/collections/jurkjes and https://hetlandvanooit.be/collections/rokjes took over 3 s to send their HTML from our server.

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

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

1 error was logged to the browser console while the page loaded, for example “Refused to apply style from 'https://hetlandvanooit.be/cdn/shop/t/5/assets/app.min.js?v=174181184205775263941705925717'…”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

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

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

Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel (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.

Opening the homepage sets 17 cookies, 2 of them by other companies (measured from a US location before any click).

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