stellalife.com website review

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

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

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

8 third-party services load with your homepage (Trust Pilot, stellalife.work and Hubspot and others), adding 798 KiB and 347 ms of main-thread time.

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

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

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 100 ms.

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

19 KiB JavaScript is shipped twice across bundles.

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

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

The page becomes fully interactive after 6.9 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 79 ms to 87 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 2.3 MB in 218 requests on a phone: other files 835 KiB (122), scripts 667 KiB (58) and images 401 KiB (21). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example maxresdefault.webp at 1,280 px wide, shown at 346 px. Resized copies would save about 17 KiB.

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

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

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

Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

1 tap target is too small or too close together to hit reliably with a finger.

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

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

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

Your title is 70 characters, so Google will cut it off around 60: “VEGA Oral Recovery Care: Dental Healing Spray, Gel, Rinse - StellaLife”.

6 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

Open Graph is missing og:title and og:description, so shared links fall back to guesses.

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

The homepage links to 229 pages on stellalife.com and 55 external pages.

https://stellalife.com/pages/bundles is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://stellalife.com/products/stellalife-vega-oral-care-vanilla-mint-kit, https://stellalife.com/products/stellalife-vega-oral-care-coconut-recovery-kit and https://stellalife.com/products/stellalife-vega-oral-care-recovery-kit-16oz all use the title “VEGA Recovery Kit - Dry Mouth Socket Lichen Planus Dental StellaLife”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://stellalife.com/blogs/in-the-news, https://stellalife.com/products, https://stellalife.com/pages/bundles, https://stellalife.com/collections/category-recovery-kit, https://stellalife.com/collections/category-oral-gels and https://stellalife.com/collections/category-pre-post-probiotics 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://stellalife.com/products, whose canonical is https://stellalife.com/collections. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://stellalife.com/products and https://stellalife.com/collections/category-recovery-kit have no <h1> headline, so visitors and search engines get no clear main topic.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

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

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://static.mailerlite.com/css/universal.css?v4' from origin 'https://stellalife.com' h…”.

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

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.

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

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and LinkedIn Insight and 2 mores (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 27 cookies, 8 of them by other companies (measured from a US location before any click).

Loading the homepage contacts 36 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.