Website review, no card needed
mamagroeit.nl website review
Visit site (opens in a new tab)Reviewed 12 November 202620 issues · 71 checks
This review found 20 issues worth fixing on mamagroeit.nl, 7 of them high impact, across 71 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
85BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Jul 25, 2026 | 1.7 s |
| Aug 1, 2026 | 1.6 s |
| Aug 8, 2026 | 1.6 s |
| Aug 15, 2026 | 1.8 s |
| Aug 29, 2026 | 2.2 s |
| Sep 5, 2026 | 2.4 s |
| Sep 12, 2026 | 2.2 s |
| Sep 19, 2026 | 2.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Jul 25, 2026 | 86 ms |
| Aug 1, 2026 | 83 ms |
| Aug 8, 2026 | 89 ms |
| Aug 15, 2026 | 82 ms |
| Aug 29, 2026 | 82 ms |
| Sep 12, 2026 | 82 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
Speed
Render-blocking requests
1.8 s15 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.8 s.
Use efficient cache lifetimes
750 ms · 522 KiB39 files are served with short cache lifetimes, so returning visitors download them again (522 KiB).
Reduce unused CSS
470 ms · 97 KiBAbout 97 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 470 ms faster on a phone.
Reduce unused JavaScript
150 ms · 136 KiBAbout 136 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
Font display
150 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).
5 third-party services on the page
5 third-party services load with your homepage (Google Tag Manager, pzz.io and Google Fonts and others), adding 192 KiB and 122 ms of main-thread time.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 81 ms. During a long task the page ignores taps.
Improve image delivery
54 KiB3 images could be 54 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Legacy JavaScript
10 KiBPolyfills for old browsers add 10 KiB JavaScript that modern phones do not need.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
3 checks passed
Mobile performance score: 90
90/100Your mobile performance score is 90. That is in Google's “good” band (90 and up).
Main-thread work: 0.4 s
A phone's processor spends 0.4 s on main-thread work while loading, 137 ms of it running JavaScript. That is comfortably low.
Server response: 182 ms
182 msYour server sent the HTML in 182 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Speed Index: 6.0 s
6.0 sVisually, the page fills in at 6.0 s (Speed Index). Good is under 3.4 s.
Largest content (LCP) got 38% slower for real visitors
+38%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.7 s to 2.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 2.3 s
2.3 sThe first text or image appears after 2.3 s on a phone. Good is under 1.8 s.
Time to Interactive: 4.2 s
4.2 sThe page becomes fully interactive after 4.2 s. Good is under 3.8 s.
6 images without width and height
6 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-3%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 86 ms to 82 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Not enough real-visitor data yet
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.
3 checks passed
Largest Contentful Paint: 2.3 s
2.3 sYour largest element renders in 2.3 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Van babyuitzet tot de beste oefenbroekjes voor de zindelijk…”.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 38 ms
38 msScripts block the page for only 38 ms while loading. Good is under 200 ms.
Images and page weight
5 images below the first screen load straight away
5 images further down the page (223 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.2 g of CO₂ per visit
0.21 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.21 g of CO₂e: 25.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Page weight: 759 KiB in 45 requests
759 KiBYour homepage downloads 759 KiB in 45 requests on a phone: scripts 317 KiB (18), images 279 KiB (9) and stylesheets 113 KiB (13). That is a lean page.
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Links look like plain text
15 links inside paragraphs rely on colour alone to stand out.
Links must have discernible text (5 elements)
Links must have discernible text: 5 elements on the page fail this check, rated serious by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
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.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
2 checks passed
Every image has alt text
All 15 images in the HTML carry an alt attribute.
46 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 4 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (24 characters)
Your title is only 24 characters: “MamaGroeit - Mama Groeit”. Between 30 and 65 characters leaves room to say what you do and for whom.
142 internal links, 3 external
The homepage links to 142 pages on mamagroeit.nl and 3 external pages.
7 checks passed
Meta description: 127 characters
Your meta description is 127 characters: “De beste koopadvies/koopgidsen, eerlijke reviews, prachtige bevallingsverhalen en veel andere artikel lees je op MAMAGR…”.
One H1 headline
Your main headline reads: “MamaGroeit”.
Canonical URL set
The canonical URL is https://mamagroeit.nl/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, WebPage and WebSite.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://mamagroeit.nl/sitemap_index.xml.
AI search readiness
No Organization structured data
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.
No llms.txt
There is no https://mamagroeit.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.
2 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (1,540 words), so crawlers that don't run JavaScript still read it.
Other pages
3 pages slow to respond
https://mamagroeit.nl/babysokken-die-blijven-zitten-dit-zijn-de-beste, https://mamagroeit.nl/schommelstoel-babykamer-10x-de-beste-rocking-chairs and https://mamagroeit.nl/beste-luieremmer took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 100 found) and read each the way a search engine does.
7 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 15 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
9 small tap targets
9 of 27 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
No calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 1,257 words of copy
The homepage carries about 1,257 words of visible text.
2 checks passed
2 short forms
2 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Analytics.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (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.
3 cookies set on arrival
3Opening the homepage sets 3 cookies (measured from a US location before any click).
No consent tool detected
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.
6 other companies contacted
Loading the homepage contacts 6 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at mamagroeit.nl, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
- The footer still says © 2023.
Stack
- CMS
- WordPress
- Framework
- jQuery
- Analytics
- Google Analytics
- Hosting
- Jeroen van Brink trading as Infrapod
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 20 issues on mamagroeit.nl, including 8 speed issues, 1 SEO issue and 4 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.