saison.com.au website review

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

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

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

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

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

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

Klaviyo costs a phone 94 ms of main-thread work and 310 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.

Shopify costs a phone 53 ms of main-thread work and 399 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.

8 third-party services load with your homepage (Klaviyo, Shopify and nfcube.com and others), adding 977 KiB and 209 ms of main-thread time.

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

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

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

28 KiB JavaScript is shipped twice across bundles.

21 KiB could be saved by minifying JavaScript.

Polyfills for old browsers add 19 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 16.1 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 21.6 s. Good is under 3.8 s.

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

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-11-07, real Chrome visitors' tap response (inp) went from 88 ms to 122 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 21.1 MB in 353 requests on a phone: media 14.3 MB (5), images 4.5 MB (54) and scripts 1.0 MB (128). Under 2 MB keeps phones on slow connections fast.

2 images weigh 1.4 MB together. On a phone connection a single image that size takes seconds.

Website_Tile-Claus_Porto-Brand_Tiles2.png 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).

1 image (171 KiB) is 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.

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

10 buttons have no accessible name, so screen readers announce just “button”.

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

Scrollable region must have keyboard access: 7 elements on the page fail this check, rated serious by axe-core.

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

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

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

Your title is 68 characters, so Google will cut it off around 60: “Saison: Distributor of The World's Best Fragrance & Lifestyle Brands”.

There are 3 <h1> headlines (“”, “SALE ON NOW” and “SALE ON NOW”). One clear main headline is easier for people and search engines.

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

The homepage links to 427 pages on saison.com.au and 7 external pages.

https://www.saison.com.au/collections and https://www.saison.com.au/collections/acca-kappa have no <h1> headline, so visitors and search engines get no clear main topic.

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

3 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'classList')”.

Social proof on the homepage: “200,000+ Happy customers”. 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.

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

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