nemah.com website review

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

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

6 images could be 2.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

About 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 840 ms faster on a phone.

8 third-party services load with your homepage (Shopify, Klaviyo and tetralive.com and others), adding 2.9 MB and 1.5 s of main-thread time.

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

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

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

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

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

Klaviyo costs a phone 263 ms of main-thread work and 624 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.

tetralive.com costs a phone 218 ms of main-thread work and 382 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.

rebuyengine.com costs a phone 174 ms of main-thread work and 782 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.

PayPal costs a phone 212 ms of main-thread work and 393 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.

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

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

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

46 KiB could be saved by minifying CSS.

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.

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

Your largest element takes 9.0 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 12.6 s (Speed Index). Good is under 3.4 s.

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

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' largest content (lcp) went from 1.7 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 9.0 MB in 452 requests on a phone: images 3.7 MB (45), scripts 2.6 MB (171) and other files 1.1 MB (183). Under 2 MB keeps phones on slow connections fast.

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

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

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

1 button has no accessible name, so screen readers announce just “button”.

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

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

Your title is 68 characters, so Google will cut it off around 60: “Nēmah | Clean, Dermatologist-Tested Skincare Products for Mom & Baby”.

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

There are 2 <h1> headlines (“Nēmah” and “Nēmah”). One clear main headline is easier for people and search engines.

The homepage links to 218 pages on nemah.com and 9 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://nemah.com/pages/build-your-set, https://nemah.com/pages/community, https://nemah.com/blogs/all-blogs, https://nemah.com/pages/refer-a-friend, https://nemah.com/pages/rewards and https://nemah.com/pages/onward-track use the same meta description. A description written for each page earns more clicks.

https://nemah.com/collections/mom, https://nemah.com/collections/all, https://nemah.com/pages/community, https://nemah.com/pages/refer-a-friend, https://nemah.com/pages/onward-track and https://nemah.com/collections/best-sellers and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

The page uses 1 deprecated browser API that will stop working in future browsers (“CSS appearance value `slider-vertical` is not standardized and will be removed.”).

5 errors were logged to the browser console while the page loaded, for example “Unexpected token '<'”.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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 763 words of visible text.

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