vanitystock.com website review

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

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

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

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

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

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

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

5 third-party services load with your homepage (Shopify, Cloudflare and Trust Pilot and others), adding 635 KiB and 97 ms of main-thread time.

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

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

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

About 16 KiB of CSS is downloaded but never applied on this page.

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.

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

Your largest element takes 6.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Pelle spenta e secca dopo l’estate?”.

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

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

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

eff35f8e-7853-4268-a6b6-73dbd7b10ce0.png 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).

6 images (549 KiB) 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.

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

9 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

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

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

Elements with visible text labels do not have matching accessible names. (2 elements).

The robots meta tag says “noindex, follow, nocache”: Google is told not to list this page at all.

Google's crawler is blocked from indexing this page.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 459 pages on vanitystock.com and 2 external pages.

There is no https://vanitystock.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://vanitystock.com/en-de/contacts, https://vanitystock.com/en-de/b2b-contact, https://vanitystock.com/en-de/collections/discover-the-best-offers-on-vanity-stock, https://vanitystock.com/en-de/collections/current-promotion, https://vanitystock.com/en-de/collections/hair-care-on-promotion and https://vanitystock.com/en-de/collections/mens-care-offers and 9 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://vanitystock.com/en-de and https://vanitystock.com/en-de/collections/current-promotion all use the title “VanityStock - Beauty & Personal Care Products”. Search engines can't tell which page to show for a search, so each competes with the others.

https://vanitystock.com/en-de/collections/bundle-and-save and https://vanitystock.com/en-de/collections/vanity-or-premium-deals took over 3 s to send their HTML from our server.

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

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

Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

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 1,085 words of visible text.

Opening the homepage sets 11 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 6 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.