luxecosmetics.de website review

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

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

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

36 images could be 2.4 MB 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.

8 third-party services load with your homepage (Google Tag Manager, ZenDesk and Shopify and others), adding 6.2 MB and 1.1 s of main-thread time.

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

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

Shopify costs a phone 145 ms of main-thread work and 4.7 MB 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.

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

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

ZenDesk costs a phone 325 ms of main-thread work and 476 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.

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

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

4 KiB could be saved by minifying CSS.

2 KiB could be saved by minifying JavaScript.

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

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

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

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

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

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

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

Your homepage downloads 9.0 MB in 233 requests on a phone: media 3.3 MB (6), images 2.9 MB (54) and scripts 2.2 MB (110). Under 2 MB keeps phones on slow connections fast.

17 images are downloaded at several times the size a phone draws them, for example 1_optimized_8ce946ac-e79f-4b18-8fff-d291dd63fe6b.png at 1,024 px wide, shown at 310 px. Resized copies would save about 505 KiB.

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

2 images (73 KiB) 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.

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

Certain ARIA roles must be contained by particular parents: 4 elements on the page fail this check, rated critical by axe-core.

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

Links must have discernible text: 5 elements on the page fail this check, rated serious by axe-core.

Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.

1 tap target is too small or too close together to hit reliably with a finger.

41 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.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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).

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 22 characters: “Luxe Cosmetics Germany”. Between 30 and 65 characters leaves room to say what you do and for whom.

Open Graph is missing og:description, so shared links fall back to guesses.

The homepage links to 76 pages on luxecosmetics.de and 4 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://luxecosmetics.de/products/luxe-wimpernshampoo is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://luxecosmetics.de/collections/wimpernlifting-produkte, https://luxecosmetics.de/products/luxe-wimpern-und-augenbrauen-serum, https://luxecosmetics.de/collections/luxe-augenbrauen-produkte and https://luxecosmetics.de/collections/luxe-wimpernlifting-zubehor have no meta description, so Google writes the search snippet from whatever text it finds.

https://luxecosmetics.de/collections/pfingst-sale, https://luxecosmetics.de/collections/wimpernlifting-produkte, https://luxecosmetics.de/collections/luxe-augenbrauen-produkte and https://luxecosmetics.de/collections/luxe-wimpernlifting-zubehor have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

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

3 errors were logged to the browser console while the page loaded, for example “Invalid left-hand side in assignment”.

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

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 testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

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