tryrosabella.com website review

About 890 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.9 s faster on a phone.

Your mobile performance score is 23. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

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

8 third-party services load with your homepage (alia-prod.com, Google Tag Manager and trackcollect.com and others), adding 1.9 MB and 1.8 s of main-thread time.

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

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

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

Google Tag Manager costs a phone 385 ms of main-thread work and 359 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.

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

trackcollect.com costs a phone 283 ms of main-thread work and 128 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.

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

cloudfront.net costs a phone 126 ms of main-thread work and 387 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.

39 KiB could be saved by minifying JavaScript.

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

Polyfills for old browsers add 78 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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

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.

Your largest element takes 17.5 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 24.9 s. Good is under 3.8 s.

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

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

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

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

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.6 s to 3.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Real visitors see the first content after 2.1 s (75th percentile). Good is under 1.8 s.

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

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

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

Your homepage downloads 4.7 MB in 397 requests on a phone: scripts 2.4 MB (166), images 1.0 MB (42) and other files 984 KiB (146). Under 2 MB keeps phones on slow connections fast.

2 images weigh 1.2 MB together. On a phone connection a single image that size takes seconds.

4 images are downloaded at several times the size a phone draws them, for example gummies_1.webp at 800 px wide, shown at 152 px. Resized copies would save about 670 KiB.

8 images (2.6 MB) 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.

img-banner.webp 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).

2 images further down the page (337 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

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

1 frame has no title, so screen-reader users cannot tell what it contains.

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

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

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

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

Elements with visible text labels do not have matching accessible names. (6 elements).

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

The homepage links to 67 pages on tryrosabella.com and 13 external pages.

https://tryrosabella.com/products/rosabella-moringa-gummies-sub is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://tryrosabella.com/policies/shipping-policy and https://tryrosabella.com/policies/refund-policy have no meta description, so Google writes the search snippet from whatever text it finds.

https://tryrosabella.com/products/rosabella-electrolyte-drink-powder-b1 and https://tryrosabella.com/apps/trackyourorder have no <h1> headline, so visitors and search engines get no clear main topic.

https://tryrosabella.com/pages/beetroot, https://tryrosabella.com/products/rosabella-moringa-gummies-sub, https://tryrosabella.com/apps/trackyourorder, https://tryrosabella.com/policies/shipping-policy and https://tryrosabella.com/policies/refund-policy took over 3 s to send their HTML from our server.

We fetched 15 pages linked from your homepage (of 27 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 '&'”.

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

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