gearshop.com.au website review

17 images could be 447 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.3 s faster on a phone.

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

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

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

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

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

8 third-party services load with your homepage (latitudefinancial.com, LoyaltyLion and swish.app and others), adding 1.3 MB and 615 ms of main-thread time.

About 82 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.

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

latitudefinancial.com costs a phone 243 ms of main-thread work and 449 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.

LoyaltyLion costs a phone 90 ms of main-thread work and 347 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.

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

5 KiB could be saved by minifying JavaScript.

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

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 8.2 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 17.5 s. Good is under 3.8 s.

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 5.4 MB in 504 requests on a phone: images 2.5 MB (116), scripts 1.5 MB (172) and other files 1.1 MB (201). Under 2 MB keeps phones on slow connections fast.

Gearshop_Brands_Big_Agnes_Sleep_Mats-banner-desktop.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).

6 images (425 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.

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

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

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

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

Heading levels should only increase by one: 2 elements on the page fail this check, rated moderate by axe-core.

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

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

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

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

The homepage links to 759 pages on gearshop.com.au and 0 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), 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.

https://www.gearshop.com.au/policies/shipping-policy and https://www.gearshop.com.au/collections/bivouac-emergency-shelters have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.gearshop.com.au/policies/shipping-policy, https://www.gearshop.com.au/collections/lightweight-ultralight-tents, https://www.gearshop.com.au/collections/tarpaulins, https://www.gearshop.com.au/collections/tent-footprints, https://www.gearshop.com.au/collections/camping-hammocks and https://www.gearshop.com.au/collections/tent-hammock-accessories and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

3 errors were logged to the browser console while the page loaded, for example “renderInContainer(): could not find container: latitude-product-widget”.

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

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

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

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