badabulle.com website review

Shopify costs a phone 1.2 s of main-thread work and 7.6 MB 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.

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

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

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

8 third-party services load with your homepage (Shopify, tolk.ai and tncapp.com and others), adding 8.2 MB and 1.6 s of main-thread time.

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

About 638 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 330 ms faster on a phone.

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

8 images could be 287 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

tolk.ai costs a phone 212 ms of main-thread work and 395 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.

14 files are served with short cache lifetimes, so returning visitors download them again (176 KiB).

52 KiB could be saved by minifying JavaScript.

Polyfills for old browsers add 31 KiB JavaScript that modern phones do not need.

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

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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

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

Your largest element takes 6.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 130 ms to 171 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.4 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 9.6 MB in 312 requests on a phone: images 6.6 MB (46), scripts 1.5 MB (86) and other files 1.0 MB (139). Under 2 MB keeps phones on slow connections fast.

huile_anti_vergeture.svg weighs 4.4 MB. On a phone connection a single image that size takes seconds.

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

1 image has no alt text, which hurts accessibility and image search.

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

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

Your title is 69 characters, so Google will cut it off around 60: “Babymoov® Site Officiel | Puériculture & Produits bébé garantis à vie”.

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

The homepage links to 230 pages on badabulle.com and 5 external pages.

https://babymoov.com/pages/contact is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://babymoov.com/collections/nos-imparfaits has no meta description, so Google writes the search snippet from whatever text it finds.

https://babymoov.com/pages/contact, https://babymoov.com/pages/re-babymoov, https://babymoov.com/pages/marque-badabulle, https://babymoov.com/pages/doomoo-grow-in-comfort and https://babymoov.com/pages/la-boutique-a-cadeaux have no <h1> headline, so visitors and search engines get no clear main topic.

https://babymoov.com/collections/soins-grossesse-hydratation-doomoo-shinncare took over 3 s to send its HTML from our server.

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

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

4 errors were logged to the browser console while the page loaded, for example “[Regios Discounts] [USER ERROR] You must embed the "Discounts Embed" for this feature to work: CollectionPage”.

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

Before a visitor clicks anything, the page loads Amazon Ads, Meta Pixel, Pinterest Tag, Snap Pixel and TikTok Pixel (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.

Opening the homepage sets 17 cookies (measured from a US location before any click).

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