weider.de website review

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

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

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

8 third-party services load with your homepage (Shopify, TikTok and Klaviyo and others), adding 1.4 MB and 747 ms of main-thread time.

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

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

Shopify costs a phone 332 ms of main-thread work and 1,016 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 61 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.

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

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

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

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

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.

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

Your largest element takes 7.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “WEIDER Black Month W1”.

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

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

3 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 138 ms to 137 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.2 s to 1.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 5.3 MB in 266 requests on a phone: images 2.6 MB (73), scripts 1.5 MB (83) and other files 874 KiB (81). Under 2 MB keeps phones on slow connections fast.

39 images (3.8 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.

7 images further down the page (590 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

1 image is downloaded at several times the size a phone draws it, for example Logo_der_Globus_SB-Warenhaus_GmbH___Co.KG_-_Globus-Holding.p at 1,219 px wide, shown at 39 px. Resized copies would save about 92 KiB.

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

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

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

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

Elements with visible text labels do not have matching accessible names. (1 element).

There are 2 <h1> headlines (“Weider Germany” and “WEIDER Adventskalender 2026”). One clear main headline is easier for people and search engines.

The homepage links to 140 pages on weider.de and 13 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.

https://www.weider.de/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://www.weider.de/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.weider.de/customer_authentication/redirect and https://www.weider.de/policies/shipping-policy have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.weider.de/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.

https://www.weider.de/collections/sale took over 3 s to send its HTML from our server.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=343281052&tm=gtm002&Ver=2&mid=9af3cc6d-4d68-4ac7-b68e-5c8bfb13b514&bo=1&sid=c729f830d8b911f1af6d2398d59c9028&vid=c72a2a80d8b911f190aa6915344dbf68&vids=1&msclkid=N&pi=9.

15 of 66 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 “Unexpected token '<'”.

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

Large scripts ship without source maps.

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

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