hyluniapro.com website review

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

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

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

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

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

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

Shopify costs a phone 91 ms of main-thread work and 563 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 101 ms of main-thread work and 309 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.

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

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

7 images could be 151 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

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

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 2.7 MB in 194 requests on a phone: scripts 1.1 MB (88), other files 656 KiB (74) and images 651 KiB (15). Under 2 MB keeps phones on slow connections fast.

Hero-04_1.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

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

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

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

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

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

1 visible link has no text or label, so screen readers cannot say where it goes.

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

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

Your page has no <title>, so Google has to invent the blue link in search results.

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

Your <h1> is empty.

The homepage links to 142 pages on hyluniapro.com and 7 external pages.

https://hyluniapro.com/collections/products, https://hyluniapro.com/collections/hymed-products, https://hyluniapro.com/pages/special-offer, https://hyluniapro.com/blogs/blog, https://hyluniapro.com/pages/story-of-our-birth and https://hyluniapro.com/pages/founding-team and 9 others have no <title>, so Google invents the link text in results.

https://hyluniapro.com/collections/products, https://hyluniapro.com/collections/hymed-products, https://hyluniapro.com/collections/hylunia-retail, https://hyluniapro.com/collections/retail-face-care, https://hyluniapro.com/collections/face-care-cleansers and https://hyluniapro.com/collections/face-care-toners and 3 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://hyluniapro.com/collections/products, https://hyluniapro.com/collections/hymed-products, https://hyluniapro.com/pages/special-offer, https://hyluniapro.com/blogs/blog, https://hyluniapro.com/pages/story-of-our-birth and https://hyluniapro.com/pages/webinars and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://hyluniapro.com/collections/products, https://hyluniapro.com/collections/hymed-products, https://hyluniapro.com/pages/special-offer, https://hyluniapro.com/pages/story-of-our-birth, https://hyluniapro.com/pages/founding-team and https://hyluniapro.com/pages/philosophy and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://hyluniapro.com/pages/special-offer and https://hyluniapro.com/pages/philosophy 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.

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

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

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

The homepage shows no opening hours. If customers visit or call, show when.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

Before a visitor clicks anything, the page loads Klaviyo (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 12 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 14 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.