sohaliving.com website review

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

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

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

28 images could be 2.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 550 ms faster on a phone.

8 third-party services load with your homepage (tabarn.app, aitrillion.com and Accessibe Accessibility Overlay and others), adding 2.6 MB and 1.5 s of main-thread time.

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

18 files are served with short cache lifetimes, so returning visitors download them again (1.3 MB).

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

tabarn.app costs a phone 574 ms of main-thread work and 130 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.

aitrillion.com costs a phone 419 ms of main-thread work and 1.2 MB 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.

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

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

tidio.co costs a phone 81 ms of main-thread work and 515 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.

Shopify costs a phone 90 ms of main-thread work and 351 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.

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

15 KiB could be saved by minifying JavaScript.

Polyfills for old browsers add 14 KiB JavaScript that modern phones do not need.

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

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

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

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

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

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

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 97 ms to 98 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 12.2 MB in 360 requests on a phone: images 7.6 MB (93), scripts 2.6 MB (80) and other files 1.0 MB (155). Under 2 MB keeps phones on slow connections fast.

14 images weigh 10.6 MB together. On a phone connection a single image that size takes seconds.

39 images (16.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.

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

4 buttons have no accessible name, so screen readers announce just “button”.

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

1 tap target is too small or too close together to hit reliably with a finger.

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

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

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

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

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

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

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

There are 4 <h1> headlines (“”, “The Christmas Shop” and “Shop the Look”). One clear main headline is easier for people and search engines.

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

The homepage links to 535 pages on sohaliving.com and 36 external pages.

https://www.sohaliving.com/collections/christmas-collection, https://www.sohaliving.com/pages/wish-list, https://www.sohaliving.com/pages/shop-by-print, https://www.sohaliving.com/collections/new-arrivals and https://www.sohaliving.com/collections/pillows-and-blankets have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.sohaliving.com/collections/christmas-collection, https://www.sohaliving.com/pages/soha-keiki, https://www.sohaliving.com/collections/home-and-living, https://www.sohaliving.com/collections/accessories, https://www.sohaliving.com/collections/stationery and https://www.sohaliving.com/collections/gourmet-and-sweets and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

4 errors were logged to the browser console while the page loaded, for example “button is not defined”.

Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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

Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager, Meta Pixel 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, 1 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 38 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.