myellora.com website review

8 third-party services load with your homepage (alia-prod.com, heatmap.com and 506.io and others), adding 8.8 MB and 657 ms of main-thread time.

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

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

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

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

alia-prod.com costs a phone 410 ms of main-thread work and 293 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 278 KiB of JavaScript is downloaded but never used on this page.

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

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

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

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

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

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

For real visitors the layout shifts by 0.44 (75th percentile). Good is under 0.1.

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

The layout shifts by 0.458 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

The first text or image appears after 1.9 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-10-31, real Chrome visitors' tap response (inp) went from 157 ms to 152 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 10.3 MB in 251 requests on a phone: media 6.6 MB (5), images 1.7 MB (44) and other files 852 KiB (126). Under 2 MB keeps phones on slow connections fast.

hf_20260924_163714_b1841c70-64c7-4d3d-957b-85ea558ecfff.png 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).

1 image is downloaded at several times the size a phone draws it, for example hf_20260924_163714_b1841c70-64c7-4d3d-957b-85ea558ecfff.png at 2,048 px wide, shown at 390 px. Resized copies would save about 85 KiB.

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

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

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

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

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

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

Elements with visible text labels do not have matching accessible names. (1 element).

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 6 characters: “Ellora”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 2 <h1> headlines (“Ellora” and “Kill first. Flush second. Ancient Tradition in a …”). One clear main headline is easier for people and search engines.

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

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

The homepage links to 38 pages on myellora.com and 2 external pages.

Your Organization JSON-LD is missing logo, description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

https://www.myellora.com/collections/ellora-products, https://www.myellora.com/products/ellora-cleanse, https://www.myellora.com/products/ellora-binder-cleanse, https://www.myellora.com/products/ellora-zeolite-binder, https://www.myellora.com/products/ellora-candida-cleanse and https://www.myellora.com/products/ellora-liver-detox and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.myellora.com/apps/parcelpanel, https://www.myellora.com/products/ellora-cleanse, https://www.myellora.com/products/ellora-binder-cleanse, https://www.myellora.com/products/ellora-zeolite-binder and https://www.myellora.com/pages/contact have no <h1> headline, so visitors and search engines get no clear main topic.

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

4 errors were logged to the browser console while the page loaded, for example “Unexpected token ','”.

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

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

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

The homepage carries about 908 words of visible text.

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