oztrail.com.au website review

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

Your mobile performance score is 48. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

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

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

8 third-party services load with your homepage (Clarity, Klaviyo and Yotpo and others), adding 735 KiB and 733 ms of main-thread time.

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

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

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

Klaviyo costs a phone 150 ms of main-thread work and 312 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 13 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.

69 KiB JavaScript is shipped twice across bundles.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

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

7 KiB could be saved by minifying JavaScript.

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.

3 KiB could be saved by minifying CSS.

Your largest element takes 10.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “OUR BIGGEST SALE OF THE YEAR - NOW ON! BLACK FRIDAY UP TO 6…”.

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

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

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

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

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

Your homepage downloads 3.1 MB in 277 requests on a phone: scripts 1.4 MB (105), other files 747 KiB (108) and images 466 KiB (25). Under 2 MB keeps phones on slow connections fast.

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

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

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

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

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

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

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

There are 2 <h1> headlines (“” and “BLACKFRIDAY”). One clear main headline is easier for people and search engines.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 627 pages on oztrail.com.au and 5 external pages.

https://www.oztrail.com.au/collections/clearance has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.oztrail.com.au/pages/black-friday and https://www.oztrail.com.au/policies/shipping-policy use the same meta description. A description written for each page earns more clicks.

https://www.oztrail.com.au/pages/black-friday, https://www.oztrail.com.au/policies/shipping-policy, https://www.oztrail.com.au/collections/sale, https://www.oztrail.com.au/collections/clearance, https://www.oztrail.com.au/collections/best-sellers and https://www.oztrail.com.au/collections/new-arrivals and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.oztrail.com.au/collections/clearance took over 3 s to send its HTML from our server.

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

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

Large scripts ship without source maps.

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.

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 1,498 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

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