mayfieldlighting.com.au website review

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, custompricecalculator.com and Shopify and others), adding 890 KiB and 644 ms of main-thread time.

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

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

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

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

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

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

13 KiB JavaScript is shipped twice across bundles.

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.

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

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

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

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

Your largest element takes 2.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “AUTUMN / WINTER 2026”. Most of its time is element render delay (2.6 s).

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

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 88 ms to 95 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.7 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 2.4 MB in 219 requests on a phone: scripts 1.0 MB (55), other files 775 KiB (105) and images 405 KiB (25). Under 2 MB keeps phones on slow connections fast.

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

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

1 image has no alt text, which hurts accessibility and image search.

All page content should be contained by landmarks: 3 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: 1 element on the page fails this check, rated moderate by axe-core.

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

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

Elements with visible text labels do not have matching accessible names. (1 element).

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is 69 characters, so Google will cut it off around 60: “Lighting Designed in Australia | Buy Lamps Online | Mayfield Lighting”.

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

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 205 pages on mayfieldlighting.com.au and 18 external pages.

Your robots.txt lets ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User) read the homepage but closes other sections to them, so answers about those pages can't cite you.

https://mayfieldlighting.com.au/pages/collections and https://mayfieldlighting.com.au/collections all use the title “Collections”. Search engines can't tell which page to show for a search, so each competes with the others.

https://mayfieldlighting.com.au/collections/pendant-lighting, https://mayfieldlighting.com.au/pages/collections, https://mayfieldlighting.com.au/pages/autumn-winter-2026, https://mayfieldlighting.com.au/collections/soren-23, https://mayfieldlighting.com.au/collections/brass-edit-23 and https://mayfieldlighting.com.au/collections/marble-edit-22 and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://mayfieldlighting.com.au/collections/all, https://mayfieldlighting.com.au/collections/table-lamps, https://mayfieldlighting.com.au/collections/floor-lamps, https://mayfieldlighting.com.au/collections/desk-lamps, https://mayfieldlighting.com.au/collections/pendant-lighting and https://mayfieldlighting.com.au/collections/lamp-shades and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://mayfieldlighting.com.au/collections/table-lamps, https://mayfieldlighting.com.au/collections/floor-lamps and https://mayfieldlighting.com.au/collections/desk-lamps took over 3 s to send their HTML from our server.

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

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

5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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

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 12 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 19 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.