Website review, no card needed
bananabeauty.fr website review
Visit site (opens in a new tab)Reviewed 16 November 202635 issues · 83 checks
This review found 35 issues worth fixing on bananabeauty.fr, 9 of them high impact, across 83 checks. The most urgent: page weight: 4.7 MB in 262 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
84B- #22,537 of 126,458 reviewed websitesbeats 77%
- #14,358 of 70,479 online storesbeats 74%
- #13,916 of 63,977 Shopify storesbeats 72%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 990 ms |
| Jun 6, 2026 | 974 ms |
| Jun 13, 2026 | 927 ms |
| Jun 20, 2026 | 878 ms |
| Jun 27, 2026 | 871 ms |
| Jul 4, 2026 | 869 ms |
| Jul 11, 2026 | 887 ms |
| Jul 18, 2026 | 935 ms |
| Jul 25, 2026 | 902 ms |
| Aug 1, 2026 | 921 ms |
| Aug 8, 2026 | 927 ms |
| Aug 15, 2026 | 923 ms |
| Aug 22, 2026 | 985 ms |
| Aug 29, 2026 | 1.0 s |
| Sep 5, 2026 | 1.0 s |
| Sep 12, 2026 | 1.0 s |
| Sep 19, 2026 | 1.0 s |
| Sep 26, 2026 | 963 ms |
| Oct 3, 2026 | 928 ms |
| Oct 10, 2026 | 899 ms |
| Oct 17, 2026 | 881 ms |
| Oct 24, 2026 | 869 ms |
| Oct 31, 2026 | 863 ms |
| Nov 7, 2026 | 826 ms |
| Nov 14, 2026 | 785 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 185 ms |
| Jun 6, 2026 | 186 ms |
| Jun 13, 2026 | 180 ms |
| Jun 20, 2026 | 173 ms |
| Jun 27, 2026 | 171 ms |
| Jul 4, 2026 | 172 ms |
| Jul 11, 2026 | 170 ms |
| Jul 18, 2026 | 170 ms |
| Jul 25, 2026 | 163 ms |
| Aug 1, 2026 | 160 ms |
| Aug 8, 2026 | 162 ms |
| Aug 15, 2026 | 168 ms |
| Aug 22, 2026 | 180 ms |
| Aug 29, 2026 | 191 ms |
| Sep 5, 2026 | 191 ms |
| Sep 12, 2026 | 178 ms |
| Sep 19, 2026 | 167 ms |
| Sep 26, 2026 | 152 ms |
| Oct 3, 2026 | 148 ms |
| Oct 10, 2026 | 139 ms |
| Oct 17, 2026 | 138 ms |
| Oct 24, 2026 | 146 ms |
| Oct 31, 2026 | 148 ms |
| Nov 7, 2026 | 145 ms |
| Nov 14, 2026 | 138 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.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Mobile performance score: 61
61/100Your mobile performance score is 61. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
956 KiB5 images could be 956 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Reduce unused JavaScript
590 ms · 129 KiBAbout 129 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 590 ms faster on a phone.
Use efficient cache lifetimes
450 ms · 49 KiB12 files are served with short cache lifetimes, so returning visitors download them again (49 KiB).
Render-blocking requests
300 ms15 files block the first paint until they finish downloading. Deferring or inlining them could save about 300 ms.
Main-thread work: 2.9 s
A phone's processor spends 2.9 s on main-thread work while loading, 1.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
2,547 HTML elements
The page has 2,547 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Shopify adds 188 ms
188 msShopify costs a phone 188 ms of main-thread work and 480 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 (Shopify, Clarity and nfcube.com and others), adding 647 KiB and 326 ms of main-thread time.
Reduce unused CSS
150 ms · 38 KiBAbout 38 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 136 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.
Duplicated JavaScript
5 KiB5 KiB JavaScript is shipped twice across bundles.
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: 13 ms
13 msYour server sent the HTML in 13 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 19.7 s
19.7 sYour largest element takes 19.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “three models wearing banana beauty products”.
Time to Interactive: 20.2 s
20.2 sThe page becomes fully interactive after 20.2 s. Good is under 3.8 s.
Speed Index: 9.5 s
9.5 sVisually, the page fills in at 9.5 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.8 s
2.8 sThe first text or image appears after 2.8 s on a phone. Good is under 1.8 s.
2 images without width and height
2 images have no width and height attributes, so the layout jumps as each one loads.
10 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.1 s
1.1 sReal visitors wait 1.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 153 ms
153 msReal visitors wait 153 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 0.9 s
0.9 sReal visitors see the first content after 0.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 343 ms
343 msReal visitors wait 343 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 24% faster for real visitors
-24%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 185 ms to 138 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 18% faster for real visitors
-18%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.0 s to 0.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 123 ms
123 msScripts block the page for only 123 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 4.7 MB in 262 requests
4.7 MBYour homepage downloads 4.7 MB in 262 requests on a phone: images 3.0 MB (48), other files 869 KiB (111) and scripts 593 KiB (68). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
Shop_The_Look_02.png weighs 648 KiB. On a phone connection a single image that size takes seconds.
3 images far larger than shown
713 KiB3 images are downloaded at several times the size a phone draws them, for example Shop_The_Look_02.png at 3,405 px wide, shown at 390 px. Resized copies would save about 713 KiB.
8 images below the first screen load straight away
8 images further down the page (1.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
2 images in older formats
2 images (139 KiB) are 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 1.3 g of CO₂ per visit
1.32 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.32 g of CO₂e: 158.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
11 buttons without a name
11 buttons have no accessible name, so screen readers announce just “button”.
7 text elements with low contrast
7 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
2 tap targets too small
2 tap targets are too small or too close together to hit reliably with a finger.
8 links without text
8 visible links have no text or label, so screen readers cannot say where they go.
ARIA role should be appropriate for the element (11 elements)
ARIA role should be appropriate for the element: 11 elements on the page fail this check, rated minor by axe-core.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 38 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 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 6 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 (76 characters)
Your title is 76 characters, so Google will cut it off around 60: “Banana Beauty | Maquillage 100% Vegan et Cruelty Free – Banana Beauty France”.
3 H1 headlines
There are 3 <h1> headlines (“”, “Bestsellers” and “NOUVEAUTÉS”). One clear main headline is easier for people and search engines.
3 links crawlers can't follow
3 links have no real href, so search engines can't follow them.
176 internal links, 5 external
The homepage links to 176 pages on bananabeauty.fr and 5 external pages.
6 checks passed
Meta description: 152 characters
Your meta description is 152 characters: “Découvre notre maquillage pour les yeux et nos Rouges à Lèvres Liquides Vegan & Cruelty Free. Livraison gratuite à part…”.
Canonical URL set
The canonical URL is https://www.bananabeauty.fr/.
Structured data in place
Structured data found: Organization and WebSite.
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.bananabeauty.fr/sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.bananabeauty.fr/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 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 (976 words), so crawlers that don't run JavaScript still read it.
Other pages
3 pages without a meta description
https://www.bananabeauty.fr/policies/shipping-policy, https://www.bananabeauty.fr/collections/new-era-loading-sale and https://www.bananabeauty.fr/collections/new-in have no meta description, so Google writes the search snippet from whatever text it finds.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.bananabeauty.fr/collections/lips/rouge-%C3%A0-l%C3%A8vres-liquide, whose canonical is https://www.bananabeauty.fr/collections/lips/rouge-%c3%a0-l%c3%a8vres-liquide. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
4 pages without an H1
https://www.bananabeauty.fr/collections/all, https://www.bananabeauty.fr/collections/new-era-loading-sale, https://www.bananabeauty.fr/collections/new-in and https://www.bananabeauty.fr/collections/lips/rouge-%C3%A0-l%C3%A8vres-liquide have 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 46 found) and read each the way a search engine does.
4 checks passed
Linked pages load
5 pages of 15 loaded without an error (the rest turned automated requests away).
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 5 pages that loaded have a <title>.
Best practices
27 small tap targets
27 of 76 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
2 distorted images
2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 32 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
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.
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 529 words of copy
The homepage carries about 529 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP NOW”.
2 calls to action
The homepage has 2 calls to action, for example “SHOP NOW” and “Contact”.
17 short forms
17 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Microsoft Clarity.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity and 1 more (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.
20 cookies set on arrival
20Opening the homepage sets 20 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.
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 bananabeauty.fr, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
Your storefront loads 6 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Microsoft Clarity · Judge Me Reviews · Pushowl · cloudfront.net · mulwi.com · nfcube.com
Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info
Upkeep, stack and company
Stack
- Framework
- Tailwind CSS
- E-commerce
- Shopify
- Analytics
- Microsoft Clarity
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 35 issues on bananabeauty.fr, including 13 speed issues, 3 SEO issues and 2 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.