sudexpress.fr website review

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Optanon and Clarity and others), adding 942 KiB and 716 ms of main-thread time.

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

About 436 KiB of JavaScript is downloaded but never used on this page.

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

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

5 images could be 69 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.

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

About 40 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.

19 KiB could be saved by minifying JavaScript.

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

Polyfills for old browsers add 9 KiB JavaScript that modern phones do not need.

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 7.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Sud Express”.

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

Real visitors wait 205 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

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

Real visitors see the first content after 2.1 s (75th percentile). Good is under 1.8 s.

Scripts block taps and scrolling for 525 ms in total while the page loads. Good is under 200 ms.

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

Your homepage downloads 3.3 MB in 229 requests on a phone: scripts 1.3 MB (68), images 896 KiB (18) and other files 823 KiB (121). Under 2 MB keeps phones on slow connections fast.

1 image further down the page (27 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

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

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

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

Structured data found ((untyped) and WebSite) but with 8 problems, for example “untyped block: missing @context (expected "https://schema.org")”.

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

The homepage links to 131 pages on sudexpress.fr and 48 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.sudexpress.fr/pages/faq, https://www.sudexpress.fr/collections/jeans, https://www.sudexpress.fr/collections/robes-et-jupes, https://www.sudexpress.fr/collections/vestes-manteaux, https://www.sudexpress.fr/collections/le-vestiaire-sud-express and https://www.sudexpress.fr/collections/velours and 2 others use the same meta description. A description written for each page earns more clicks.

https://www.sudexpress.fr/pages/retours-boutiques and https://www.sudexpress.fr/pages/faq have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

3 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://www.sudexpress.fr/cdn/shop/t/66/assets/component-list-menu.css?v=17195' because it…”.

Large scripts ship without source maps.

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

Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager and Microsoft Clarity (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

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

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