hellovitaminbee.com website review

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

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

7 images could be 442 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 100 ms faster on a phone.

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

Shopify costs a phone 79 ms of main-thread work and 895 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 244 KiB of JavaScript is downloaded but never used on this page.

3 third-party services load with your homepage (Shopify, Judge.me and shop.app), adding 905 KiB and 79 ms of main-thread time.

1 long task block the main thread while loading, the longest for 53 ms. During a long task the page ignores taps.

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

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

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.

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

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

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

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 307 requests on a phone: other files 1.1 MB (160), scripts 659 KiB (93) and images 566 KiB (7). Under 2 MB keeps phones on slow connections fast.

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

Delayed refresh under 20 hours must not be used: 1 element on the page fails this check, rated critical by axe-core.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is 72 characters, so Google will cut it off around 60: “Organic Elderberry Syrup & Botanical Skincare – Vitamin Bee Wellness Co.”.

The homepage links to 43 pages on hellovitaminbee.com and 13 external pages.

Your homepage links to https://hellovitaminbee.com/collections/346624983197, which answers with an error. Visitors hit a dead end and search engines drop it.

https://hellovitaminbee.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://hellovitaminbee.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://hellovitaminbee.com/collections/subscribe-save, https://hellovitaminbee.com/collections/all and https://hellovitaminbee.com/customer_authentication/redirect have no meta description, so Google writes the search snippet from whatever text it finds.

https://hellovitaminbee.com/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage (of 23 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: the server responded with a status of 429 ()”.

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 has only about 10 words of visible text; thin pages give Google and first-time buyers little to go on.

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 1 host run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.