mhwigs.com.au website review

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

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

8 third-party services load with your homepage (Google Tag Manager, Klaviyo and Clarity and others), adding 2.1 MB and 994 ms of main-thread time.

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

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

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

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

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

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

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

Shopify costs a phone 124 ms of main-thread work and 638 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 91 KiB of CSS is downloaded but never applied on this page.

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

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

17 KiB JavaScript is shipped twice across bundles.

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.

3 KiB could be saved by minifying JavaScript.

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

Your largest element takes 6.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Genesis Hand Tied™ 16" - Soft Linen Blonde”.

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

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

Your homepage downloads 10.3 MB in 495 requests on a phone: media 6.0 MB (1), scripts 2.0 MB (226) and other files 969 KiB (171). Under 2 MB keeps phones on slow connections fast.

1 image (35 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.

5 images further down the page (111 KiB) 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 2.93 g of CO₂e: 351.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

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

1 image has no alt text, which hurts accessibility and image search.

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

Your <h1> is empty.

The homepage links to 151 pages on mhwigs.com.au and 15 external pages.

https://mhwigs.com.au/collections/new-arrivals-1 has no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://mhwigs.com.au/collections/genesis-hand-tied%E2%84%A2-luxury-synthetic-wigs, whose canonical is https://mhwigs.com.au/collections/genesis-hand-tied%e2%84%a2-luxury-synthetic-wigs. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://mhwigs.com.au/collections/new-arrivals-1, https://mhwigs.com.au/collections/best-sellers, https://mhwigs.com.au/collections/13-x-6-lace-front, https://mhwigs.com.au/collections/14-inch, https://mhwigs.com.au/collections/18-inch and https://mhwigs.com.au/collections/22-inch and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

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

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.

Social proof on the homepage: 31 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

The homepage shows no opening hours. If customers visit or call, show when.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

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