stila.net website review

Signyfyd costs a phone 1.2 s of main-thread work and 281 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.

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

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

The page has 7,398 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, Google Tag Manager and Clarity and others), adding 1.6 MB and 2.1 s of main-thread time.

About 833 KiB of JavaScript is downloaded but never used on this page.

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

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

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

Google Tag Manager costs a phone 236 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.

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

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

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

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.

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 8.9 MB in 420 requests on a phone: images 4.6 MB (91), scripts 2.3 MB (128) and other files 1.4 MB (153). 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.53 g of CO₂e: 303.5 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.

Your canonical URL points to stilacosmetics.com, not stila.net, so Google may credit that host instead.

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

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

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

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

1 image failed to load on a phone, for example https://i.liadm.com/s/85221?&aid=252f3222-0674-4909-be7d-e90279a1d805&ref=A9EEEE18&_=0.17770122703274815.

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

6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_TUNNEL_CONNECTION_FAILED”.

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 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 22 cookies, 1 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 65 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.