maidesite.fr website review

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

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

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

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

2 images could be 532 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

xcottons.com costs a phone 99 ms of main-thread work and 363 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 load with your homepage (xcottons.com, loox.io and omnisnippet1.com and others), adding 787 KiB and 327 ms of main-thread time.

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

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

About 32 KiB of CSS is downloaded but never applied on this page.

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.

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.

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

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

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

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

For real visitors the layout shifts by 0.19 (75th percentile). Good is under 0.1.

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

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

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

2 images are downloaded at several times the size a phone draws them, for example 2_-_0731_-_2_c47f70e5-1983-410e-a4ae-1f532669a7b0.jpg at 2,560 px wide, shown at 390 px. Resized copies would save about 510 KiB.

Your homepage downloads 3.0 MB in 179 requests on a phone: images 1.2 MB (18), other files 780 KiB (69) and scripts 764 KiB (53). Under 2 MB keeps phones on slow connections fast.

3 images further down the page (670 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 0.86 g of CO₂e: 103.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

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

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

All page content should be contained by landmarks: 16 elements on the page fail this check, rated moderate by axe-core.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

5 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 → h4, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.

Elements with visible text labels do not have matching accessible names. (1 element).

There is no <h1>, so neither visitors nor Google get a clear main headline.

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

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

2 links have no real href, so search engines can't follow them.

The homepage links to 79 pages on maidesite.fr and 6 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.

https://www.maidesite.fr/collections/all, https://www.maidesite.fr/pages/black-friday-2025, https://www.maidesite.fr/pages/2026-soldes-du-nouvel-an, https://www.maidesite.fr/pages/group-buy, https://www.maidesite.fr/products/bureau-debout-electrique-maidesite-t2-a-double-moteur and https://www.maidesite.fr/pages/2026-promotion-de-printemps and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.maidesite.fr/collections/all, https://www.maidesite.fr/collections/bureau-assis-debout-electrique, https://www.maidesite.fr/pages/group-buy, https://www.maidesite.fr/products/bureau-debout-electrique-maidesite-t2-a-double-moteur, https://www.maidesite.fr/products/maidesite-t2-pro-plus-cadre-de-table-reglable-electriquement-en-hauteur and https://www.maidesite.fr/products/maidesite-t4-pro-plus-bureau-assis-debout-electrique and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

6 of 24 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 “Uncaught Error: Goaffpro is already loaded. This message prevents duplicate loading of the script. Kindly ignore.”.

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 testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (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 18 cookies, 1 of them by other companies (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 27 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.