vomar.nl website review

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

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

5 third-party services load with your homepage (cloudfront.net, Google Tag Manager and cookiebot.eu and others), adding 2.3 MB and 553 ms of main-thread time.

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 750 ms.

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

cloudfront.net costs a phone 317 ms of main-thread work and 1.8 MB 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.

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

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

Google Tag Manager costs a phone 182 ms of main-thread work and 335 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 15 KiB of CSS is downloaded but never applied on this page.

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

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.

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

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

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

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

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

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

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

6 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 2.4 s to 2.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 2.7 MB in 37 requests on a phone: images 1.3 MB (16), scripts 1,004 KiB (12) and fonts 330 KiB (5). Under 2 MB keeps phones on slow connections fast.

themabanner 2025 390x200 stramien_v2 -.jpg 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.76 g of CO₂e: 91.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

Form elements should have a visible label: 1 element on the page fails this check, rated serious by axe-core.

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.

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

Your title is 67 characters, so Google will cut it off around 60: “Vomar Voordeelmarkt | Altijd een lage prijs voor al je boodschappen”.

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

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

Your meta description is 270 characters; Google truncates after about 160, so the end of your pitch is cut.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

1 link has no real href, so search engines can't follow it.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 36 pages on vomar.nl and 10 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.

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

https://www.vomar.nl/sparen, https://www.vomar.nl/producten/baby-kind, https://www.vomar.nl/producten/bier-wijn-sterke-drank, https://www.vomar.nl/producten/diepvries, https://www.vomar.nl/producten/drogisterij and https://www.vomar.nl/producten/frisdrank-sappen-koffie-thee and 5 others all use the title “Vomar Voordeelmarkt”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.vomar.nl/producten/baby-kind, https://www.vomar.nl/producten/bier-wijn-sterke-drank, https://www.vomar.nl/producten/diepvries, https://www.vomar.nl/producten/drogisterij, https://www.vomar.nl/producten/frisdrank-sappen-koffie-thee and https://www.vomar.nl/producten/huisdieren and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.vomar.nl/kik has no <h1> headline, so visitors and search engines get no clear main topic.

https://www.vomar.nl/folders, https://www.vomar.nl/producten, https://www.vomar.nl/winkels, https://www.vomar.nl/sparen, https://www.vomar.nl/producten/baby-kind and https://www.vomar.nl/producten/bier-wijn-sterke-drank and 8 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

https://www.vomar.nl/producten/huishouden, https://www.vomar.nl/producten/koken-tafelen-non-food, https://www.vomar.nl/producten/vers and https://www.vomar.nl/producten/voorraadkast took over 3 s to send their HTML from our server.

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

1 error was logged to the browser console while the page loaded, for example “Uncaught TypeError: Cannot read properties of undefined (reading 'addEventListener')”.

2 images are served at too low a resolution for sharp phone screens.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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

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

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

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

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