th.loccitane.com website review

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

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

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

10 images could be 779 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.

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

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

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

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

easychat.co costs a phone 271 ms of main-thread work and 587 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 151 ms of main-thread work and 311 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.

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

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

About 60 KiB of CSS is downloaded but never applied on this page.

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

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

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 18.2 s. Good is under 3.8 s.

Real visitors wait 219 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

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

Your largest element takes 2.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Image banner 2”.

1 image 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 144 ms to 145 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 4.8 MB in 386 requests on a phone: scripts 1.6 MB (107), images 1.5 MB (32) and other files 1.2 MB (194). Under 2 MB keeps phones on slow connections fast.

dfa40dd9-71d0-4078-a6c6-8a3d467169e8.png weighs 567 KiB. On a phone connection a single image that size takes seconds.

3 images (670 KiB) 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.

1 image is downloaded at several times the size a phone draws it, for example dfa40dd9-71d0-4078-a6c6-8a3d467169e8.png at 697 px wide, shown at 160 px. Resized copies would save about 298 KiB.

5 images further down the page (157 KiB) 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.37 g of CO₂e: 164.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 button has no accessible name, so screen readers announce just “button”.

ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

1 frame has no title, so screen-reader users cannot tell what it contains.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

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

Your <h1> is empty.

The homepage links to 361 pages on th.loccitane.com and 7 external pages.

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

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

https://th.loccitane.com/collections/holiday-2026-ornaments and https://th.loccitane.com/collections/holiday-2026-sets all use the title “เซ็ตของขวัญ Holiday 2026 | Advent Calendar – L'Occitane Thailand”. Search engines can't tell which page to show for a search, so each competes with the others.

https://th.loccitane.com/customer_authentication/redirect and https://th.loccitane.com/policies/shipping-policy have no meta description, so Google writes the search snippet from whatever text it finds.

https://th.loccitane.com/pages/holiday and https://th.loccitane.com/collections/holiday-2026-ornaments use the same meta description. A description written for each page earns more clicks.

https://th.loccitane.com/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage (of 168 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.”).

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://maps.develic.com/packs/front.css' from origin 'https://th.loccitane.com' has been …”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

Large scripts ship without source maps.

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

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage has only about 77 words of visible text; thin pages give Google and first-time buyers little to go on.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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