xchair.com website review

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

8 third-party services load with your homepage (Google Tag Manager, Klevu Search and Facebook and others), adding 2.3 MB and 1.6 s of main-thread time.

About 1.1 MB of JavaScript is downloaded but never used on this page.

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

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

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

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

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

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

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

Ada costs a phone 91 ms of main-thread work and 527 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.

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

113 KiB could be saved by minifying JavaScript.

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

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.

1 image could be 5 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

4 KiB could be saved by minifying CSS.

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

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

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

Visually, the page fills in at 3.9 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 137 ms to 146 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 2.1 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 4.2 MB in 362 requests on a phone: scripts 2.7 MB (105), other files 1,023 KiB (203) and HTML 198 KiB (6). Under 2 MB keeps phones on slow connections fast.

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

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

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

1 visible link has no text or label, so screen readers cannot say where it goes.

ARIA role should be appropriate for the element: 6 elements on the page fail this check, rated minor by axe-core.

Alternative text of images should not be repeated as text: 3 elements on the page fail this check, rated minor by axe-core.

Your title is 66 characters, so Google will cut it off around 60: “Shop X-Chair Office Chairs and Accessories | X-Chair Official Site”.

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

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

2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 125 pages on xchair.com and 16 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://www.xchair.com/collections/executive-management-office-chairs, https://www.xchair.com/collections/task-guest-chairs, https://www.xchair.com/collections/leather-vegan-leather-office-chairs, https://www.xchair.com/collections/mesh-office-chairs and https://www.xchair.com/collections/massage-heat-office-chairs have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.xchair.com/collections/all, https://www.xchair.com/collections/office-chairs, https://www.xchair.com/products/xtech-ultimate-executive-office-chair, https://www.xchair.com/products/x4-leather-executive-office-chair, https://www.xchair.com/products/x3-atr-management-office-chair and https://www.xchair.com/products/x2-ksport-mesh-management-office-chair and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.xchair.com/collections/leather-vegan-leather-office-chairs, https://www.xchair.com/collections/refurbished and https://www.xchair.com/collections/tables-desks have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=5565013&tm=gtm002&Ver=2&mid=e57bbb3b-558e-430e-a3f6-cbde78d00c88&bo=1&sid=4845e970dd7e11f191e0cf3fefe8813b&vid=4845f340dd7e11f1be7d4569d3db8cd4&vids=1&msclkid=N&pi=918.

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

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

Large scripts ship without source maps.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

Before a visitor clicks anything, the page loads Amazon Ads, Google Ads, Google Analytics, Google Tag Manager and Klaviyo and 4 mores (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 27 cookies, 1 of them by other companies (measured from a US location before any click).

Loading the homepage contacts 57 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.