Website review, no card needed
bledina.com website review
Visit site (opens in a new tab)Reviewed 19 November 202641 issues · 80 checks
This review found 41 issues worth fixing on bledina.com, 16 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
76CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 1.8 s |
| Jun 6, 2026 | 1.8 s |
| Jun 13, 2026 | 1.8 s |
| Jun 20, 2026 | 1.8 s |
| Jun 27, 2026 | 1.9 s |
| Jul 4, 2026 | 1.9 s |
| Jul 11, 2026 | 1.9 s |
| Jul 18, 2026 | 1.9 s |
| Jul 25, 2026 | 1.9 s |
| Aug 1, 2026 | 1.9 s |
| Aug 8, 2026 | 2.0 s |
| Aug 15, 2026 | 2.0 s |
| Aug 22, 2026 | 2.1 s |
| Aug 29, 2026 | 2.1 s |
| Sep 5, 2026 | 2.1 s |
| Sep 12, 2026 | 2.1 s |
| Sep 19, 2026 | 2.2 s |
| Sep 26, 2026 | 2.2 s |
| Oct 3, 2026 | 2.3 s |
| Oct 10, 2026 | 2.3 s |
| Oct 17, 2026 | 2.3 s |
| Oct 24, 2026 | 2.4 s |
| Oct 31, 2026 | 2.4 s |
| Nov 7, 2026 | 2.4 s |
| Nov 14, 2026 | 2.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 103 ms |
| Jun 6, 2026 | 103 ms |
| Jun 13, 2026 | 104 ms |
| Jun 20, 2026 | 104 ms |
| Jun 27, 2026 | 107 ms |
| Jul 4, 2026 | 111 ms |
| Jul 11, 2026 | 112 ms |
| Jul 18, 2026 | 113 ms |
| Jul 25, 2026 | 114 ms |
| Aug 1, 2026 | 114 ms |
| Aug 8, 2026 | 117 ms |
| Aug 15, 2026 | 120 ms |
| Aug 22, 2026 | 120 ms |
| Aug 29, 2026 | 120 ms |
| Sep 5, 2026 | 121 ms |
| Sep 12, 2026 | 122 ms |
| Sep 19, 2026 | 125 ms |
| Sep 26, 2026 | 129 ms |
| Oct 3, 2026 | 133 ms |
| Oct 10, 2026 | 136 ms |
| Oct 17, 2026 | 139 ms |
| Oct 24, 2026 | 142 ms |
| Oct 31, 2026 | 145 ms |
| Nov 7, 2026 | 148 ms |
| Nov 14, 2026 | 148 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
1.1 s
2.2 s
3.4 s
4.5 s
5.6 s
6.7 s
7.8 s
8.9 s
Speed
Reduce unused JavaScript
1.9 s · 730 KiBAbout 730 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.9 s faster on a phone.
Render-blocking requests
1.8 s5 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.8 s.
Improve image delivery
1.2 MB10 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
8 third-party services on the page
8 third-party services load with your homepage (digital4danone.com, danone-dtc.net and azure.com and others), adding 2.3 MB and 920 ms of main-thread time.
Mobile performance score: 50
50/100Your mobile performance score is 50. Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
750 ms · 144 KiBAbout 144 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.
Use efficient cache lifetimes
858 KiB45 files are served with short cache lifetimes, so returning visitors download them again (858 KiB).
digital4danone.com adds 443 ms
443 msdigital4danone.com costs a phone 443 ms of main-thread work and 1.3 MB 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.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 440 ms. During a long task the page ignores taps.
danone-dtc.net adds 275 ms
275 msdanone-dtc.net costs a phone 275 ms of main-thread work and 711 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.
Main-thread work: 3.2 s
A phone's processor spends 3.2 s on main-thread work while loading, 1.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Legacy JavaScript
47 KiBPolyfills for old browsers add 47 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.
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: 4 ms
4 msYour server sent the HTML in 4 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: 6.5 s
6.5 sThe first text or image appears after 6.5 s on a phone. Good is under 1.8 s.
Time to Interactive: 16.9 s
16.9 sThe page becomes fully interactive after 16.9 s. Good is under 3.8 s.
Largest Contentful Paint: 6.5 s
6.5 sYour largest element takes 6.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Le lait maternel est ce qu’il y a de mieux et apporte tous …”.
Speed Index: 9.3 s
9.3 sVisually, the page fills in at 9.3 s (Speed Index). Good is under 3.4 s.
Real-user CLS: 0.12
0.12For real visitors the layout shifts by 0.12 (75th percentile). Good is under 0.1.
Tap response (INP) got 44% slower for real visitors
+44%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 103 ms to 148 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 30% slower for real visitors
+30%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.8 s to 2.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 382 ms
382 msScripts block taps and scrolling for 382 ms in total while the page loads. Good is under 200 ms.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
5 checks passed
Real-user LCP: 1.7 s
1.7 sReal visitors wait 1.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 147 ms
147 msReal visitors wait 147 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 463 ms
463 msReal visitors wait 463 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.001
0.001The layout barely moves while loading (CLS 0.001, good is under 0.1).
Images and page weight
1 image over 500 KB
header-contact-dsk.png weighs 617 KiB. On a phone connection a single image that size takes seconds.
5 images far larger than shown
700 KiB5 images are downloaded at several times the size a phone draws them, for example header-contact-dsk.png at 1,280 px wide, shown at 120 px. Resized copies would save about 700 KiB.
Page weight: 3.2 MB in 104 requests
3.2 MBYour homepage downloads 3.2 MB in 104 requests on a phone: scripts 1.4 MB (43), images 1.3 MB (12) and stylesheets 175 KiB (5). Under 2 MB keeps phones on slow connections fast.
1 image in older formats
1 image (617 KiB) is 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.
1 image below the first screen load straight away
1 image further down the page (39 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 0.9 g of CO₂ per visit
0.89 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.89 g of CO₂e: 107.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Images must have alternative text (3 elements)
Images must have alternative text: 3 elements on the page fail 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.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
3 buttons without a name
3 buttons have no accessible name, so screen readers announce just “button”.
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.
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.
1 checks passed
44 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: 44 passed and 6 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
3 H1 headlines
There are 3 <h1> headlines (“Bien manger s'apprend petit à petit”, “Alimentation bébé” and “Développement et santé de bébé”). One clear main headline is easier for people and search engines.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
85 internal links, 11 external
The homepage links to 85 pages on bledina.com and 11 external pages.
6 checks passed
Meta description: 122 characters
Your meta description is 122 characters: “De 4/6 à 36 mois, des gammes adaptées aux besoins spécifiques de bébé ! Des produits, conseils et des Recettes pour béb…”.
Title: 61 characters
Your title is a healthy 61 characters: “Blédina : Repas et recettes pour l'alimentation de votre bébé”.
Canonical URL set
The canonical URL is https://www.bledina.com/.
Structured data in place
Structured data found: Brand, Organization, WebPage and WebSite.
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://www.bledina.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.bledina.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.
3 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.
Organization data: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (1,002 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page hidden from search
https://www.bledina.com/deconnexion is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
4 pages without a meta description
https://www.bledina.com/deconnexion, https://www.bledina.com/shop/laits-bebe/lait-de-croissance, https://www.bledina.com/shop/plats-cuisines-bebe and https://www.bledina.com/shop/gamme-vegetale have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://www.bledina.com/deconnexion 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 64 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.
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.
Every page has a title
All 13 pages that loaded have a <title>.
Best practices
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Connecting to 'https://use.typekit.net/uvd6lwx.css' violates the following Content Security Policy directive: "connect-…”.
2 checks passed
Tap targets are thumb-sized
22 of 25 tappable elements near the top are at least 24 px.
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.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 870 words of copy
The homepage carries about 870 words of visible text.
2 checks passed
3 calls to action
The homepage has 3 calls to action, for example “Le shop” and “Nouveaux sur le shop”.
Direct contact links
Visitors can reach you directly: 3 phone links and 0 email links.
Privacy and tracking
2 cookies set on arrival
2Opening the homepage sets 2 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.
19 other companies contacted
Loading the homepage contacts 19 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 bledina.com, 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
- Hosting
- Fastly
Company
- Founded
- 1881
- Headquarters
- Limonest
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 41 issues on bledina.com, including 21 speed issues, 2 SEO issues and 3 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.