vitalnutritive.com website review

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

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

23 images could be 441 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.0 s faster on a phone.

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

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

8 third-party services load with your homepage (Google Tag Manager, reamaze.com and Klaviyo and others), adding 2.6 MB and 1.3 s of main-thread time.

About 232 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 590 ms faster on a phone.

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

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

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

reamaze.com costs a phone 186 ms of main-thread work and 317 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.

Klaviyo costs a phone 135 ms of main-thread work and 333 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.

thefrontrowhealth.com costs a phone 81 ms of main-thread work and 819 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 108 ms of main-thread work and 436 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.

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

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

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

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

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

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

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

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

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

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

Your homepage downloads 6.2 MB in 613 requests on a phone: scripts 2.1 MB (212), other files 1.4 MB (246) and images 1.3 MB (82). Under 2 MB keeps phones on slow connections fast.

HOME_Mobile_Bundles.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).

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

3 images (483 KiB) 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.

By the Sustainable Web Design model, a visit to your homepage emits about 1.75 g of CO₂e: 209.9 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.

Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

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

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

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

The homepage links to 80 pages on vitalnutritive.com and 0 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), 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://vitalyrahealth.com/collections/all, https://vitalyrahealth.com/pages/subscribe-and-save, https://vitalyrahealth.com/pages/about-us, https://vitalyrahealth.com/pages/contact-us, https://vitalyrahealth.com/collections/best-sellers and https://vitalyrahealth.com/collections/all-bundles and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://vitalyrahealth.com/collections/best-sellers and https://vitalyrahealth.com/collections/all-bundles have no <h1> headline, so visitors and search engines get no clear main topic.

https://vitalyrahealth.com/collections/all, https://vitalyrahealth.com/products/vitalyra-hair-complex, https://vitalyrahealth.com/products/vitalyra-liver-support and https://vitalyrahealth.com/products/vitalyra-super-fruits-veggies took over 3 s to send their HTML from our server.

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

2 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=28484787&Ver=2&mid=fe22cfd2-b6b8-4f95-9f98-f33ce3f0b3ba&bo=1&sid=e6338350ddd511f1a18abf2f80401ef0&vid=e633a7a0ddd511f1b13555152f962fc3&vids=1&msclkid=N&pi=918639831&lg.

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

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_CONNECTION_RESET”.

Your longest form asks for 9 fields (0 required). Every extra field lowers completion.

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 1,122 words of visible text.

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