nourishmax.com website review

YouTube costs a phone 10.0 s of main-thread work and 12.0 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

About 6.7 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.8 s faster on a phone.

About 136 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 4.4 s faster on a phone.

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

Your mobile performance score is 13. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

8 third-party services load with your homepage (YouTube, Intercom and Shopify and others), adding 13.9 MB and 11.7 s of main-thread time.

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

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

Intercom costs a phone 391 ms of main-thread work and 234 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 308 ms of main-thread work and 530 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 321 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.

Other Google APIs/SDKs costs a phone 249 ms of main-thread work and 308 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 2,021 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

2 images could be 17 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. 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).

Polyfills for old browsers add 18 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.

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 23.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “WOMAN HOLDING Ceramides & Lipids Complex Restorative Serum”.

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

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

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

The layout shifts by 0.402 while loading, so content jumps under the reader's thumb. Good is under 0.1.

Real visitors wait 2.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

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

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

Your homepage downloads 17.0 MB in 573 requests on a phone: scripts 11.9 MB (160), other files 1.5 MB (291) and HTML 1.4 MB (31). Under 2 MB keeps phones on slow connections fast.

nm-sale-up-to-40.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).

2 images further down the page (52 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

12 frames have no title, so screen-reader users cannot tell what they contain.

2 elements hidden from screen readers can still receive keyboard focus.

1 text element doesn'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.

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

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

Your title is 69 characters, so Google will cut it off around 60: “NourishMax Maximize Your Youth With Natural Skin & Hair Care Products”.

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

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

3 links have no real href, so search engines can't follow them.

The homepage links to 115 pages on nourishmax.com and 15 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://www.nourishmax.com/collections/all, https://www.nourishmax.com/collections/haircare, https://www.nourishmax.com/collections/supplements, https://www.nourishmax.com/collections/body-care, https://www.nourishmax.com/policies/shipping-policy and https://www.nourishmax.com/policies/refund-policy have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 5 pages by a URL that isn't their canonical one, for example https://www.nourishmax.com/collections/devices/products/advanced-5d-pro-light-therapy-face-mask, whose canonical is https://www.nourishmax.com/products/advanced-5d-pro-light-therapy-face-mask. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.nourishmax.com/collections/all, https://www.nourishmax.com/collections/skincare, https://www.nourishmax.com/collections/haircare, https://www.nourishmax.com/collections/supplements, https://www.nourishmax.com/collections/body-care and https://www.nourishmax.com/collections/devices/products/advanced-5d-pro-light-therapy-face-mask and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

2 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=187033488&Ver=2&mid=b067eb76-16ac-45a9-b777-8be9d119ca88&bo=1&sid=77d34f30d39c11f1815971e13597b524&vid=77dcb7f0d39c11f1bf5f2130fb0b0ac5&vids=1&msclkid=N&pi=918639831&l.

6 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

3 of 12 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 “Failed to load resource: net::ERR_FAILED”.

Large scripts ship without source maps.

Chrome logged issues while loading the page (“Cookie”).

The homepage carries about 1,470 words of visible text.

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