astin.com.au website review

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

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

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

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

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

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

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

7 third-party services load with your homepage (Shopify, Lucky Orange and chatty.net and others), adding 232 KiB and 85 ms of main-thread time.

1 long task block the main thread while loading, the longest for 69 ms. During a long task the page ignores taps.

3 images could be 49 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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 “Modern building exterior with illuminated steps and lights …”.

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

The layout shifts by 0.34 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

The first text or image appears after 3.2 s on a phone. Good is under 1.8 s.

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 2.1 MB in 170 requests on a phone: other files 755 KiB (91), images 738 KiB (24) and scripts 383 KiB (44). Under 2 MB keeps phones on slow connections fast.

image_23.webp 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).

2 images are downloaded at several times the size a phone draws them, for example Astin_Main_logo_all_White_Mettalic_70c55481-58b7-4274-a534-2 at 1,001 px wide, shown at 125 px. Resized copies would save about 318 KiB.

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

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

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

Alternative text of images should not be repeated as text: 6 elements on the page fail this check, rated minor by axe-core.

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

There are 2 <h1> headlines (“Astin Emporium” and “Light up your home in style”). One clear main headline is easier for people and search engines.

The homepage links to 120 pages on astin.com.au and 1 external page.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

Your homepage links to https://www.astin.com.au/customer_authentication/redirect, which answers with an error. Visitors hit a dead end and search engines drop it.

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

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 400 ()”.

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

Social proof on the homepage: 10 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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.

The homepage has only about 111 words of visible text; thin pages give Google and first-time buyers little to go on.

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

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