tryrevitalglow.com website review

8 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.2 s.

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

8 third-party services load with your homepage (Clarity, Shopify and Klaviyo and others), adding 957 KiB and 815 ms of main-thread time.

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

Clarity costs a phone 344 ms of main-thread work and 29 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.

azurefd.net costs a phone 86 ms of main-thread work and 331 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.

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

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

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

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

42 KiB JavaScript is shipped twice across bundles.

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

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

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

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 5.3 MB in 145 requests on a phone: media 3.9 MB (2), scripts 1,017 KiB (88) and images 202 KiB (10). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example revitalglow-b02-r3-01-hero.png at 1,024 px wide, shown at 268 px. Resized copies would save about 22 KiB.

1 image further down the page (56 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

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

1 image has no alt text, which hurts accessibility and image search.

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

1 visible link has no text or label, so screen readers cannot say where it goes.

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

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

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

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

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 2 <h1> headlines (“RevitalGlow” and “RevitalGlow Red Cell Builder Drops”). 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.

The homepage links to 30 pages on tryrevitalglow.com and 0 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

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

https://tryrevitalglow.com/a/loop_subscriptions/get-subscription-link is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/ and https://tryrevitalglow.com/a/loop_subscriptions/get-subscription-link all use the title “RevitalGlow”. Search engines can't tell which page to show for a search, so each competes with the others.

https://tryrevitalglow.com/pages/contact-us, https://tryrevitalglow.com/a/loop_subscriptions/get-subscription-link, https://tryrevitalglow.com/pages/about-us-1, https://tryrevitalglow.com/pages/contact, https://tryrevitalglow.com/policies/shipping-policy and https://tryrevitalglow.com/policies/refund-policy and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://tryrevitalglow.com/a/loop_subscriptions/get-subscription-link, https://tryrevitalglow.com/pages/about-us-1 and https://tryrevitalglow.com/pages/contact have no <h1> headline, so visitors and search engines get no clear main topic.

https://tryrevitalglow.com/products/revitalglow-red-cell-builder-drops, https://tryrevitalglow.com/pages/contact-us, https://tryrevitalglow.com/a/loop_subscriptions/get-subscription-link, https://tryrevitalglow.com/blogs/revitalglow-blog, https://tryrevitalglow.com/blogs/revitalglow-blog/high-mcv-meaning and https://tryrevitalglow.com/blogs/revitalglow-blog/what-is-methylfolate and 1 other took over 3 s to send their HTML from our server.

We fetched 14 pages linked from your homepage and read each the way a search engine does.

3 of 7 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

3 errors were logged to the browser console while the page loaded, for example “Invalid left-hand side in assignment”.

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.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

The homepage carries about 1,050 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 14 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 31 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.