sensitivehome.com website review

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

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

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

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

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

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

8 third-party services load with your homepage (Clarity, Klaviyo and useamp.com and others), adding 1.1 MB and 674 ms of main-thread time.

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

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

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

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

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

5 KiB could be saved by minifying JavaScript.

Your largest element takes 20.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “100% All Natural Made for Sensitive Skin Types A Better Way…”.

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

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

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

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

32 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' largest content (lcp) went from 2.2 s to 2.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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 5.7 MB in 502 requests on a phone: images 2.6 MB (60), other files 1.4 MB (289) and scripts 1.3 MB (107). Under 2 MB keeps phones on slow connections fast.

12 images are downloaded at several times the size a phone draws them, for example BTC-7.jpg at 3,029 px wide, shown at 251 px. Resized copies would save about 1.4 MB.

9 images further down the page (1.3 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

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

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

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

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

Your <h1> is empty.

The homepage links to 49 pages on sensitivehome.com and 6 external pages.

https://www.betterthanclean.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://www.betterthanclean.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.betterthanclean.com/collections/all, https://www.betterthanclean.com/pages/about-us and https://www.betterthanclean.com/customer_authentication/redirect have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.betterthanclean.com/collections/all, https://www.betterthanclean.com/collections/bundles-kits, https://www.betterthanclean.com/collections/concentrate-refills-8oz, https://www.betterthanclean.com/collections/dish-soap, https://www.betterthanclean.com/collections/accessories and https://www.betterthanclean.com/pages/about-us and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

6 images failed to load on a phone, for example https://www.betterthanclean.com/Liquid%20error%20(snippets/header-drawer-new%20line%20106):%20invalid%20url%20input.

6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

3 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

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

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