jurlique.hk website review

103 files are served with short cache lifetimes, so returning visitors download them again (37.5 MB).

31 images could be 31.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.3 s faster on a phone.

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

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

211 KiB could be saved by minifying JavaScript.

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

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

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

2 third-party services load with your homepage (Google Tag Manager and Google Analytics), adding 166 KiB and 120 ms of main-thread time.

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

11 KiB could be saved by minifying CSS.

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.

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

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

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

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

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

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 0.7 s to 0.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 37.7 MB in 107 requests on a phone: images 36.7 MB (60), scripts 819 KiB (22) and stylesheets 119 KiB (21). Under 2 MB keeps phones on slow connections fast.

11 images weigh 31.4 MB together. On a phone connection a single image that size takes seconds.

2 images are downloaded at several times the size a phone draws them, for example Homepage-Banner-2.jpg at 4,320 px wide, shown at 1,284 px. Resized copies would save about 2.4 MB.

20 images (32.0 MB) 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.

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

1 element use ARIA attributes their role does not allow, which confuses screen readers.

12 tap targets are too small or too close together to hit reliably with a finger.

Some lists contain elements other than list items, which screen readers announce wrongly.

Some list items are not inside a list.

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

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

Structured data found (BreadcrumbList, WebPage and WebSite) but with 2 problems, for example “WebPage: url is not an absolute URL ("/")”.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

There is no robots.txt at jurlique.hk/robots.txt, the first file search crawlers ask for.

4 links have no real href, so search engines can't follow them.

Your hreflang tags are invalid, so Google may show the wrong language version.

The homepage links to 117 pages on jurlique.hk and 14 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

There is no https://www.jurlique.hk/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://www.jurlique.hk/product-types/cleansers-and-exfoliators, https://www.jurlique.hk/product-types/mists-and-essences, https://www.jurlique.hk/product-types/face-oils, https://www.jurlique.hk/product-types/serums, https://www.jurlique.hk/product-types/moisturisers and https://www.jurlique.hk/product-types/masks and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.jurlique.hk/face, https://www.jurlique.hk/product-types/cleansers-and-exfoliators, https://www.jurlique.hk/product-types/mists-and-essences, https://www.jurlique.hk/product-types/face-oils, https://www.jurlique.hk/product-types/serums and https://www.jurlique.hk/product-types/moisturisers and 8 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

https://www.jurlique.hk/stores, https://www.jurlique.hk/product-types/cleansers-and-exfoliators, https://www.jurlique.hk/product-types/face-oils, https://www.jurlique.hk/product-types/serums, https://www.jurlique.hk/product-types/moisturisers and https://www.jurlique.hk/product-types/masks and 4 others took over 3 s to send their HTML from our server.

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

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

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

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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 19 words of visible text; thin pages give Google and first-time buyers little to go on.

There is no form on the homepage, so every lead has to click through to another page first.

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 Analytics and Google Tag Manager (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 3 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 2 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.