stilacosmetics.com website review

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

Signyfyd costs a phone 1.1 s of main-thread work and 280 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

Your mobile performance score is 45. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

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

8 third-party services load with your homepage (Signyfyd, Clarity and Google Tag Manager and others), adding 1.7 MB and 2.0 s of main-thread time.

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

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

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

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

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

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

Clarity costs a phone 275 ms of main-thread work and 29 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.

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

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

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

30 KiB could be saved by minifying JavaScript.

11 KiB JavaScript is shipped twice across bundles.

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 13.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Stila Cosmetics”.

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

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

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

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

Real visitors wait 229 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

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

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

Your homepage downloads 10.0 MB in 519 requests on a phone: images 5.2 MB (93), scripts 2.4 MB (134) and other files 1.8 MB (243). Under 2 MB keeps phones on slow connections fast.

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

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

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

Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

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

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

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

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

Your <h1> is empty.

The homepage links to 179 pages on stilacosmetics.com and 1 external page.

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.stilacosmetics.com/collections/meadow-dream-collection, https://www.stilacosmetics.com/collections/pretty-striking-collection, https://www.stilacosmetics.com/collections/rebel-beauty-collection and https://www.stilacosmetics.com/collections/newest-arrivals have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.stilacosmetics.com/products/sunrise-eyes-liqua-play-eye-shadow-collection and https://www.stilacosmetics.com/products/all-fire use the same meta description. A description written for each page earns more clicks.

https://www.stilacosmetics.com/pages/the-hunger-games-sunrise-on-the-reaping, https://www.stilacosmetics.com/products/sunrise-eyes-liqua-play-eye-shadow-collection, https://www.stilacosmetics.com/products/all-fire, https://www.stilacosmetics.com/collections/meadow-dream-collection, https://www.stilacosmetics.com/collections/pretty-striking-collection and https://www.stilacosmetics.com/collections/rebel-beauty-collection and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.stilacosmetics.com/collections/best-sellers took over 3 s to send its HTML from our server.

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

3 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

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

4 errors were logged to the browser console while the page loaded, for example “Shopify's Google Analytics stub called with: [array Array] See https://help.shopify.com/manual/promoting-marketing/pixe…”.

Chrome logged issues while loading the page (“Cookie”).

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage has only about 248 words of visible text; thin pages give Google and first-time buyers little to go on.

There is no form on the homepage, so every lead has to click through to another page first.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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