nuu3.com website review

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

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

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

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

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

8 third-party services load with your homepage (rebuyengine.com, gotolstoy.com and Google CDN and others), adding 2.4 MB and 896 ms of main-thread time.

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

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

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

8 KiB could be saved by minifying JavaScript.

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

Google CDN costs a phone 142 ms of main-thread work and 298 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 130 ms of main-thread work and 354 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.

LoyaltyLion costs a phone 53 ms of main-thread work and 366 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 long tasks block the main thread while loading, the longest for 165 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).

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.

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

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

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

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

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

Scripts block taps and scrolling for 267 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.

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 5.2 MB in 487 requests on a phone: scripts 2.2 MB (138), other files 1.5 MB (284) and images 911 KiB (29). Under 2 MB keeps phones on slow connections fast.

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

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

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

1 frame has no title, so screen-reader users cannot tell what it contains.

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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

Elements with visible text labels do not have matching accessible names. (2 elements).

Your title is 69 characters, so Google will cut it off around 60: “Nuu3™ Supplements – Official Website | Shop Natural Health & Wellness”.

The homepage links to 76 pages on nuu3.com and 4 external pages.

https://www.nuu3.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

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

https://www.nuu3.com/pages/quiz, https://www.nuu3.com/pages/deals, https://www.nuu3.com/customer_authentication/redirect, https://www.nuu3.com/collections/products, https://www.nuu3.com/collections/boost-immunity and https://www.nuu3.com/collections/digestive-health and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.nuu3.com/pages/rewards, https://www.nuu3.com/pages/deals and https://www.nuu3.com/customer_authentication/redirect have no <h1> headline, so visitors and search engines get no clear main topic.

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

2 images failed to load on a phone, for example https://cdn.shopify.com/s/files/1/0624/6642/5008/files/super-fuel-2048x2048-front_1_400x400.jpg?v=1747227809.

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

6 errors were logged to the browser console while the page loaded, for example “jQuery is not defined”.

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

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

Social proof on the homepage: 63 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

The homepage carries about 780 words of visible text.

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