revivserums.com website review

About 1.7 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 6.5 s faster on a phone.

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

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

Signyfyd costs a phone 1.1 s of main-thread work and 283 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

8 third-party services load with your homepage (Signyfyd, Google Tag Manager and Shopify and others), adding 2.9 MB and 2.3 s of main-thread time.

15 images could be 1.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 550 ms faster on a phone.

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

Google Tag Manager costs a phone 321 ms of main-thread work and 515 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 227 ms of main-thread work and 975 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.

Google CDN costs a phone 130 ms of main-thread work and 300 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.

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

cloudfront.net costs a phone 101 ms of main-thread work and 299 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 53 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 250 ms faster on a phone.

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

8 KiB could be saved by minifying JavaScript.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

14 KiB could be saved by minifying CSS.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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 28.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Hero Image”.

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

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

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

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

Real visitors wait 1.1 s for your server to start answering (75th percentile). Good is under 800 ms.

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

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

Your homepage downloads 6.9 MB in 390 requests on a phone: scripts 3.3 MB (133), images 2.0 MB (38) and other files 1.3 MB (186). Under 2 MB keeps phones on slow connections fast.

6 images are downloaded at several times the size a phone draws them, for example RevivHair-REV-Advanced.png at 1,800 px wide, shown at 254 px. Resized copies would save about 970 KiB.

11 images further down the page (1.8 MB) 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.96 g of CO₂e: 235.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

2 buttons have no accessible name, so screen readers announce just “button”.

1 dropdown has no label.

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

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

2 tap targets are too small or too close together to hit reliably with a finger.

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.

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

Your title is 87 characters, so Google will cut it off around 60: “Novel, innovative topical serums for hair | skin | lash | brow | body – RevivSerums.com”.

There are 3 <h1> headlines (“”, “Next-gen serumswith advanced actives” and “RevivHair Max Hair Stimulating Serum with 5% Rede…”). One clear main headline is easier for people and search engines.

Your meta description is 215 characters; Google truncates after about 160, so the end of your pitch is cut.

4 links have no real href, so search engines can't follow them.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 130 pages on revivserums.com and 7 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.

https://www.revivserums.com/products/gift-card declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

/ and https://www.revivserums.com/products/gift-card all use the title “Novel, innovative topical serums for hair | skin | lash | brow | body…”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.revivserums.com/collections/body has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.revivserums.com/collections and https://www.revivserums.com/products/gift-card use the same meta description. A description written for each page earns more clicks.

https://www.revivserums.com/collections/hair-serums, https://www.revivserums.com/collections/facial-serums, https://www.revivserums.com/products/revivlash-lash-brow-stimulating-serum, https://www.revivserums.com/collections/customizable-serums, https://www.revivserums.com/products/revivlip-lip-serum-system and https://www.revivserums.com/collections/body and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=11041676&Ver=2&mid=8bf49dd9-3c16-4d52-8575-bf2d8e512703&bo=2&sid=356fed70dd5411f19726759baee34956&vid=35700fd0dd5411f1a007b556e3485fad&vids=1&msclkid=N&pi=918639831&lg.

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

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

3 errors were logged to the browser console while the page loaded, for example “Expected property name or '}' in JSON at position 4 (line 2 column 3)”.

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

The homepage carries about 698 words of visible text.

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