wonderskin.com website review

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

59 files are served with short cache lifetimes, so returning visitors download them again (1.0 MB).

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

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

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

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

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

12 images could be 373 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

Shopify costs a phone 119 ms of main-thread work and 369 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.

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

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

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

28 KiB JavaScript is shipped twice across bundles.

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

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

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

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

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

Real visitors wait 2.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors see the first content after 2.1 s (75th percentile). Good is under 1.8 s.

Real visitors wait 1.1 s for your server to start answering (75th percentile). Good is under 800 ms.

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

4 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 159 ms to 156 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 6.9 MB in 635 requests on a phone: scripts 2.7 MB (151), images 2.1 MB (86) and other files 1.5 MB (341). Under 2 MB keeps phones on slow connections fast.

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

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

2 tap targets are too small or too close together to hit reliably with a finger.

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

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

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

Headings should not be empty: 5 elements on the page fail this check, rated minor by axe-core.

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is only 10 characters: “WONDERSKIN”. Between 30 and 65 characters leaves room to say what you do and for whom.

The homepage links to 107 pages on wonderskin.com and 3 external pages.

https://wonderskin.com/collections/offers, https://wonderskin.com/collections/makeup, https://wonderskin.com/collections/bestsellers, https://wonderskin.com/collections/new-in, https://wonderskin.com/collections/lip and https://wonderskin.com/collections/eyes and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://wonderskin.com/collections/offers, https://wonderskin.com/collections/value-sets, https://wonderskin.com/pages/shop-the-look and https://wonderskin.com/pages/1440-eyeliner-lp have no <h1> headline, so visitors and search engines get no clear main topic.

https://wonderskin.com/collections/offers and https://wonderskin.com/collections/value-sets have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

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

6 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://wonderskin.com/cdn/shop/t/912/assets/side-cart.css?v=150140' because its MIME type…”.

Large scripts ship without source maps.

Requests the notification permission on page load.

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

The page uses urgency cues (a countdown or limited-time wording).

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