gladskin.eu website review

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

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

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

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

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

8 third-party services load with your homepage (Klaviyo, rebuyengine.com and Google Tag Manager and others), adding 2.0 MB and 672 ms of main-thread time.

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

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

Klaviyo costs a phone 182 ms of main-thread work and 338 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.

rebuyengine.com costs a phone 138 ms of main-thread work and 696 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 80 ms of main-thread work and 342 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.

3 images could be 59 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.

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

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

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.

Your largest element takes 41.2 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 45.4 s. Good is under 3.8 s.

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

The first text or image appears after 3.3 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 155 ms to 175 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.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 11.2 MB in 576 requests on a phone: fonts 5.0 MB (15), other files 2.3 MB (303) and scripts 1.9 MB (187). Under 2 MB keeps phones on slow connections fast.

55b6a202-39fe-48ee-b080-4a817bd3eaa0.png weighs 957 KiB. On a phone connection a single image that size takes seconds.

1 image (957 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.

1 image further down the page (41 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

11 elements use ARIA attributes their role does not allow, which confuses screen readers.

Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

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

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

The homepage links to 122 pages on gladskin.eu and 8 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://gladskin.eu/collections/all, https://gladskin.eu/collections/alle-producten, https://gladskin.eu/collections/shop-op-producttype, https://gladskin.eu/collections/biome-care and https://gladskin.eu/collections/soft-touch-essentials have no meta description, so Google writes the search snippet from whatever text it finds.

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

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

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

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