uggoriginal.com.au website review

About 628 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 4.5 s on main-thread work while loading, 1.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

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

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

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

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

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

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

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

5 images could be 149 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.

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

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

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 7.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “ugg boot show by shearers ugg Men Ugg Women UGG Kids UGG Ba…”.

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

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

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

1 image 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 113 ms to 123 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 1.4 s to 1.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 3.4 MB in 302 requests on a phone: scripts 1.7 MB (117), other files 785 KiB (115) and images 694 KiB (49). Under 2 MB keeps phones on slow connections fast.

MUA18_-_Runway_Show_-_Front_-_June_26-243_Image_by_Jarrad_Se is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

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

1 element use ARIA attributes their role does not allow, which confuses screen readers.

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

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

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

ARIA input fields must have an accessible name: 2 elements on the page fail this check, rated serious by axe-core.

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

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

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

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

Elements marked as presentational should be consistently ignored: 1 element on the page fails this check, rated minor by axe-core.

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

Your meta description is 258 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.

Your <h1> is empty.

The homepage links to 108 pages on uggoriginal.com.au and 22 external pages.

https://www.uggoriginal.com.au/products/cloud-mua-sneaker and https://www.uggoriginal.com.au/collections/all-collection/products/activugg-mini-short-boot declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.

/, https://www.uggoriginal.com.au/products/cloud-mua-sneaker and https://www.uggoriginal.com.au/collections/all-collection/products/activugg-mini-short-boot all use the title “SHEARERS Ugg Official Online Store”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.uggoriginal.com.au/products/cloud-mua-sneaker and https://www.uggoriginal.com.au/collections/all-collection/products/activugg-mini-short-boot use the same meta description. A description written for each page earns more clicks.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=56369046&tm=gtm002&Ver=2&mid=c971bbab-5b6a-42bc-8157-eb8f444b8477&bo=1&sid=e708fee0dd7f11f1baa8e75f9483b185&vid=e7092080dd7f11f1b22fad7fefd8124e&vids=1&msclkid=N&pi=91.

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

3 errors were logged to the browser console while the page loaded, for example “Uncaught TypeError: Cannot read properties of undefined (reading 'global_config')”.

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

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.

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

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Ads (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 15 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.