andaseat.com.au website review

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

8 third-party services load with your homepage (Google Tag Manager, ZenDesk and Google CDN and others), adding 1.9 MB and 1.1 s of main-thread time.

About 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

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

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

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

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

ZenDesk costs a phone 178 ms of main-thread work and 431 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.

Google CDN costs a phone 128 ms of main-thread work and 298 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.

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

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

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

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

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

Your largest element takes 6.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is element render delay (4.6 s).

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

33 images 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 105 ms to 121 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 3.8 MB in 221 requests on a phone: scripts 2.1 MB (86), images 1.3 MB (52) and fonts 244 KiB (9). Under 2 MB keeps phones on slow connections fast.

9 images (3.3 MB) are 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.

3 images are downloaded at several times the size a phone draws them, for example Untitled_1800_x_600_px_1800_x_800_px_1800_x_700_px_1800_x_75 at 1,500 px wide, shown at 390 px. Resized copies would save about 246 KiB.

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

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

1 frame has no title, so screen-reader users cannot tell what it contains.

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

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

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

Your title is only 18 characters: “AndaSeat Australia”. Between 30 and 65 characters leaves room to say what you do and for whom.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

Your meta description is only 18 characters: “AndaSeat Australia”. 70 to 160 characters is enough to sell the click.

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

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

The homepage links to 68 pages on andaseat.com.au and 14 external pages.

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.

https://andaseat.com.au/collections/product-range-catalogue and https://andaseat.com.au/collections/gaming-chairs all use the title “All Gaming Chairs – AndaSeat Australia”. Search engines can't tell which page to show for a search, so each competes with the others.

https://andaseat.com.au/collections/andaseat-gmaing-chairs, https://andaseat.com.au/collections/product-range-catalogue, https://andaseat.com.au/collections/andaseat-gaming-desks, https://andaseat.com.au/pages/about-us-everything-you-need-to-know-about-andaseat, https://andaseat.com.au/pages/andaseat-co-branding-partnership-collaboration and https://andaseat.com.au/pages/reviews-awards-andaseat-products and 5 others use the same meta description. A description written for each page earns more clicks.

https://andaseat.com.au/collections/andaseat-gmaing-chairs, https://andaseat.com.au/collections/product-range-catalogue, https://andaseat.com.au/collections/andaseat-gaming-desks, https://andaseat.com.au/pages/andaseat-co-branding-partnership-collaboration, https://andaseat.com.au/pages/reviews-awards-andaseat-products and https://andaseat.com.au/pages/andaseat-aftercare-guide and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://andaseat.com.au/collections/andaseat-gaming-desks took over 3 s to send its HTML from our server.

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

1 image failed to load on a phone, for example https://andaseat.com.au/Liquid%20error%20(sections/image-and-text%20line%2012):%20invalid%20url%20input.

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

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

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage carries about 2,067 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

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