bloombaby.com.au website review

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

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Hotjar and Shopify and others), adding 1.4 MB and 597 ms of main-thread time.

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

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

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

37 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 150 ms faster on a phone.

4 long tasks block the main thread while loading, the longest for 167 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.

Your largest element takes 13.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “begin life in style baby furniture you wish you had as a ki…”.

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

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

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

The first text or image appears after 2.4 s on a phone. Good is under 1.8 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.

2 images weigh 1.2 MB together. On a phone connection a single image that size takes seconds.

3 images are downloaded at several times the size a phone draws them, for example Bloom-TriBeCa-SHK56_2_1.webp at 3,600 px wide, shown at 360 px. Resized copies would save about 643 KiB.

Your homepage downloads 3.8 MB in 219 requests on a phone: images 1.6 MB (37), scripts 1.5 MB (136) and fonts 234 KiB (4). Under 2 MB keeps phones on slow connections fast.

14 images (2.2 MB) 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.

15 images further down the page (1.6 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

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

Documents must have <title> element to aid in navigation: 1 element on the page fails this check, rated serious by axe-core.

<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

1 tap target is too small or too close together to hit reliably with a finger.

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

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

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

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

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

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

Your page has no <title>, so Google has to invent the blue link in search results.

No meta description, so Google writes its own snippet from whatever text it finds.

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

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

The homepage links to 111 pages on bloombaby.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.

Your homepage links to https://bloombaby.com.au/products/alma-mini, https://bloombaby.com.au/products/alma-grow-crib, https://bloombaby.com.au/products/alma-papa-crib, https://bloombaby.com.au/products/alma-papa-toddler-rail, https://bloombaby.com.au/products/alma-max-toddler-rail and https://bloombaby.com.au/products/crib-storage, which answer with an error. Visitors hit a dead end and search engines drop them.

https://bloombaby.com.au/collections/highchairs, https://bloombaby.com.au/collections/cribs-dressers, https://bloombaby.com.au/collections/bouncers, https://bloombaby.com.au/collections/sale, https://bloombaby.com.au/collections/fitted-sheets and https://bloombaby.com.au/collections/crib-mattresses and 3 others have no <title>, so Google invents the link text in results.

https://bloombaby.com.au/collections/highchairs, https://bloombaby.com.au/collections/cribs-dressers, https://bloombaby.com.au/collections/bouncers, https://bloombaby.com.au/collections/sale, https://bloombaby.com.au/collections/fitted-sheets and https://bloombaby.com.au/collections/crib-mattresses and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

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

7 of 30 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 “Cannot assign to read only property 'protect' of object '#<Object>'”.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Klaviyo (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 24 cookies, 2 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.