Website review, no card needed

uclassic.com.au logo

uclassic.com.au website review

Visit site (opens in a new tab)Reviewed 16 November 202629 issues · 84 checks

This review found 29 issues worth fixing on uclassic.com.au, 12 of them high impact, across 84 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
2.5 s1.7 sMay 30Nov 141.8 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.4 s
Jun 6, 20262.3 s
Jun 13, 20262.3 s
Jun 20, 20262.3 s
Jun 27, 20262.3 s
Jul 4, 20262.3 s
Jul 11, 20262.2 s
Jul 18, 20262.1 s
Jul 25, 20262.2 s
Aug 1, 20262.2 s
Aug 22, 20262.2 s
Aug 29, 20262.1 s
Sep 5, 20262.2 s
Sep 12, 20262.2 s
Sep 19, 20262.1 s
Sep 26, 20262.1 s
Oct 3, 20262.0 s
Oct 10, 20261.9 s
Oct 17, 20261.9 s
Oct 24, 20261.8 s
Oct 31, 20261.8 s
Nov 7, 20261.8 s
Nov 14, 20261.8 s
Real-visitor tap response (INP)75th percentile, phones
166 ms116 msMay 30Nov 14135 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026122 ms
Jun 6, 2026126 ms
Jun 13, 2026122 ms
Jun 20, 2026133 ms
Jun 27, 2026145 ms
Jul 4, 2026160 ms
Jul 11, 2026150 ms
Jul 18, 2026142 ms
Jul 25, 2026147 ms
Aug 1, 2026142 ms
Aug 22, 2026153 ms
Aug 29, 2026152 ms
Sep 5, 2026153 ms
Sep 12, 2026155 ms
Sep 19, 2026152 ms
Sep 26, 2026146 ms
Oct 3, 2026145 ms
Oct 10, 2026138 ms
Oct 17, 2026140 ms
Oct 24, 2026136 ms
Oct 31, 2026135 ms
Nov 7, 2026136 ms
Nov 14, 2026135 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of uclassic.com.au (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. uclassic.com.au at 0.4 s0.4 s
  2. uclassic.com.au at 0.8 s0.8 s
  3. uclassic.com.au at 1.3 s1.3 s
  4. uclassic.com.au at 1.7 s1.7 s
  5. uclassic.com.au at 2.1 s2.1 s
  6. uclassic.com.au at 2.5 s2.5 s
  7. uclassic.com.au at 2.9 s2.9 s
  8. uclassic.com.au at 3.4 s3.4 s

Speed

6 to fix94
  • Render-blocking requests

    1.1 s

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

  • 3,635 HTML elements

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

  • Improve image delivery

    3.3 MB

    43 images could be 3.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 5 third-party services on the page

    5 third-party services load with your homepage (Shopify, Bugsnag and shop.app and others), adding 2.9 MB and 376 ms of main-thread time.

  • Shopify adds 371 ms

    371 ms

    Shopify costs a phone 371 ms of main-thread work and 2.8 MB 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.

  • Main-thread work: 2.4 s

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

  • Reduce unused JavaScript

    188 KiB

    About 188 KiB of JavaScript is downloaded but never used on this page.

  • 3 long tasks on the main thread

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

  • Use efficient cache lifetimes

    109 KiB

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

  • Reduce unused CSS

    64 KiB

    About 64 KiB of CSS is downloaded but never applied on this page.

  • Legacy JavaScript

    30 KiB

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

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

  • Minify JavaScript

    3 KiB

    3 KiB could be saved by minifying JavaScript.

2 checks passed
  • Mobile performance score: 94

    94/100

    Your mobile performance score is 94. That is in Google's “good” band (90 and up).

  • Server response: 10 ms

    10 ms

    Your server sent the HTML in 10 ms, well inside Google's 600 ms guideline.

Core Web Vitals

3 to fix100
  • Speed Index: 6.4 s

    6.4 s

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

  • Time to Interactive: 7.8 s

    7.8 s

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

  • 1 image without width and height

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

  • Tap response (INP) held steady for real visitors

    +9%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 122 ms to 135 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

11 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.9 s

    1.9 s

    Real visitors wait 1.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 104 ms

    104 ms

    Real visitors wait 104 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.01

    0.01

    For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.

  • Real-user FCP: 0.9 s

    0.9 s

    Real visitors see the first content after 0.9 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 537 ms

    537 ms

    Real visitors wait 537 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Largest content (LCP) got 23% faster for real visitors

    -23%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 2.4 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Total Blocking Time: 81 ms

    81 ms

    Scripts block the page for only 81 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

  • First Contentful Paint: 1.1 s

    1.1 s

    The first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.

  • Largest Contentful Paint: 1.1 s

    1.1 s

    Your largest element renders in 1.1 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “UGG Store based in Sydney, Australia, offering fast global …”.

Images and page weight

3 to fix42
  • Page weight: 6.1 MB in 331 requests

    6.1 MB

    Your homepage downloads 6.1 MB in 331 requests on a phone: images 4.1 MB (125), other files 1.0 MB (148) and scripts 698 KiB (45). Under 2 MB keeps phones on slow connections fast.

  • 8 images far larger than shown

    910 KiB

    8 images are downloaded at several times the size a phone draws them, for example c1_e1e74c91-3e6a-4911-a697-8eccb9c0d79a.jpg at 2,000 px wide, shown at 165 px. Resized copies would save about 910 KiB.

  • An image on the first screen is lazy-loaded

    black_friday_sale_-_uclassics_1080_x_1440_px.jpg 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).

  • About 1.7 g of CO₂ per visit

    1.72 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

