mephisto.com website review

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Unpkg and Google/Doubleclick Ads and others), adding 681 KiB and 283 ms of main-thread time.

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

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

2 images could be 34 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 100 ms faster on a phone.

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

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

3 KiB could be saved by minifying CSS.

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

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

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

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

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

Your homepage downloads 11.1 MB in 140 requests on a phone: media 9.7 MB (1), scripts 693 KiB (50) and images 382 KiB (33). Under 2 MB keeps phones on slow connections fast.

Hero_Banner_Mobile_-_CITY_SNEAKERS_ed68727a-e57a-4f10-bd35-4 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).

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

1 image has no alt text, which hurts accessibility and image search.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

Headings skip levels (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).

Your title is 97 characters, so Google will cut it off around 60: “MEPHISTO Boutique en Ligne Officielle France - Chaussures directement du fabricant | Meph…”.

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

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

Your <h1> is empty.

The homepage links to 185 pages on mephisto.com and 9 external pages.

https://www.mephisto.com/fr-fr/pages/centre-d-aide, https://www.mephisto.com/fr-fr/collections/nouveautes-femme, https://www.mephisto.com/fr-fr/collections/femme, https://www.mephisto.com/fr-fr/collections/sneaker-femme, https://www.mephisto.com/fr-fr/collections/chaussures-femme and https://www.mephisto.com/fr-fr/collections/mocassins-femme and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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

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