Website review, no card needed
bleulibellule.com website review
Visit site (opens in a new tab)Reviewed 27 October 202639 issues · 92 checks
This review found 39 issues worth fixing on bleulibellule.com, 12 of them high impact, across 92 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
79C- #52,732 of 116,735 reviewed websitesbeats 49%
- #35,131 of 66,814 online storesbeats 41%
- #29 of 166 PrestaShop storesbeats 78%
Closest competitors among PrestaShop stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.0 s |
| May 16, 2026 | 2.0 s |
| May 23, 2026 | 2.0 s |
| May 30, 2026 | 2.0 s |
| Jun 6, 2026 | 2.0 s |
| Jun 13, 2026 | 2.0 s |
| Jun 20, 2026 | 2.0 s |
| Jun 27, 2026 | 2.0 s |
| Jul 4, 2026 | 2.0 s |
| Jul 11, 2026 | 2.1 s |
| Jul 18, 2026 | 2.1 s |
| Jul 25, 2026 | 2.1 s |
| Aug 1, 2026 | 2.1 s |
| Aug 8, 2026 | 2.1 s |
| Aug 15, 2026 | 2.1 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.1 s |
| Sep 26, 2026 | 2.1 s |
| Oct 3, 2026 | 2.1 s |
| Oct 10, 2026 | 2.1 s |
| Oct 17, 2026 | 2.1 s |
| Oct 24, 2026 | 2.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 122 ms |
| May 16, 2026 | 121 ms |
| May 23, 2026 | 121 ms |
| May 30, 2026 | 121 ms |
| Jun 6, 2026 | 121 ms |
| Jun 13, 2026 | 121 ms |
| Jun 20, 2026 | 123 ms |
| Jun 27, 2026 | 123 ms |
| Jul 4, 2026 | 125 ms |
| Jul 11, 2026 | 126 ms |
| Jul 18, 2026 | 126 ms |
| Jul 25, 2026 | 124 ms |
| Aug 1, 2026 | 124 ms |
| Aug 8, 2026 | 125 ms |
| Aug 15, 2026 | 125 ms |
| Aug 22, 2026 | 127 ms |
| Aug 29, 2026 | 127 ms |
| Sep 5, 2026 | 128 ms |
| Sep 12, 2026 | 128 ms |
| Sep 19, 2026 | 128 ms |
| Sep 26, 2026 | 128 ms |
| Oct 3, 2026 | 126 ms |
| Oct 10, 2026 | 124 ms |
| Oct 17, 2026 | 124 ms |
| Oct 24, 2026 | 123 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.4 s
0.8 s
1.3 s
1.7 s
2.1 s
2.5 s
3.0 s
3.4 s
Speed
Reduce unused JavaScript
1.1 s · 617 KiBAbout 617 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.1 s faster on a phone.
3,298 HTML elements
The page has 3,298 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Mobile performance score: 66
66/100Your mobile performance score is 66 (desktop: 56). Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
950 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 950 ms.
Use efficient cache lifetimes
250 ms · 472 KiB26 files are served with short cache lifetimes, so returning visitors download them again (472 KiB).
Main-thread work: 2.3 s
A phone's processor spends 2.3 s on main-thread work while loading, 1.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
ZenDesk adds 130 ms
130 msZenDesk costs a phone 130 ms of main-thread work and 423 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.
8 third-party services on the page
8 third-party services load with your homepage (ZenDesk, Snapchat and Didomi and others), adding 959 KiB and 438 ms of main-thread time.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 137 ms. During a long task the page ignores taps.
Reduce unused CSS
19 KiBAbout 19 KiB of CSS is downloaded but never applied on this page.
Improve image delivery
15 KiB2 images could be 15 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
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: 5 ms
5 msYour server sent the HTML in 5 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.
Time to Interactive: 14.8 s
14.8 sThe page becomes fully interactive after 14.8 s. Good is under 3.8 s.
Largest Contentful Paint: 6.3 s
6.3 sYour largest element takes 6.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “-20% dès 2 sur Série Expert”.
Real-user CLS: 0.23
0.23For real visitors the layout shifts by 0.23 (75th percentile). Good is under 0.1.
Real-user TTFB: 903 ms
903 msReal visitors wait 903 ms for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 4.8 s
4.8 sVisually, the page fills in at 4.8 s (Speed Index). Good is under 3.4 s.
25 images without width and height
25 images have no width and height attributes, so the layout jumps as each one loads.
Total Blocking Time: 308 ms
308 msScripts block taps and scrolling for 308 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) held steady for real visitors
+2%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 122 ms to 123 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+1%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.0 s to 2.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 2.1 s
2.1 sReal visitors wait 2.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 158 ms
158 msReal visitors wait 158 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
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.
Cumulative Layout Shift: 0.073
0.073The layout barely moves while loading (CLS 0.073, good is under 0.1).
First Contentful Paint: 1.2 s
1.2 sThe first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.
Images and page weight
Page weight: 2.1 MB in 123 requests
2.1 MBYour homepage downloads 2.1 MB in 123 requests on a phone: scripts 1.4 MB (41), images 324 KiB (34) and fonts 275 KiB (8). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
1601-image_mobile.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
1 image in older formats
1 image (57 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.
About 0.6 g of CO₂ per visit
0.59 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.59 g of CO₂e: 71.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
26 buttons without a name
26 buttons have no accessible name, so screen readers announce just “button”.
26 tap targets too small
26 tap targets are too small or too close together to hit reliably with a finger.
Links look like plain text
2 links inside paragraphs rely on colour alone to stand out.
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (95 elements)
All page content should be contained by landmarks: 95 elements on the page fail this check, rated moderate by axe-core.
27 form fields without a label
27 form fields have no label, so screen readers announce an empty box and autofill guesses.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
ARIA role should be appropriate for the element (4 elements)
ARIA role should be appropriate for the element: 4 elements on the page fail this check, rated minor by axe-core.
Elements marked as presentational should be consistently ignored (4 elements)
Elements marked as presentational should be consistently ignored: 4 elements on the page fail this check, rated minor by axe-core.
Alternative text of images should not be repeated as text (3 elements)
Alternative text of images should not be repeated as text: 3 elements on the page fail this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 82 images in the HTML carry an alt attribute.
49 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 59 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 10 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (95 characters)
Your title is 95 characters, so Google will cut it off around 60: “Coiffure et esthétique, produits de marques pour particuliers et professionnels- Bleu Lib…”.
Meta description is long (198 characters)
Your meta description is 198 characters; Google truncates after about 160, so the end of your pitch is cut.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
268 internal links, 10 external
The homepage links to 268 pages on bleulibellule.com and 10 external pages.
6 checks passed
One H1 headline
Your main headline reads: “Produits coiffure et beauté”.
Canonical URL set
The canonical URL is https://www.bleulibellule.com/.
Structured data in place
Structured data found: Organization.
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://www.bleulibellule.com/1_index_sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.bleulibellule.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: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and contact details; sameAs (social profiles) and description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,918 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page hidden from search
https://www.bleulibellule.com/selections/produits/noel/calendriers-de-lavent is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
3 pages without a meta description
https://www.bleulibellule.com/programme-de-fidelite, https://www.bleulibellule.com/programme-de-fidelite-vip and https://www.bleulibellule.com/commande have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages without an H1
https://www.bleulibellule.com/programme-de-fidelite and https://www.bleulibellule.com/programme-de-fidelite-vip have no <h1> headline, so visitors and search engines get no clear main topic.
4 pages slow to respond
https://www.bleulibellule.com/produit-cheveux, https://www.bleulibellule.com/produit-cheveux/shampoing-soin-coiffant/shampoing, https://www.bleulibellule.com/produit-cheveux/shampoing-soin-coiffant/apres-shampoing and https://www.bleulibellule.com/produit-cheveux/shampoing-soin-coiffant/coffret-cheveux took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 156 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 14 pages that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=25011779&tm=gtm002&Ver=2&mid=5aa4704e-4897-4486-b6c4-c26fa22ecb3c&bo=1&sid=07cde6b0d20011f18b79d7692abfd188&vid=07ce1e00d20011f19bbfa78814dc4233&vids=1&msclkid=N&pi=91.
111 small tap targets
111 of 210 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “BV is not defined”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
Missing source maps
Large scripts ship without source maps.
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 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.
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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,728 words of copy
The homepage carries about 1,728 words of visible text.
5 checks passed
5 short forms
5 short forms (2 fields at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 149 testimonial or review blocks and a star rating.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
9 trackers load before any consent
9Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and LinkedIn Insight and 4 mores (measured from a US location before any click). A consent tool (Didomi) is installed; check it blocks these until visitors agree where the law requires it.
28 cookies set on arrival
28Opening the homepage sets 28 cookies (measured from a US location before any click).
32 other companies contacted
Loading the homepage contacts 32 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Didomi
A consent management tool (Didomi) 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 bleulibellule.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Company
- Headquarters
- Gallargues-le-Montueux
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 39 issues on bleulibellule.com, including 15 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.