mum.de website review

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

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

14 images could be 441 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.3 s faster on a phone.

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

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

About 160 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 770 ms faster on a phone.

5 third-party services load with your homepage (Google CDN, Usercentrics CMP and Google Tag Manager and others), adding 1.2 MB and 507 ms of main-thread time.

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

Google CDN costs a phone 270 ms of main-thread work and 737 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 long tasks block the main thread while loading, the longest for 85 ms. During a long task the page ignores taps.

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

Desktop scores 93 but mobile only 49. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

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

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

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

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

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

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

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

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

Your homepage downloads 3.4 MB in 66 requests on a phone: scripts 1.2 MB (23), fonts 917 KiB (5) and images 752 KiB (23). Under 2 MB keeps phones on slow connections fast.

9 images (530 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 0.96 g of CO₂e: 115.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

All page content should be contained by landmarks: 5 elements on the page fail 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 should not be empty: 2 elements on the page fail this check, rated minor by axe-core.

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

Your title is 66 characters, so Google will cut it off around 60: “CAD/CAM/CAE-, PDM/PLM- und BIM-Lösungsanbieter Mensch und Maschine”.

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

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

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 120 pages on mum.de and 18 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.

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

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

1 image is served at too low a resolution for sharp phone screens.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

Social proof on the homepage: 1 customer or partner logo. Pairing it with named testimonials or customer logos makes it far more convincing.

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 215 words of visible text; thin pages give Google and first-time buyers little to go on.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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

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

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