scentifyhome.com website review

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

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

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

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

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

8 third-party services load with your homepage (Clarity, JSDelivr CDN and rebuyengine.com and others), adding 1.1 MB and 1.1 s of main-thread time.

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

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

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

Clarity costs a phone 360 ms of main-thread work and 30 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.

JSDelivr CDN costs a phone 290 ms of main-thread work and 45 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.

rebuyengine.com costs a phone 165 ms of main-thread work and 672 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.

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

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

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

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.

3 KiB could be saved by minifying JavaScript.

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

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

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

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

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

11 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' tap response (inp) went from 112 ms to 104 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 57.5 MB in 443 requests on a phone: media 52.0 MB (6), images 2.0 MB (51) and other files 1.7 MB (266). Under 2 MB keeps phones on slow connections fast.

2 images are downloaded at several times the size a phone draws them, for example Scentify_Starter_Kit_SOCIAL_4x5_d2c0247a-c838-4d95-b827-2911 at 2,987 px wide, shown at 330 px. Resized copies would save about 513 KiB.

1 image further down the page (399 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

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

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

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

There are 3 <h1> headlines (“<img src="//scentifyhome.com/cdn/shop/files/scent…”, “Bring Iconic Hotel Aromas into Your Home” and “Transform your space with signature scents”). One clear main headline is easier for people and search engines.

The homepage links to 130 pages on scentifyhome.com and 13 external pages.

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

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

https://scentifyhome.com/pages/samples and https://scentifyhome.com/collections/samples all use the title “Samples – Scentify”. Search engines can't tell which page to show for a search, so each competes with the others.

https://scentifyhome.com/collections/diffusers, https://scentifyhome.com/collections/scents, https://scentifyhome.com/collections/reed-diffusers, https://scentifyhome.com/pages/samples, https://scentifyhome.com/customer_authentication/redirect and https://scentifyhome.com/collections/samples have no meta description, so Google writes the search snippet from whatever text it finds.

https://scentifyhome.com/products/scentify-plug-in-diffuser-v2-starter-kit and https://scentifyhome.com/products/scentify-plug-in-diffuser-v2 use the same meta description. A description written for each page earns more clicks.

https://scentifyhome.com/products/scentify-plug-in-diffuser-v2-starter-kit, https://scentifyhome.com/pages/samples and https://scentifyhome.com/customer_authentication/redirect have no <h1> headline, so visitors and search engines get no clear main topic.

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

9 of 39 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”.

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

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