andaseat.my website review

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

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

6 images could be 821 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 850 ms faster on a phone.

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

About 1.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 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 854 ms of main-thread work and 676 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.

ZenDesk costs a phone 309 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.

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

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

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

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

35 KiB could be saved by minifying JavaScript.

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

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

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

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

Your largest element takes 7.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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 4.9 MB in 255 requests on a phone: images 2.3 MB (52), scripts 1.6 MB (61) and other files 669 KiB (96). Under 2 MB keeps phones on slow connections fast.

6 images (1.7 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 novis_banner_mobile.webp at 1,500 px wide, shown at 390 px. Resized copies would save about 326 KiB.

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

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

1 link inside paragraphs relies on colour alone to stand out.

17 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.

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

Headings should not be empty: 5 elements on the page fail this check, rated minor by axe-core.

Your title is 87 characters, so Google will cut it off around 60: “Top Gaming Chair Brand for Ultimate Comfort and Style | AndaSeat MY – AndaSeat Malaysia”.

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

Your meta description is 252 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 46 pages on andaseat.my and 23 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.

Your homepage links to https://andaseat.my/collections/promotions and https://andaseat.my/pages/andaseat-top-esports-edition-gaming-chair, which answer with an error. Visitors hit a dead end and search engines drop them.

https://andaseat.my/products/andaseat-kaiser-3-series-premium-gaming-chair and https://andaseat.my/products/phantom-3-series-premium-office-gaming-chair are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://andaseat.my/blogs/news, https://andaseat.my/pages/andaseat-corporate-social-responsibility, https://andaseat.my/pages/andaseat-resource-library, https://andaseat.my/pages/ip-list and https://andaseat.my/collections/chairs use the same meta description. A description written for each page earns more clicks.

https://andaseat.my/blogs/news, https://andaseat.my/pages/regions, https://andaseat.my/pages/ip-list and https://andaseat.my/collections/chairs have no <h1> headline, so visitors and search engines get no clear main topic.

https://andaseat.my/pages/andaseat-aftercare-guide, https://andaseat.my/pages/andaseat-resource-library and https://andaseat.my/pages/shipping-delivery-policy took over 3 s to send their HTML from our server.

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

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

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: 2 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

The homepage carries about 1,440 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 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 14 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 26 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.