leif-nelson.de website review

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

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

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

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

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

8 third-party services load with your homepage (Other Google APIs/SDKs, Shopify and useamp.com and others), adding 1.3 MB and 1.3 s of main-thread time.

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

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

Other Google APIs/SDKs costs a phone 820 ms of main-thread work and 124 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.

Shopify costs a phone 214 ms of main-thread work and 762 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 images could be 259 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

7 KiB could be saved by minifying JavaScript.

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.

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

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

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

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

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

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

Your homepage downloads 9.3 MB in 608 requests on a phone: images 6.3 MB (287), other files 1.5 MB (196) and scripts 1.2 MB (90). Under 2 MB keeps phones on slow connections fast.

ln-startseite-sportswear-20260920.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

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

ARIA commands must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

All page content should be contained by landmarks: 6 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.

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

1 visible link has no text or label, so screen readers cannot say where it goes.

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

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

The homepage links to 91 pages on leif-nelson.de and 2 external pages.

https://leif-nelson.de/en-int/collections/all has no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://leif-nelson.de/en-int/collections/herren-strickwaren-1/products/ln-4195, whose canonical is https://leif-nelson.de/en-int/products/ln-4195. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://leif-nelson.de/en-int/collections/herren-strickwaren-1/products/ln-4195, https://leif-nelson.de/en-int/collections/herren-strickwaren-1/products/ln-1670 and https://leif-nelson.de/en-int/collections/herren-strickwaren-1/products/ln-20227 have no <h1> headline, so visitors and search engines get no clear main topic.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Authorization will not be covered by the wildcard symbol (*) in CORS `Access-Control-Allow-Headers`…”).

2 errors were logged to the browser console while the page loaded, for example “Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'register')”.

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.

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

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