miliboo.com website review

78 files are served with short cache lifetimes, so returning visitors download them again (8.1 MB).

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

About 697 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.8 s faster on a phone.

7 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.3 s.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.3 s).

Your mobile performance score is 56 (desktop: 53). Pages that score under 90 lose visitors before the first paint.

8 third-party services load with your homepage (Google Tag Manager, Google CDN and Trust Pilot and others), adding 1.3 MB and 518 ms of main-thread time.

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

60 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 300 ms faster on a phone.

Google Tag Manager costs a phone 235 ms of main-thread work and 371 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.

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

Google CDN costs a phone 63 ms of main-thread work and 347 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.

Polyfills for old browsers add 32 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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

10 KiB could be saved by minifying JavaScript.

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

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

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

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

The first text or image appears after 2.8 s on a phone. Good is under 1.8 s.

The layout shifts by 0.135 while loading, so content jumps under the reader's thumb. Good is under 0.1.

20 images have no width and height attributes, so the layout jumps as each one loads.

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 145 ms to 144 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 9.2 MB in 136 requests on a phone: images 7.3 MB (53), scripts 1.4 MB (40) and fonts 330 KiB (5). Under 2 MB keeps phones on slow connections fast.

25 images (4.6 MB) 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.

5 images are downloaded at several times the size a phone draws them, for example tendance3.jpg at 700 px wide, shown at 230 px. Resized copies would save about 28 KiB.

2 images further down the page (278 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

12 images have no alt text, which hurts accessibility and image search.

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

14 elements hidden from screen readers can still receive keyboard focus.

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

Elements use prohibited ARIA attributes (1 element).

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

No XML sitemap at https://www.miliboo.com/sitemap/sitemap_index_fr.xml, so Google discovers your pages only by following links.

1 link has no real href, so search engines can't follow it.

Your <h1> is empty.

Open Graph is missing og:description, so shared links fall back to guesses.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 284 pages on miliboo.com and 21 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

There is no https://www.miliboo.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.

https://www.miliboo.com/milibootiks-connectees.html and https://www.miliboo.com/mon-panier.html are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://www.miliboo.com/mon-panier.html has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.miliboo.com/espace-pro.html and https://www.miliboo.com/contact.html use the same meta description. A description written for each page earns more clicks.

https://www.miliboo.com/espace-pro.html, https://www.miliboo.com/contact.html and https://www.miliboo.com/mon-panier.html have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.miliboo.com/milibootiks-connectees.html and https://www.miliboo.com/espace-pro.html took over 3 s to send their HTML from our server.

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

10 images failed to load on a phone, for example https://www.miliboo.com/.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

4 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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

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 398 words of visible text.

Before a visitor clicks anything, the page loads Google Tag Manager, Meta Pixel and Microsoft Ads (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.

Opening the homepage sets 3 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 15 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.