mosmosh.de website review

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

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

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

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

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

1 image could be 56 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.

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

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

Cookie-Script.com costs a phone 219 ms of main-thread work and 395 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,582 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

8 third-party services load with your homepage (Cookie-Script.com, Klaviyo and JSDelivr CDN and others), adding 856 KiB and 348 ms of main-thread time.

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

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

3 KiB could be saved by minifying JavaScript.

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

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

3 KiB could be saved by minifying CSS.

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

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

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

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

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

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

Your homepage downloads 4.1 MB in 374 requests on a phone: other files 1.8 MB (268), scripts 1.5 MB (81) and images 531 KiB (7). Under 2 MB keeps phones on slow connections fast.

3 images (260 KiB) 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.

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

1 button has no accessible name, so screen readers announce just “button”.

1 dropdown has no label.

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

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

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.

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

There are 6 <h1> headlines (“LY26: Played Wth Grace”, “Neu in” and “MOS MOSH MEMBERS”). One clear main headline is easier for people and search engines.

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

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 377 pages on mosmosh.de and 9 external pages.

Your Organization JSON-LD is missing logo, description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

https://mosmosh.com/en-de/pages/home-men and https://mosmosh.com/en-de/pages/home-women have no meta description, so Google writes the search snippet from whatever text it finds.

https://mosmosh.com/en-de/pages/home-men, https://mosmosh.com/en-de/pages/about-heyanno, https://mosmosh.com/en-de/collections/heyanno-all-styles-for-women and https://mosmosh.com/en-de/collections/all-styles-for-men have no <h1> headline, so visitors and search engines get no clear main topic.

https://mosmosh.com/en-de/collections/all-styles-for-men has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

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

Large scripts ship without source maps.

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 phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage has only about 236 words of visible text; thin pages give Google and first-time buyers little to go on.

There is no form on the homepage, so every lead has to click through to another page first.

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