nothingnaughty.com.au website review

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

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

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

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

1 long task block the main thread while loading, the longest for 396 ms. During a long task the page ignores taps.

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

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

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

8 third-party services load with your homepage (Shopify, 506.io and 9gtb.com and others), adding 729 KiB and 259 ms of main-thread time.

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

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

Polyfills for old browsers add 22 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 4.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

For real visitors the layout shifts by 0.23 (75th percentile). Good is under 0.1.

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

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

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

18 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' tap response (inp) went from 121 ms to 137 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

1 image (43 KiB) is 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.57 g of CO₂e: 68.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

3 tap targets are too small or too close together to hit reliably with a finger.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

Alternative text of images should not be repeated as text: 6 elements on the page fail this check, rated minor by axe-core.

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

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

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 175 pages on nothingnaughty.com.au and 14 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.nothingnaughty.com.au/pages/about-us, https://www.nothingnaughty.com.au/pages/blog, https://www.nothingnaughty.com.au/pages/tirau-store, https://www.nothingnaughty.com.au/collections/all, https://www.nothingnaughty.com.au/collections/pantry and https://www.nothingnaughty.com.au/pages/keto and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

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

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

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 989 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 18 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 35 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.