m-net.de website review

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

About 144 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.4 s faster on a phone.

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

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

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

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

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

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

5 third-party services load with your homepage (TagCommander, FullStory and Trustcommander and others), adding 351 KiB and 461 ms of main-thread time.

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

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

53 KiB could be saved by minifying JavaScript.

Polyfills for old browsers add 11 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.

Your largest element takes 6.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Eine Frau liegt auf dem Boden und schaut in ihren Laptop”.

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

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

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

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

6 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 137 ms to 164 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 1.6 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 2.1 MB in 135 requests on a phone: scripts 1.0 MB (100), images 803 KiB (20) and stylesheets 166 KiB (3). Under 2 MB keeps phones on slow connections fast.

2 images are downloaded at several times the size a phone draws them, for example csm_m-net-frau-mit-notebook-auf-teppich_a5b79d37c9.webp at 2,017 px wide, shown at 390 px. Resized copies would save about 94 KiB.

1 image further down the page (32 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.61 g of CO₂e: 72.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

2 buttons have no accessible name, so screen readers announce just “button”.

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

10 tap targets are too small or too close together to hit reliably with a finger.

ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

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

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

Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

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.

ARIA role should be appropriate for the element: 35 elements on the page fail this check, rated minor by axe-core.

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

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

Elements marked as presentational should be consistently ignored: 3 elements on the page fail this check, rated minor by axe-core.

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

Elements with visible text labels do not have matching accessible names. (12 elements).

No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 208 pages on m-net.de and 35 external pages.

There is no https://www.m-net.de/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.m-net.de/privatkunden/tarife-und-angebote/internet-telefon/mkk, whose canonical is https://www.m-net.de/privatkunden/tarife-und-angebote/internet-telefon/regio. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.m-net.de/service/m-net-shopfinder, https://www.m-net.de/privatkunden/tarife-und-angebote and https://www.m-net.de/privatkunden/tarife-und-angebote/highspeed-internet-ohne-festnetz took over 3 s to send their HTML from our server.

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

1 image failed to load on a phone, for example https://analytics.aklamio.com/analytics.gif?environment=production&location=embed&integration_type=gif.

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

The page uses 2 deprecated browser APIs that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

Large scripts ship without source maps.

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

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

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