ellanu.com website review

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

5 images could be 6.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

8 third-party services load with your homepage (alia-prod.com, Shopify and loox.io and others), adding 8.8 MB and 1.2 s of main-thread time.

alia-prod.com costs a phone 500 ms of main-thread work and 6.9 MB 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.

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

About 736 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

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

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

monkcommerce.app costs a phone 115 ms of main-thread work and 545 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 38 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.

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

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

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

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

2 KiB could be saved by minifying CSS.

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

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

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

Real visitors wait 3.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

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

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' largest content (lcp) went from 3.8 s to 3.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 11.2 MB in 514 requests on a phone: images 6.8 MB (15), scripts 2.2 MB (227) and other files 1.2 MB (226). Under 2 MB keeps phones on slow connections fast.

homepage-hero-mobile-slide-image-02-3.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 3.18 g of CO₂e: 381.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

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

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

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

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

Your title is only 15 characters: “Ellanu – EllaNu”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

Your <h1> is empty.

The homepage links to 107 pages on ellanu.com and 5 external pages.

https://ellanu.com/products/membrasin-system and https://ellanu.com/products/membrasin-vitality-pearls-new-intimate-moisture-cream-bundle all use the title “Membrasin® System – EllaNu”. Search engines can't tell which page to show for a search, so each competes with the others.

https://ellanu.com/pages/how-it-works, https://ellanu.com/pages/clinical, https://ellanu.com/pages/our-story, https://ellanu.com/blogs/learning-center and https://ellanu.com/pages/contact have no meta description, so Google writes the search snippet from whatever text it finds.

https://ellanu.com/products/membrasin-system and https://ellanu.com/products/membrasin-vitality-pearls-new-intimate-moisture-cream-bundle use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://ellanu.com/products/membrasin-vitality-pearls-new-intimate-moisture-cream-bundle, whose canonical is https://ellanu.com/products/membrasin-system. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://ellanu.com/collections/intimate-moisture, https://ellanu.com/collections/hormonal-changes, https://ellanu.com/collections/daily-well-being, https://ellanu.com/pages/how-it-works, https://ellanu.com/pages/clinical and https://ellanu.com/pages/our-story and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Authorization will not be covered by the wildcard symbol (*) in CORS `Access-Control-Allow-Headers`…”).

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

4 errors were logged to the browser console while the page loaded, for example “Uncaught (in promise) undefined”.

Chrome logged issues while loading the page (“Cookie”).

Social proof on the homepage: 42 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 6 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 32 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.