maisonbaika.com website review

44 images could be 3.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.6 s faster on a phone.

Your mobile performance score is 67. Pages that score under 90 lose visitors before the first paint.

11 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.

8 third-party services load with your homepage (Shopify, pop-convert.com and Google CDN and others), adding 1.1 MB and 326 ms of main-thread time.

A phone's processor spends 3.9 s on main-thread work while loading, 867 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

The page has 2,847 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

Shopify costs a phone 200 ms of main-thread work and 828 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.

About 161 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 260 ms faster on a phone.

About 39 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 110 ms faster on a phone.

19 KiB could be saved by minifying JavaScript.

7 files are served with short cache lifetimes, so returning visitors download them again (126 KiB).

2 long tasks block the main thread while loading, the longest for 87 ms. During a long task the page ignores taps.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

The page becomes fully interactive after 26.5 s. Good is under 3.8 s.

Your largest element takes 8.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

Visually, the page fills in at 7.9 s (Speed Index). Good is under 3.4 s.

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 7.5 MB in 430 requests on a phone: images 5.1 MB (77), other files 1.2 MB (165) and scripts 842 KiB (133). Under 2 MB keeps phones on slow connections fast.

7 images are downloaded at several times the size a phone draws them, for example 50.webp at 1,026 px wide, shown at 143 px. Resized copies would save about 879 KiB.

Header-pendentif-lovy-mobile_1.webp 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).

9 images (1,024 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.

By the Sustainable Web Design model, a visit to your homepage emits about 2.12 g of CO₂e: 254.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 button has no accessible name, so screen readers announce just “button”.

29 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

All page content should be contained by landmarks: 3 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 on the page fails this check, rated moderate by axe-core.

6 visible links have no text or label, so screen readers cannot say where they go.

2 form fields have no label, so screen readers announce an empty box and autofill guesses.

Headings skip levels (h2 → h5), which makes the page harder to scan with a screen reader.

Your title is 84 characters, so Google will cut it off around 60: “Maison Baïka | Bijoux, Colliers, Bagues, Boucles d'oreilles, Bracelets – MaisonBaika”.

Your meta description is 313 characters; Google truncates after about 160, so the end of your pitch is cut.

Your <h1> is empty.

The homepage links to 102 pages on maisonbaika.com and 15 external pages.

https://maisonbaika.com/products/bracelet-coeurs-dore-copie and https://maisonbaika.com/products/bracelet-coeur-plaque-or all use the title “Bracelet Coeurs - Doré - Maison Baïka – MaisonBaika”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://maisonbaika.com/collections/all, https://maisonbaika.com/pages/faq, https://maisonbaika.com/collections/nouveautes, https://maisonbaika.com/collections/accessoires, https://maisonbaika.com/collections/infinity and https://maisonbaika.com/collections/best-sellers use the same meta description. A description written for each page earns more clicks.

We fetched 15 pages linked from your homepage (of 48 found) and read each the way a search engine does.

15 of 66 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

Social proof on the homepage: 108 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 714 words of visible text.

Opening the homepage sets 4 cookies (measured from a US location before any click).

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.

Loading the homepage contacts 13 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.