saturdaysnyc.com.au website review

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, jQuery CDN and Klaviyo and others), adding 2.7 MB and 1.7 s of main-thread time.

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

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

Klaviyo costs a phone 260 ms of main-thread work and 627 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 316 ms. During a long task the page ignores taps.

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

jQuery CDN costs a phone 271 ms of main-thread work and 34 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.

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

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

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

About 82 KiB of CSS is downloaded but never applied on this page.

19 KiB could be saved by minifying JavaScript.

13 KiB could be saved by minifying CSS.

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.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

Your largest element takes 13.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Saturdays NYC Holiday 2026 new arrivals”.

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

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

Real visitors wait 2.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors wait 355 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

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

Real visitors see the first content after 2.6 s (75th percentile). Good is under 1.8 s.

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

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

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

Your homepage downloads 6.9 MB in 406 requests on a phone: images 2.9 MB (22), scripts 2.6 MB (228) and other files 1.0 MB (126). Under 2 MB keeps phones on slow connections fast.

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

1 image (621 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.

2 images are downloaded at several times the size a phone draws them, for example Holiday26_Hero_Flannels_Mobile_1440x2024_667e5ee1-b894-4e8c- at 1,440 px wide, shown at 390 px. Resized copies would save about 143 KiB.

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

Interactive controls must not be nested: 11 elements on the page fail this check, rated serious by axe-core.

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

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

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

All page content should be contained by landmarks: 29 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.

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

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

3 form fields have no label, so screen readers announce an empty box and autofill guesses.

1 tap target is too small or too close together to hit reliably with a finger.

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

The homepage links to 345 pages on saturdaysnyc.com.au and 2 external pages.

Your Organization JSON-LD is missing logo, 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.

robots.txt blocks GPTBot and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

https://www.saturdaysnyc.com.au/collections/mens-tops and https://www.saturdaysnyc.com.au/collections/category-mens-tops all use the title “Men's Tops | Saturdays NYC”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.saturdaysnyc.com.au/collections/holiday-26, https://www.saturdaysnyc.com.au/collections/champion-for-saturdays and https://www.saturdaysnyc.com.au/collections/womens-new-arrivals have no meta description, so Google writes the search snippet from whatever text it finds.

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

38 of 153 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

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

Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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