weareneen.com website review

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

8 images could be 451 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.9 s faster on a phone.

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

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

8 third-party services load with your homepage (Google CDN, Klaviyo and rechargecdn.com and others), adding 1.8 MB and 989 ms of main-thread time.

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

Google CDN costs a phone 606 ms of main-thread work and 1.1 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 45 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.

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

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

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

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

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

3 KiB could be saved by minifying CSS.

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

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

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

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

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

Your homepage downloads 13.0 MB in 293 requests on a phone: media 8.5 MB (4), scripts 1.9 MB (89) and images 1.1 MB (52). Under 2 MB keeps phones on slow connections fast.

neen-pretty-extra-mascara-main-1.webp weighs 540 KiB. On a phone connection a single image that size takes seconds.

7 images (1.1 MB) 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.

2 images are downloaded at several times the size a phone draws them, for example Sprinkle_6d590bb8-5850-41f4-8e41-73b1ef4f2bf9.webp at 1,080 px wide, shown at 78 px. Resized copies would save about 423 KiB.

3 images further down the page (477 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

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

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

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

Headings skip levels (h3 → h5), which makes the page harder to scan with a screen reader.

Your meta description is 177 characters; Google truncates after about 160, so the end of your pitch is cut.

The homepage links to 76 pages on weareneen.com and 15 external pages.

https://weareneen.com/collections/lip, https://weareneen.com/collections/cheeks, https://weareneen.com/collections/vegan-brushes, https://weareneen.com/collections/sets, https://weareneen.com/collections/all and https://weareneen.com/blogs/tutorials have no meta description, so Google writes the search snippet from whatever text it finds.

https://weareneen.com/collections/eyes, https://weareneen.com/collections/lip, https://weareneen.com/collections/cheeks, https://weareneen.com/collections/vegan-brushes, https://weareneen.com/collections/sets and https://weareneen.com/collections/all have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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