nutrientrescue.nz website review

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

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

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

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

About 396 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

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

rechargecdn.com costs a phone 186 ms of main-thread work and 297 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.

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

About 132 KiB of CSS is downloaded but never applied on this page.

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

1 image could be 49 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

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

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

Real visitors wait 393 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

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

Your largest element takes 2.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Get a FREE Travel Pack with your Get Started Pack purchase”. Most of its time is element render delay (2.5 s).

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

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

Your homepage downloads 3.3 MB in 255 requests on a phone: scripts 1.1 MB (86), other files 867 KiB (120) and images 830 KiB (17). Under 2 MB keeps phones on slow connections fast.

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

2 images (92 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

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

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

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

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

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

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

Your title is 73 characters, so Google will cut it off around 60: “Natural New Zealand-grown superfood powders – Nutrient Rescue New Zealand”.

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

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

5 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 97 pages on nutrientrescue.nz and 23 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.

The HTML your server sends has 2,295 of the 4,289 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

https://nutrientrescue.nz/pages/10k-travel-voucher-giveaway, https://nutrientrescue.nz/pages/ingredients, https://nutrientrescue.nz/pages/subscribe-save, https://nutrientrescue.nz/pages/our-story and https://nutrientrescue.nz/pages/meet-our-growers have no <h1> headline, so visitors and search engines get no clear main topic.

https://nutrientrescue.nz/collections/shop, https://nutrientrescue.nz/collections/featured, https://nutrientrescue.nz/collections/bundles and https://nutrientrescue.nz/blogs/recipes took over 3 s to send their HTML from our server.

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

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

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

1 image is served at too low a resolution for sharp phone screens.

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.

The homepage carries about 4,289 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 21 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.