Website review, no card needed
wellbabyness.be website review
Visit site (opens in a new tab)Reviewed 17 November 202627 issues · 71 checks
This review found 27 issues worth fixing on wellbabyness.be, 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
75C- #79,209 of 120,620 reviewed websitesbeats 30%
- #50,525 of 68,290 online storesbeats 22%
- #1,347 of 2,791 WooCommerce storesbeats 45%
Closest competitors among WooCommerce stores
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
1.5 s
3.0 s
4.5 s
6.0 s
7.4 s
8.9 s
10.4 s
11.9 s
Speed
Render-blocking requests
3.1 s44 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.1 s.
Reduce unused JavaScript
900 ms · 238 KiBAbout 238 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 900 ms faster on a phone.
Mobile performance score: 59
59/100Your mobile performance score is 59. Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
450 ms · 92 KiBAbout 92 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
Google Tag Manager adds 288 ms
288 msGoogle Tag Manager costs a phone 288 ms of main-thread work and 309 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.
Improve image delivery
300 ms · 13 KiB1 image could be 13 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.
Main-thread work: 2.9 s
A phone's processor spends 2.9 s on main-thread work while loading, 963 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
5 third-party services on the page
5 third-party services load with your homepage (Google Tag Manager, cdn-cookieyes.com and optimole.com and others), adding 426 KiB and 354 ms of main-thread time.
Legacy JavaScript
150 ms · 35 KiBPolyfills for old browsers add 35 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
12 long tasks on the main thread
12 long tasks block the main thread while loading, the longest for 137 ms. During a long task the page ignores taps.
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.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 23 ms
23 msYour server sent the HTML in 23 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 8.6 s
8.6 sYour largest element takes 8.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 7.7 s
7.7 sVisually, the page fills in at 7.7 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 8.6 s
8.6 sThe page becomes fully interactive after 8.6 s. Good is under 3.8 s.
Total Blocking Time: 341 ms
341 msScripts block taps and scrolling for 341 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 1.9 s
1.9 sThe first text or image appears after 1.9 s on a phone. Good is under 1.8 s.
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.
1 checks passed
Cumulative Layout Shift: 0.008
0.008The layout barely moves while loading (CLS 0.008, good is under 0.1).
Images and page weight
About 0.4 g of CO₂ per visit
0.38 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.38 g of CO₂e: 45.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
4 checks passed
Page weight: 1.3 MB in 122 requests
1.3 MBYour homepage downloads 1.3 MB in 122 requests on a phone: scripts 667 KiB (54), fonts 438 KiB (9) and stylesheets 165 KiB (42). That is a lean page.
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
15 text elements with low contrast
15 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 (4 elements)
All page content should be contained by landmarks: 4 elements on the page fail this check, rated moderate by axe-core.
4 links without text
4 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h1 → h5), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 6 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 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 3 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
2 H1 headlines
There are 2 <h1> headlines (“Jouw mooiste momenten, tastbaar gemaakt in een un…” and “Ook genieten van onze Privé Babyspa”). One clear main headline is easier for people and search engines.
No XML sitemap
No XML sitemap at https://wellbabyness.be/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at wellbabyness.be/robots.txt, the first file search crawlers ask for.
28 internal links, 8 external
The homepage links to 28 pages on wellbabyness.be and 8 external pages.
5 checks passed
Meta description: 136 characters
Your meta description is 136 characters: “Zwangerschapsbeeldjes en babyspa - Wellbabyness: Vereeuwig je zwangerschap met een 3D-beeldje en geniet van ontspanning…”.
Title: 46 characters
Your title is a healthy 46 characters: “Zwangerschapsbeeldjes & Babyspa | Wellbabyness”.
Canonical URL set
The canonical URL is https://wellbabyness.be/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, Organization, WebPage and WebSite.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
AI search readiness
2 checks passed
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (191 words), so crawlers that don't run JavaScript still read it.
Other pages
9 pages without a meta description
https://wellbabyness.be/zwangerschapsbeeldjes-op-basis-van-fotos, https://wellbabyness.be/babyspa-2, https://wellbabyness.be/arrangementen, https://wellbabyness.be/winkel, https://wellbabyness.be/contact and https://wellbabyness.be/product-categorie/cadeau/cadeaubonnen and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://wellbabyness.be/portretbeeldjes and https://wellbabyness.be/dierenbeeldje use the same meta description. A description written for each page earns more clicks.
3 pages without an H1
https://wellbabyness.be/babyspa-2, https://wellbabyness.be/contact and https://wellbabyness.be/product-categorie/cadeau/cadeaubonnen have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://wellbabyness.be/contact has 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.
13 internal pages checked
We fetched 13 pages linked from your homepage and read each the way a search engine does.
5 checks passed
Linked pages load
12 pages of 13 loaded without an error (the rest turned automated requests away).
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Titles are unique
Every page we checked has its own title.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 12 pages that loaded have a <title>.
Best practices
3 small tap targets
3 of 12 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Unexpected token '...'”.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
1 checks passed
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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
Local business without LocalBusiness data
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.
Only about 169 words
The homepage has only about 169 words of visible text; thin pages give Google and first-time buyers little to go on.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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.
5 checks passed
2 calls to action
The homepage has 2 calls to action, for example “Contact”.
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
Direct contact links
Visitors can reach you directly: 2 phone links and 1 email link.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
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). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.
2 cookies set on arrival
2Opening the homepage sets 2 cookies (measured from a US location before any click).
7 other companies contacted
Loading the homepage contacts 7 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: CookieYes
A consent management tool (CookieYes) loads with the page.
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 wellbabyness.be, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- jQuery
- E-commerce
- WooCommerce
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- Snel.com B.V.
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 27 issues on wellbabyness.be, including 12 speed issues, 3 SEO issues 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.