mephistousa.com website review

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

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

Your mobile performance score is 37. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

5 images could be 1.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

8 third-party services load with your homepage (Google Tag Manager, Facebook and TikTok and others), adding 2.3 MB and 738 ms of main-thread time.

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

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

Attentive costs a phone 102 ms of main-thread work and 1.3 MB 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.

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

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

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

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

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.

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.

Real visitors wait 4.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

Your largest element takes 8.3 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 16.2 s. Good is under 3.8 s.

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

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

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

Real visitors wait 961 ms for your server to start answering (75th percentile). Good is under 800 ms.

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

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

Your homepage downloads 4.1 MB in 176 requests on a phone: images 2.0 MB (37), scripts 1.4 MB (66) and fonts 401 KiB (12). Under 2 MB keeps phones on slow connections fast.

soho-hero-mobile-green-1200x1080.png 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 1.15 g of CO₂e: 138.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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.

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

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

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

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

Your title is only 23 characters: “Mephisto | Mephisto USA”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 16 <h1> headlines (“”, “Unparalleled walking comfort” and “Match”). One clear main headline is easier for people and search engines.

2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 223 pages on mephistousa.com and 2 external pages.

https://mephistousa.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://mephistousa.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://mephistousa.com/customer_authentication/redirect and https://mephistousa.com/policies/shipping-policy have no meta description, so Google writes the search snippet from whatever text it finds.

https://mephistousa.com/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.

https://mephistousa.com/pages/hsa-fsa-eligible-shoes took over 3 s to send its HTML from our server.

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

1 error was logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'addEventListener')”.

Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

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

The homepage shows no opening hours. If customers visit or call, show when.

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

The page uses urgency cues (a countdown or limited-time wording).

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