escentric.com website review

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

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

About 524 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 620 ms faster on a phone.

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

8 third-party services load with your homepage (ZenDesk, Clarity and Klaviyo and others), adding 1.5 MB and 849 ms of main-thread time.

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

ZenDesk costs a phone 263 ms of main-thread work and 478 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 119 ms of main-thread work and 496 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.

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

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

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

86 KiB could be saved by minifying JavaScript.

3 long tasks block the main thread while loading, the longest for 63 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).

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

5 KiB JavaScript is shipped twice across bundles.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

4 KiB could be saved by minifying CSS.

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

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

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

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

8 images have no width and height attributes, so the layout jumps as each one loads.

Your homepage downloads 7.4 MB in 513 requests on a phone: media 3.6 MB (3), scripts 1.6 MB (140) and other files 1.4 MB (276). Under 2 MB keeps phones on slow connections fast.

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

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

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

All page content should be contained by landmarks: 5 elements on the page fail this check, rated moderate by axe-core.

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

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

Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.

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

Your title is 66 characters, so Google will cut it off around 60: “Escentric Molecules | Official Site - Luxury Fragrances & Bodycare”.

Your <h1> is empty.

The homepage links to 249 pages on escentric.com and 4 external pages.

/en-us/pages/newsletter, /en-us/products/cologne-one, /en-us/products/molecule-8-5ml-discovery-set and /en-us/products/escentric-8-5ml-discovery-set have no <h1> headline, so visitors and search engines get no clear main topic.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

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

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

Opening https://escentric.com goes through 2 redirects before the homepage loads.

1 link go through two or more redirects, for example https://www.escentric.com/checkout.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

escentric.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust 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 728 words of visible text.

DMARC is set to p=none, so mail pretending to be escentric.com is still delivered. Reports are on, so moving to quarantine is the next step.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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

Opening the homepage sets 19 cookies (measured from a US location before any click).

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