sarasellstrade.com website review

Shopify costs a phone 10.9 s of main-thread work and 627 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

About 512 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.2 s faster on a phone.

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

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

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

8 third-party services load with your homepage (Shopify, Google Tag Manager and Facebook and others), adding 1.5 MB and 11.5 s of main-thread time.

9 long tasks block the main thread while loading, the longest for 10.0 s. During a long task the page ignores taps.

About 190 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.

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

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

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

Facebook costs a phone 257 ms of main-thread work and 297 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,909 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

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

11 KiB could be saved by minifying JavaScript.

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.

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

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

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

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

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

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 3.9 MB in 253 requests on a phone: scripts 1.6 MB (89), images 941 KiB (12) and other files 915 KiB (132). Under 2 MB keeps phones on slow connections fast.

254153-001_ESS_550x.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

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

ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

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 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

No meta description, so Google writes its own snippet from whatever text it finds.

1 link has no real href, so search engines can't follow it.

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

Your <h1> is empty.

The homepage links to 302 pages on sarasellstrade.com and 11 external pages.

Your Organization JSON-LD is missing logo, sameAs (social profiles), 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.

https://sarasellstrade.com/collections/furniture, https://sarasellstrade.com/collections/sofas-sectionals, https://sarasellstrade.com/collections/chairs, https://sarasellstrade.com/collections/cabinets-shelving, https://sarasellstrade.com/collections/consoles-sideboards and https://sarasellstrade.com/collections/coffee-tables and 7 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://sarasellstrade.com/collections/furniture, https://sarasellstrade.com/collections/sofas-sectionals, https://sarasellstrade.com/collections/chairs, https://sarasellstrade.com/collections/cabinets-shelving, https://sarasellstrade.com/collections/consoles-sideboards and https://sarasellstrade.com/collections/coffee-tables and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

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

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

4 errors were logged to the browser console while the page loaded, for example “Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'register')”.

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach 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 411 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 (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 27 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.