mama-2b.nl website review

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

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

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

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

About 606 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.

Your mobile performance score is 56. Pages that score under 90 lose visitors before the first paint.

The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

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

2 third-party services load with your homepage (trustindex.io and Google Fonts), adding 93 KiB and 29 ms of main-thread time.

20 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 15.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Welkom bij Mama2B Een zwangerschap is een bijzondere period…”.

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

2 images weigh 1.3 MB together. On a phone connection a single image that size takes seconds.

Your homepage downloads 3.5 MB in 71 requests on a phone: images 1.7 MB (13), scripts 1.0 MB (22) and stylesheets 490 KiB (31). Under 2 MB keeps phones on slow connections fast.

3 images (1.4 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.

2 images further down the page (1.3 MB) 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 0.99 g of CO₂e: 118.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

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

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

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.

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

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

There are 5 <h1> headlines (“Welkom bij Mama2B”, “Onze diensten” and “Anderen over Mama-2B”). One clear main headline is easier for people and search engines.

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

There is no robots.txt at mama-2b.nl/robots.txt, the first file search crawlers ask for.

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

The homepage links to 116 pages on mama-2b.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.

https://mama-2b.nl/werkgebied, https://mama-2b.nl/spreekuur-locaties, https://mama-2b.nl/ons-team, https://mama-2b.nl/namenboekje, https://mama-2b.nl/verhuur and https://mama-2b.nl/samenwerking and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://mama-2b.nl/spreekuur-locaties took over 3 s to send its HTML from our server.

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

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

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

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.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

There is no form on the homepage, so every lead has to click through to another page first.

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

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 4 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.