vanman.shop website review

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

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

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

8 third-party services load with your homepage (alia-prod.com, Google Tag Manager and Shopify and others), adding 1.1 MB and 869 ms of main-thread time.

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

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

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

alia-prod.com costs a phone 309 ms of main-thread work and 262 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.

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

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

12 long tasks block the main thread while loading, the longest for 179 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).

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

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.

2 KiB could be saved by minifying CSS.

2 KiB could be saved by minifying JavaScript.

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 8.9 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 18.6 s. Good is under 3.8 s.

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

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

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

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

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

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

17 images have no width and height attributes, so the layout jumps as each one loads.

Your homepage downloads 4.0 MB in 293 requests on a phone: other files 1.1 MB (163), scripts 1.1 MB (65) and images 1,011 KiB (27). Under 2 MB keeps phones on slow connections fast.

1 image (122 KiB) is 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 1.13 g of CO₂e: 135.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

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

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

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

1 link has no real href, so search engines can't follow it.

The homepage links to 127 pages on vanman.shop and 4 external pages.

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://vanman.shop/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://vanman.shop/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://vanman.shop/collections/face-body and https://vanman.shop/collections/natural-deodorants all use the title “VanMans Natural Deodorants”. Search engines can't tell which page to show for a search, so each competes with the others.

https://vanman.shop/collections/best-sellers, https://vanman.shop/collections/bundles, https://vanman.shop/customer_authentication/redirect, https://vanman.shop/collections/newly-released, https://vanman.shop/collections/face-body and https://vanman.shop/collections/tallow-soaps and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

https://vanman.shop/collections/bundles, https://vanman.shop/customer_authentication/redirect and https://vanman.shop/collections/vanman-collection have no <h1> headline, so visitors and search engines get no clear main topic.

https://vanman.shop/collections/tallow-soaps took over 3 s to send its HTML from our server.

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

2 images failed to load on a phone, for example https://vanman.shop/.

Social proof on the homepage: 56 testimonial or review blocks. 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 666 words of visible text.

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