jeuneora-sg.com website review

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

15 images could be 648 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.

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

Klaviyo costs a phone 109 ms of main-thread work and 334 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 third-party services load with your homepage (Klaviyo, Clarity and Google Tag Manager and others), adding 853 KiB and 418 ms of main-thread time.

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

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

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

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

Polyfills for old browsers add 29 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.

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

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

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

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

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

Your homepage downloads 5.3 MB in 215 requests on a phone: media 2.3 MB (2), images 1.0 MB (33) and scripts 911 KiB (79). Under 2 MB keeps phones on slow connections fast.

4 images are downloaded at several times the size a phone draws them, for example ElevenLabs_image_gpt-image-2_use_the_refe..._2026-05-12T03_4 at 800 px wide, shown at 130 px. Resized copies would save about 390 KiB.

4 images (329 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 further down the page (101 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 1.50 g of CO₂e: 179.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

3 buttons have no accessible name, so screen readers announce just “button”.

1 dropdown has no label.

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

2 elements hidden from screen readers can still receive keyboard focus.

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

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

There are 2 <h1> headlines (“The home of women's wellbeing.” and “Science-backed skincare and supplements, designed…”). One clear main headline is easier for people and search engines.

Structured data found (Article, OnlineStore and WebSite) but with 1 problem, for example “Article: image is not an absolute URL ("//jeuneora.co.nz/cdn/shop/articles/creatine-for-women-over-…”.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 85 pages on jeuneora-sg.com and 9 external pages.

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

1 image failed to load on a phone, for example https://jeuneora.co.nz/?shpxid=fa58f925-beba-48cf-8d45-e82fd5a14677.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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 630 words of visible text.

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