nuzest.com.au website review

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

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

8 third-party services load with your homepage (Klaviyo, squarecdn.com and rechargecdn.com and others), adding 1.4 MB and 2.8 s of main-thread time.

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

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

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

About 725 KiB of JavaScript is downloaded but never used on this page.

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

squarecdn.com costs a phone 401 ms of main-thread work and 192 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.

rechargecdn.com costs a phone 370 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.

okendo.io costs a phone 336 ms of main-thread work and 358 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 326 ms of main-thread work and 97 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.

4 images could be 35 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.

Polyfills for old browsers add 82 KiB JavaScript that modern phones do not need.

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

3 KiB could be saved by minifying JavaScript.

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

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

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

Your largest element takes 4.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is element render delay (2.3 s).

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

Your homepage downloads 10.2 MB in 231 requests on a phone: media 6.4 MB (1), scripts 1.9 MB (100) and images 844 KiB (32). Under 2 MB keeps phones on slow connections fast.

nuzest_shop_our_best_sellers.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 2.89 g of CO₂e: 347.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

12 buttons have no accessible name, so screen readers announce just “button”.

1 dropdown has no label.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

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

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

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

The homepage links to 92 pages on nuzest.com.au and 3 external pages.

Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

https://www.nuzest.com.au/collections/all has no <h1> headline, so visitors and search engines get no clear main topic.

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

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

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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

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.

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.

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

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