mysortimo.de website review

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

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

7 images could be 451 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.8 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.

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

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

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

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

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

3 third-party services load with your homepage (consentmanager.net, Hubspot and Adobe TypeKit), adding 196 KiB and 180 ms of main-thread time.

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

Your largest element takes 25.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Ladder handling made easy –the new Sortimo Rear ladder…”.

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

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

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

10 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-31, real Chrome visitors' tap response (inp) went from 94 ms to 98 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 5.9 MB in 72 requests on a phone: images 3.2 MB (38), scripts 1.8 MB (15) and fonts 528 KiB (5). Under 2 MB keeps phones on slow connections fast.

Vorschaubild-2023-02-FR-Sortimo-Effizienz-Video-FINAL.00-00- weighs 1.4 MB. On a phone connection a single image that size takes seconds.

5 images are downloaded at several times the size a phone draws them, for example Vorschaubild-2023-02-FR-Sortimo-Effizienz-Video-FINAL.00-00- at 3,840 px wide, shown at 370 px. Resized copies would save about 1.6 MB.

9 images (2.3 MB) 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.

6 images further down the page (1.9 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

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

15 text elements don'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: 3 elements on the page fail 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.

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

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

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

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

Your robots.txt disallows the whole site for every crawler, so search engines are told to stay out.

Structured data found (Organization and WebSite) but with 1 problem, for example “WebSite: missing name”.

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

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

1 link has no real href, so search engines can't follow it.

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

The homepage links to 576 pages on mysortimo.de and 27 external pages.

Your robots.txt shuts out Claude search (Claude-SearchBot), Claude (Claude-User) and Perplexity (Perplexity-User). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.

There is no https://www.mysortimo.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.

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

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

1 error was logged to the browser console while the page loaded, for example “Error: <svg> attribute height: Expected length, "87,95".”.

4 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

Large scripts ship without source maps.

Social proof on the homepage: 6 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

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

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