9 to fixGoogle 8588
  • Hidden but focusable

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

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 1 tap target too small

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

  • 1 image without alt text

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

  • All page content should be contained by landmarks (5 elements)

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

  • Page should contain a level-one heading (1 element)

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

  • 28 form fields without a label

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

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Alternative text of images should not be repeated as text (1 element)

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

  • Elements with visible text labels do not have matching accessible names.

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

1 checks passed
  • 46 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 8 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 9287
  • No H1 headline

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

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 256 internal links, 0 external

    The homepage links to 256 pages on uclassic.com.au and 0 external pages.

6 checks passed
  • Meta description: 126 characters

    Your meta description is 126 characters: “U CLASSIC offers authentic Australian sheepskin ugg boots. Comfortable, stylish, and made to last. Shop best selling ug…”.

  • Title: 54 characters

    Your title is a healthy 54 characters: “U CLASSIC | Australian Sheepskin Ugg Boots – U Classic”.

  • Canonical URL set

    The canonical URL is https://uclassic.com.au/.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://uclassic.com.au/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing logo, description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

3 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Text is in the HTML

    Your server sends the page's text in the HTML (703 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://uclassic.com.au/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

1 to fix95
  • 9 pages without an H1

    https://uclassic.com.au/collections/women, https://uclassic.com.au/collections/thongs-fluff, https://uclassic.com.au/collections/slippers-and-scuffs, https://uclassic.com.au/collections/traditional-slipper, https://uclassic.com.au/collections/moccasins-1 and https://uclassic.com.au/collections/scuffs-1 and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 3 pages with very little text

    https://uclassic.com.au/collections/slippers-and-scuffs, https://uclassic.com.au/collections/moccasins-1 and https://uclassic.com.au/collections/scuffs-1 have 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.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Swatch King: Incorrect option selector, option element was not found!”.

2 checks passed
  • Tap targets are thumb-sized

    51 of 63 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • No call to action on the first screen

    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 analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

  • About 371 words of copy

    The homepage carries about 371 words of visible text.

4 checks passed
  • 9 calls to action

    The homepage has 9 calls to action, for example “Shop All Women”, “Shop All Men” and “Contact Us”.

  • 4 short forms

    4 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 1 customer or partner logo and 3 trust badges.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 1 email link.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 11 cookies set on arrival

    11

    Opening the homepage sets 11 cookies (measured from a US location before any click).

  • No consent tool detected

    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.

  • 18 other companies contacted

    Loading the homepage contacts 18 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at uclassic.com.au, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 6 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Essential A B Testing · Swatch King · Transcy · Ecomposer Builder · Variant Image Swatch · Booster Kit By Qikify

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

Framework
jQuery
E-commerce
Shopify
Hosting
Shopify

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 29 issues on uclassic.com.au, including 9 speed issues, 2 SEO issues and 2 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25