Website review, no card needed
buissonniere.com website review
Visit site (opens in a new tab)Reviewed 24 October 202643 issues · 80 checks
This review found 43 issues worth fixing on buissonniere.com, 21 of them high impact, across 80 checks. The most urgent: reduce unused JavaScript. 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
61D- #113,804 of 117,615 reviewed websitesbeats 3%
- #66,104 of 66,923 online storesbeats 1%
- #632 of 711 Magento storesbeats 9%
Closest competitors among Magento stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 1.9 s |
| May 9, 2026 | 1.9 s |
| May 16, 2026 | 1.8 s |
| May 23, 2026 | 1.8 s |
| May 30, 2026 | 1.7 s |
| Jun 6, 2026 | 1.7 s |
| Jun 13, 2026 | 1.7 s |
| Jun 20, 2026 | 1.7 s |
| Jun 27, 2026 | 1.7 s |
| Jul 4, 2026 | 1.7 s |
| Jul 11, 2026 | 1.7 s |
| Jul 18, 2026 | 1.7 s |
| Jul 25, 2026 | 1.8 s |
| Aug 1, 2026 | 1.7 s |
| Aug 8, 2026 | 1.7 s |
| Aug 15, 2026 | 1.7 s |
| Aug 22, 2026 | 1.6 s |
| Aug 29, 2026 | 1.6 s |
| Sep 5, 2026 | 1.6 s |
| Sep 12, 2026 | 1.6 s |
| Sep 19, 2026 | 1.6 s |
| Sep 26, 2026 | 1.6 s |
| Oct 3, 2026 | 1.6 s |
| Oct 10, 2026 | 1.6 s |
| Oct 17, 2026 | 1.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 195 ms |
| May 9, 2026 | 187 ms |
| May 16, 2026 | 184 ms |
| May 23, 2026 | 177 ms |
| May 30, 2026 | 176 ms |
| Jun 6, 2026 | 176 ms |
| Jun 13, 2026 | 171 ms |
| Jun 20, 2026 | 170 ms |
| Jun 27, 2026 | 175 ms |
| Jul 4, 2026 | 178 ms |
| Jul 11, 2026 | 184 ms |
| Jul 18, 2026 | 184 ms |
| Jul 25, 2026 | 179 ms |
| Aug 1, 2026 | 180 ms |
| Aug 8, 2026 | 182 ms |
| Aug 15, 2026 | 189 ms |
| Aug 22, 2026 | 196 ms |
| Aug 29, 2026 | 202 ms |
| Sep 5, 2026 | 202 ms |
| Sep 12, 2026 | 203 ms |
| Sep 19, 2026 | 204 ms |
| Sep 26, 2026 | 204 ms |
| Oct 3, 2026 | 204 ms |
| Oct 10, 2026 | 201 ms |
| Oct 17, 2026 | 200 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
How it loaded on a phone
0.7 s
1.5 s
2.2 s
3.0 s
3.7 s
4.4 s
5.2 s
5.9 s
Speed
Reduce unused JavaScript
11.3 s · 2.8 MBAbout 2.8 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 11.3 s faster on a phone.
Avoid multiple page redirects
4.1 sThe page goes through 2 redirects before it starts loading, costing about 4.1 s. Link and advertise the final URL directly.
Mobile performance score: 10
10/100Your mobile performance score is 10 (desktop: 12). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 7.8 s
A phone's processor spends 7.8 s on main-thread work while loading, 4.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Reduce unused CSS
600 ms · 342 KiBAbout 342 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 304 ms. During a long task the page ignores taps.
Minify JavaScript
37 KiB37 KiB could be saved by minifying JavaScript.
1 third-party service on the page
1 third-party service load with your homepage (hlx.page), adding 4 KiB and 0 ms of main-thread time.
1 checks passed
Server response: 11 ms
11 msYour server sent the HTML in 11 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
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.
First Contentful Paint: 9.4 s
9.4 sThe first text or image appears after 9.4 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 63.5 s
63.5 sYour largest element takes 63.5 s to render on a phone. Google's threshold for “good” is 2.5 s.
Speed Index: 24.2 s
24.2 sVisually, the page fills in at 24.2 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 65.9 s
65.9 sThe page becomes fully interactive after 65.9 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.915
0.915The layout shifts by 0.915 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Total Blocking Time: 928 ms
928 msScripts block taps and scrolling for 928 ms in total while the page loads. Good is under 200 ms.
Real-user INP: 223 ms
223 msReal visitors wait 223 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.12
0.12For real visitors the layout shifts by 0.12 (75th percentile). Good is under 0.1.
4 images without width and height
4 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+5%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 195 ms to 200 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user LCP: 1.6 s
1.6 sReal visitors wait 1.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 1.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 778 ms
778 msReal visitors wait 778 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 19% faster for real visitors
-19%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.9 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 54.1 MB in 246 requests
54.1 MBYour homepage downloads 54.1 MB in 246 requests on a phone: other files 37.0 MB (90), images 12.4 MB (33) and scripts 3.5 MB (78). Under 2 MB keeps phones on slow connections fast.
5 images over 500 KB
5 images weigh 8.6 MB together. On a phone connection a single image that size takes seconds.
7 images far larger than shown
7.1 MB7 images are downloaded at several times the size a phone draws them, for example POST_N_1_21-02_16.png at 1,200 px wide, shown at 185 px. Resized copies would save about 7.1 MB.
About 15.3 g of CO₂ per visit
15.33 gBy the Sustainable Web Design model, a visit to your homepage emits about 15.33 g of CO₂e: 1840.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
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.
Accessibility
Images must have alternative text (1 element)
Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.
2 text elements with low contrast
2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
ARIA dialog and alertdialog nodes should have an accessible name (1 element)
ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
Orphan list items
Some list items are not inside a list.
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
10 links without text
10 visible links have no text or label, so screen readers cannot say where they go.
1 checks passed
43 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: 43 passed and 7 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
310 internal links, 11 external
The homepage links to 310 pages on buissonniere.com and 11 external pages.
5 checks passed
Meta description: 135 characters
Your meta description is 135 characters: “Des vêtements de qualité à prix juste, livrés directement chez vous. Découvrez notre nouvelle collection en ligne et da…”.
Title: 65 characters
Your title is a healthy 65 characters: “Buissonnière : Prêt-à-porter et Accessoires pour toute la famille”.
Canonical URL set
The canonical URL is https://buissonniere.com/fr/.
robots.txt in place
robots.txt is in place.
XML sitemap found
Your XML sitemap is reachable at https://buissonniere.com/sitemap.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://buissonniere.com/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.
1 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.
Other pages
2 pages share a title
https://buissonniere.com/fr/bebes and https://buissonniere.com/fr/bebes/collection all use the title “Collection pour Bébés”. Search engines can't tell which page to show for a search, so each competes with the others.
4 pages share a meta description
https://buissonniere.com/fr/privacy-policy-cookie-restriction-mode and https://buissonniere.com/fr/bebes/collection/pulls-cardigans-sweatshirts use the same meta description. A description written for each page earns more clicks.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://buissonniere.com/fr/privacy-policy-cookie-restriction-mode, whose canonical is https://buissonniere.com/fr/rgpd. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
1 page without an H1
https://buissonniere.com/fr/privacy-policy-cookie-restriction-mode has no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 123 found) and read each the way a search engine does.
4 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Every page has a meta description
All 15 pages that loaded have a meta description.
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
2 third-party cookies
2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
14 of 16 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
A 8-field form
Your longest form asks for 8 fields (0 required). Every extra field lowers completion.
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.
Only about 87 words
The homepage has only about 87 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Learn more”.
10 calls to action
The homepage has 10 calls to action, for example “Shop By” and “Shop By Basculer vers”.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Meta 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.
29 cookies set on arrival
29Opening the homepage sets 29 cookies, 2 of them by other companies (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.
29 other companies contacted
Loading the homepage contacts 29 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 buissonniere.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- E-commerce
- Magento
- Analytics
- Google Tag Manager
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 43 issues on buissonniere.com, including 16 speed issues, 4 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.