fussmatten.de website review

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

8 third-party services load with your homepage (Google Tag Manager, smarketer.de and JSDelivr CDN and others), adding 1.2 MB and 1.1 s of main-thread time.

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

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

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

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

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

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

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

Shopify costs a phone 90 ms of main-thread work and 303 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.

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

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

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

2 KiB could be saved by minifying JavaScript.

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.

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

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

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

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

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

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

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

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

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

Your homepage downloads 4.0 MB in 253 requests on a phone: images 1.5 MB (71), scripts 1.3 MB (53) and other files 927 KiB (114). Under 2 MB keeps phones on slow connections fast.

1 image (216 KiB) is 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.13 g of CO₂e: 135.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

12 images have no alt text, which hurts accessibility and image search.

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

Headings skip levels (h1 → h3), 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 only 22 characters: “Fussmatten Online Shop”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 84 pages on fussmatten.de and 3 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), 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://fussmatten.de/pages/kontakt and https://fussmatten.de/pages/b2b have no meta description, so Google writes the search snippet from whatever text it finds.

https://fussmatten.de/pages/b2b, https://fussmatten.de/collections/schmutzfangmatten, https://fussmatten.de/collections/fussabtreter, https://fussmatten.de/products/fussmatte-kokos-eingansmatten-individuell-angefertigt-bis-30-mm-hohe, https://fussmatten.de/collections/ringgummimatten and https://fussmatten.de/products/schmutzfangmatte-splash-auf-mass and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://fussmatten.de/pages/kontakt, https://fussmatten.de/products/schmutzfangmatte-splash-auf-mass and https://fussmatten.de/products/schmutzfangmatte-use-wash-in-vielen-farben-auf-wunschmass have 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.

https://fussmatten.de/collections/sport-freizeit, https://fussmatten.de/products/schmutzfangmatte-splash-auf-mass, https://fussmatten.de/products/schmutzfangmatte-use-wash-in-vielen-farben-auf-wunschmass, https://fussmatten.de/products/fussmatte-mit-innovatives-3d-netz-imperial-1000 and https://fussmatten.de/products/fussmatte-rhine-unicolor-10-farben-6-grossen took over 3 s to send their HTML from our server.

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

1 image failed to load on a phone, for example https://fussmatten.de/cdn/shop/files/icon-modal-pdp.jpg?v=3573.

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

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

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.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (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 15 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.