jurlique.com website review

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

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

8 third-party services load with your homepage (Attentive, Shopify and Klaviyo and others), adding 1.3 MB and 923 ms of main-thread time.

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

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

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

About 633 KiB of JavaScript is downloaded but never used on this page.

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

rechargecdn.com costs a phone 84 ms of main-thread work and 298 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.

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

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

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

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

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

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

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

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

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

Real visitors wait 891 ms for your server to start answering (75th percentile). Good is under 800 ms.

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

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

Your homepage downloads 4.8 MB in 419 requests on a phone: scripts 1.7 MB (174), images 1.6 MB (51) and other files 914 KiB (140). Under 2 MB keeps phones on slow connections fast.

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

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

Scrollable region must have keyboard access: 6 elements on the page fail this check, rated serious by axe-core.

Elements must only use permitted ARIA attributes: 2 elements on the page fail this check, rated serious by axe-core.

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

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

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

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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

Elements with visible text labels do not have matching accessible names. (1 element).

There are 2 <h1> headlines (“” and “”). One clear main headline is easier for people and search engines.

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

Structured data found (Organization and WebSite) but with 2 problems, for example “Organization: sameAs is not an absolute URL ("#")”.

4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 206 pages on jurlique.com and 10 external pages.

https://jurlique.com/collections/all, https://jurlique.com/collections/aroma-accessories and https://jurlique.com/collections/discovery-sets have no meta description, so Google writes the search snippet from whatever text it finds.

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

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

5 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://jurlique.com/cdn/shop/t/80/assets/section-collection-grid.css?v=9187' because its …”.

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

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