mujiaustralia.com website review

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

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

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

57 images could be 7.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 800 ms faster on a phone.

8 third-party services load with your homepage (Heroku, Klaviyo and Google Tag Manager and others), adding 2.2 MB and 1.6 s of main-thread time.

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

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

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

Heroku costs a phone 379 ms of main-thread work and 59 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 84 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

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

Google Tag Manager costs a phone 208 ms of main-thread work and 316 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.

vitals.app costs a phone 155 ms of main-thread work and 428 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.

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

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

68 KiB JavaScript is shipped twice across bundles.

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

6 KiB could be saved by minifying CSS.

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.

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

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

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

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

Your homepage downloads 19.0 MB in 392 requests on a phone: images 15.6 MB (143), scripts 2.4 MB (148) and other files 667 KiB (80). Under 2 MB keeps phones on slow connections fast.

7 images weigh 4.8 MB together. On a phone connection a single image that size takes seconds.

21 images are downloaded at several times the size a phone draws them, for example W_s_Linen_Wide_Pants.png at 2,048 px wide, shown at 155 px. Resized copies would save about 5.2 MB.

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

2 images (779 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 5.40 g of CO₂e: 647.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

2 elements hidden from screen readers can still receive keyboard focus.

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

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

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

Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

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

Your title is 67 characters, so Google will cut it off around 60: “MUJI Australia Online | Shop Household, Stationery, Clothing & More”.

There are 3 <h1> headlines (“Made for Summer Comfort”, “MUJI Furniture” and “Household, Stationery, Clothing & More”). One clear main headline is easier for people and search engines.

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

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

The homepage links to 543 pages on mujiaustralia.com and 18 external pages.

https://muji.com.au/collections/new-lower-price and https://muji.com.au/collections/back-in-stock use the same meta description. A description written for each page earns more clicks.

https://muji.com.au/pages/newsletter-subscription, https://muji.com.au/collections/best-sellers, https://muji.com.au/collections/best-of-fashion, https://muji.com.au/collections/holiday-gifting and https://muji.com.au/collections/household have no <h1> headline, so visitors and search engines get no clear main topic.

https://muji.com.au/collections/best-of-fashion has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

https://muji.com.au/collections/new-clothing-accessories, https://muji.com.au/collections/best-sellers, https://muji.com.au/collections/best-of-food, https://muji.com.au/collections/best-of-home, https://muji.com.au/collections/best-of-fashion and https://muji.com.au/collections/holiday-gifting and 1 other took over 3 s to send their HTML from our server.

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

4 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://muji.com.au/cdn/shop/t/144/assets/tiny.content.min.css?v=50921' because its MIME t…”.

Requests the notification permission on page load.

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

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

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

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