banuskin.com website review

About 326 KiB of JavaScript is downloaded but never used on this page. 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 (308 KiB).

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

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

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

8 third-party services load with your homepage (alia-prod.com, Clarity and Klaviyo and others), adding 979 KiB and 483 ms of main-thread time.

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

5 images could be 109 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

2 KiB could be saved by minifying CSS.

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

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

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

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

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

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

Your homepage downloads 3.0 MB in 228 requests on a phone: scripts 1,008 KiB (75), other files 818 KiB (107) and fonts 565 KiB (15). Under 2 MB keeps phones on slow connections fast.

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

Some lists contain elements other than list items, which screen readers announce wrongly.

1 tap target is too small or too close together to hit reliably with a finger.

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

ARIA role should be appropriate for the element: 22 elements on the page fail this check, rated minor by axe-core.

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

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is 80 characters, so Google will cut it off around 60: “Banu Skin | Clinically Tested, Acne-Safe Skincare That Actually Works – banuskin”.

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

Structured data found (WebSite) but with 1 problem, for example “ld+json block 1 is not valid JSON (Expected double-quoted property name in JSON at position 230)”.

6 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 123 pages on banuskin.com and 38 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://banuskin.com/collections/hsa-fsa-eligible, https://banuskin.com/collections/bundle-and-save-acne-care-kits, https://banuskin.com/apps/gbb/easybundle/1, https://banuskin.com/pages/hsa-fsa, https://banuskin.com/products/the-starter-set and https://banuskin.com/pages/about and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

https://banuskin.com/apps/gbb/easybundle/1 and https://banuskin.com/pages/hsa-fsa have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

Social proof on the homepage: 1 testimonial or review block. 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.

The homepage carries about 462 words of visible text.

Before a visitor clicks anything, the page loads Klaviyo and Microsoft Clarity (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 4 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 28 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.