Website review, no card needed
bizou.com website review
Visit site (opens in a new tab)Reviewed 9 November 202623 issues · 78 checks
This review found 23 issues worth fixing on bizou.com, 6 of them high impact, across 78 checks. The most urgent: 5 tap targets too small. 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
86B- #12,041 of 124,162 reviewed websitesbeats 87%
- #7,292 of 69,801 online storesbeats 85%
- #7,062 of 63,483 Shopify storesbeats 84%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.0 s |
| May 23, 2026 | 1.0 s |
| May 30, 2026 | 982 ms |
| Jun 6, 2026 | 958 ms |
| Jun 13, 2026 | 938 ms |
| Jun 20, 2026 | 867 ms |
| Jun 27, 2026 | 861 ms |
| Jul 4, 2026 | 824 ms |
| Jul 11, 2026 | 831 ms |
| Jul 18, 2026 | 848 ms |
| Jul 25, 2026 | 833 ms |
| Aug 1, 2026 | 836 ms |
| Aug 8, 2026 | 816 ms |
| Aug 15, 2026 | 818 ms |
| Aug 22, 2026 | 826 ms |
| Aug 29, 2026 | 856 ms |
| Sep 5, 2026 | 876 ms |
| Sep 12, 2026 | 886 ms |
| Sep 19, 2026 | 884 ms |
| Sep 26, 2026 | 837 ms |
| Oct 3, 2026 | 822 ms |
| Oct 10, 2026 | 815 ms |
| Oct 17, 2026 | 848 ms |
| Oct 24, 2026 | 881 ms |
| Oct 31, 2026 | 907 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 89 ms |
| May 23, 2026 | 91 ms |
| May 30, 2026 | 90 ms |
| Jun 6, 2026 | 92 ms |
| Jun 13, 2026 | 95 ms |
| Jun 20, 2026 | 95 ms |
| Jun 27, 2026 | 98 ms |
| Jul 4, 2026 | 98 ms |
| Jul 11, 2026 | 102 ms |
| Jul 18, 2026 | 103 ms |
| Jul 25, 2026 | 105 ms |
| Aug 1, 2026 | 110 ms |
| Aug 8, 2026 | 108 ms |
| Aug 15, 2026 | 110 ms |
| Aug 22, 2026 | 106 ms |
| Aug 29, 2026 | 105 ms |
| Sep 5, 2026 | 104 ms |
| Sep 12, 2026 | 103 ms |
| Sep 19, 2026 | 104 ms |
| Sep 26, 2026 | 104 ms |
| Oct 3, 2026 | 103 ms |
| Oct 10, 2026 | 105 ms |
| Oct 17, 2026 | 107 ms |
| Oct 24, 2026 | 105 ms |
| Oct 31, 2026 | 110 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
Speed
Mobile performance score: 66
66/100Your mobile performance score is 66. Pages that score under 90 lose visitors before the first paint.
Main-thread work: 2.9 s
A phone's processor spends 2.9 s on main-thread work while loading, 367 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
1,959 HTML elements
The page has 1,959 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Use efficient cache lifetimes
250 ms · 39 KiB8 files are served with short cache lifetimes, so returning visitors download them again (39 KiB).
Improve image delivery
150 ms · 133 KiB3 images could be 133 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
Reduce unused JavaScript
150 ms · 24 KiBAbout 24 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
Reduce unused CSS
150 ms · 19 KiBAbout 19 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 third-party services on the page
3 third-party services load with your homepage (Snapchat, Shopify and shop.app), adding 335 KiB and 126 ms of main-thread time.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 58 ms. During a long task the page ignores taps.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
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: 6 ms
6 msYour server sent the HTML in 6 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 10.8 s
10.8 sYour largest element takes 10.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 10.9 s
10.9 sThe page becomes fully interactive after 10.9 s. Good is under 3.8 s.
Speed Index: 6.0 s
6.0 sVisually, the page fills in at 6.0 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.7 s
2.7 sThe first text or image appears after 2.7 s on a phone. Good is under 1.8 s.
Tap response (INP) got 19% slower for real visitors
+19%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 89 ms to 110 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
9 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: 2.0 s
2.0 sReal visitors wait 2.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 112 ms
112 msReal visitors wait 112 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: 1.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 509 ms
509 msReal visitors wait 509 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 13% faster for real visitors
-13%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.0 s to 0.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 9 ms
9 msScripts block the page for only 9 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 2.0 MB in 180 requests
2.0 MBYour homepage downloads 2.0 MB in 180 requests on a phone: other files 749 KiB (94), images 729 KiB (21) and scripts 346 KiB (55). Under 2 MB keeps phones on slow connections fast.
About 0.6 g of CO₂ per visit
0.57 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.57 g of CO₂e: 68.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 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.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
5 tap targets too small
5 tap targets are too small or too close together to hit reliably with a finger.
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.
Alternative text of images should not be repeated as text (1 element)
Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h6), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
2 checks passed
Every image has alt text
All 80 images in the HTML carry an alt attribute.
51 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: 51 passed and 4 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
148 internal links, 5 external
The homepage links to 148 pages on bizou.com and 5 external pages.
8 checks passed
Meta description: 157 characters
Your meta description is 157 characters: “Découvrez nos bijoux abordables et tendance : bagues, colliers, bracelets, boucles d'oreilles et accessoires. Livraison…”.
One H1 headline
Your main headline reads: “Bizou”.
Title: 53 characters
Your title is a healthy 53 characters: “Bizou : Bijoux tendance pour femmes | Québec & Canada”.
Canonical URL set
The canonical URL is https://bizou.com/.
Structured data in place
Structured data found: BreadcrumbList, 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://bizou.com/sitemap.xml.
AI search readiness
Organization data is thin (2 of 6 facts)
Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
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.
Text is in the HTML
Your server sends the page's text in the HTML (1,025 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://bizou.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
15 pages without a meta description
https://bizou.com/collections/la-nouveaute, https://bizou.com/collections/boucles-doreilles, https://bizou.com/collections/colliers, https://bizou.com/collections/bracelets, https://bizou.com/collections/chaines-de-cheville and https://bizou.com/collections/bague and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
14 pages without an H1
https://bizou.com/collections/la-nouveaute, https://bizou.com/collections/boucles-doreilles, https://bizou.com/collections/colliers, https://bizou.com/collections/bracelets, https://bizou.com/collections/bague and https://bizou.com/collections/mini and 8 others 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 64 found) and read each the way a search engine does.
5 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.
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
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 “Failed to load resource: the server responded with a status of 404 ()”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
63 of 73 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 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.
Thin social proof
Social proof on the homepage: 8 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 731 words of copy
The homepage carries about 731 words of visible text.
1 checks passed
48 short forms
48 short forms (1 field at most) are right on the homepage.
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 Snap Pixel 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.
16 cookies set on arrival
16Opening the homepage sets 16 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.
20 other companies contacted
Loading the homepage contacts 20 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 bizou.com, 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 1 app. It is code from another company running for your shoppers.
Apps your storefront loads
snapchat.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
- E-commerce
- Shopify
- Hosting
- Cloudflare
Company
- Employees
- 750
- Founded
- 1982
- Headquarters
- Sainte-Marie
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 23 issues on bizou.com, including 7 speed issues, 1 SEO issue and 5 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.