smartkits.com.au website review

Shopify costs a phone 1.0 s of main-thread work and 480 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

8 third-party services load with your homepage (Shopify, Google Tag Manager and Lucky Orange and others), adding 1.7 MB and 1.9 s of main-thread time.

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

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

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

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

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

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

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

Polyfills for old browsers add 35 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.

Your largest element takes 15.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “20% OFF & FREE SHIPPING!”.

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

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

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

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

Your homepage downloads 5.6 MB in 294 requests on a phone: images 2.7 MB (23), scripts 1.8 MB (71) and other files 997 KiB (162). Under 2 MB keeps phones on slow connections fast.

GET_SUMMER_READY.svg weighs 1.8 MB. On a phone connection a single image that size takes seconds.

GET_SUMMER_READY.svg 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 1.60 g of CO₂e: 191.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

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

Your title is 90 characters, so Google will cut it off around 60: “DIY Patio & Pergola Kits | Carports | Decks & Gazebos Australia Wide – SmartKits Australia”.

Your meta description is 161 characters; Google truncates after about 160, so the end of your pitch is cut.

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

Your <h1> is empty.

The homepage links to 129 pages on smartkits.com.au and 8 external pages.

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

https://smartkits.com.au/collections/gable-patio-roofs and https://smartkits.com.au/collections/gable-patio-roofs-freestanding use the same meta description. A description written for each page earns more clicks.

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

4 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 ()”.

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 testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and HubSpot and 3 mores (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 33 cookies, 8 of them by other companies (measured from a US location before any click).

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