samoh.in website review

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

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

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

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

8 third-party services load with your homepage (cloudfront.net, Shopify and Clarity and others), adding 1.0 MB and 801 ms of main-thread time.

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

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

cloudfront.net costs a phone 219 ms of main-thread work and 295 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.

Shopify costs a phone 169 ms of main-thread work and 333 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 long tasks block the main thread while loading, the longest for 153 ms. During a long task the page ignores taps.

About 17 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 JavaScript is shipped twice across bundles.

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

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

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

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

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

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

Your homepage downloads 3.1 MB in 237 requests on a phone: scripts 1,019 KiB (65), other files 998 KiB (113) and images 845 KiB (18). Under 2 MB keeps phones on slow connections fast.

banner3-mob_4785400c-985a-4c23-a02a-de980b0a00ba.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 0.88 g of CO₂e: 105.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

ARIA commands must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

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

Elements with visible text labels do not have matching accessible names. (1 element).

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

Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: logo is not an absolute URL ("https:files/Logo.svg")”.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

Your <h1> is empty.

The homepage links to 76 pages on samoh.in and 11 external pages.

https://www.samoh.in/collections/women-wear-view-all has no <h1> headline, so visitors and search engines get no clear main topic.

https://www.samoh.in/collections/women-wear-view-all has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

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

4 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'addEventListener')”.

3 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

2 images are served at too low a resolution for sharp phone screens.

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

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 165 words of visible text; thin pages give Google and first-time buyers little to go on.

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