ninabailey.com.au website review

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

6 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.

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

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

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

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

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

6 third-party services load with your homepage (Shopify, Clarity and wholesalegorilla.app and others), adding 544 KiB and 363 ms of main-thread time.

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

32 KiB could be saved by minifying JavaScript.

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

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

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

28 KiB JavaScript is shipped twice across bundles.

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.

4 KiB could be saved by minifying CSS.

Your largest element takes 8.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Banner Image”.

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

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

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

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 16.8 MB in 261 requests on a phone: media 14.4 MB (1), other files 895 KiB (145) and scripts 722 KiB (51). Under 2 MB keeps phones on slow connections fast.

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

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

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

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

The homepage links to 206 pages on ninabailey.com.au and 3 external pages.

https://ninabailey.com.au/pages/ws-quick-order-form is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://ninabailey.com.au/collections/face, https://ninabailey.com.au/collections/body, https://ninabailey.com.au/collections/perfume-oils, https://ninabailey.com.au/collections/gift-bundles, https://ninabailey.com.au/collections/gift-packs-bundles and https://ninabailey.com.au/collections/gifts-under-20 and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://ninabailey.com.au/pages/about-us, https://ninabailey.com.au/pages/contact-us and https://ninabailey.com.au/pages/ws-quick-order-form have no <h1> headline, so visitors and search engines get no clear main topic.

https://ninabailey.com.au/collections/face, https://ninabailey.com.au/collections/body and https://ninabailey.com.au/collections/perfume-oils took over 3 s to send their HTML from our server.

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

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

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

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