redheadrevolution.us website review

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

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

8 third-party services load with your homepage (Klaviyo, Shopify and Yotpo and others), adding 1.4 MB and 430 ms of main-thread time.

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

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

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

Shopify costs a phone 136 ms of main-thread work and 744 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,929 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

Klaviyo costs a phone 158 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.

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

7 KiB could be saved by minifying JavaScript.

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

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

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

3 KiB JavaScript is shipped twice across bundles.

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

Your largest element takes 5.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “A group of redheads laughing together”.

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

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

Your homepage downloads 3.4 MB in 310 requests on a phone: images 1.1 MB (26), scripts 1.1 MB (110) and other files 882 KiB (139). Under 2 MB keeps phones on slow connections fast.

Pink_Checkered_Pouch_and_Makeup_Tubes.png 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).

1 image is downloaded at several times the size a phone draws it, for example 1eevP_JRqsoetRqWVXtYeLmiFhYkDvkbN_w1600.jpg at 1,600 px wide, shown at 390 px. Resized copies would save about 77 KiB.

2 images (448 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 0.97 g of CO₂e: 116.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

1 tap target is too small or too close together to hit reliably with a finger.

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

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

19 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

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

Your title is 69 characters, so Google will cut it off around 60: “Makeup for Redheads: Mascara, Brow Gel & Lip Color Redhead Revolution”.

There are 2 <h1> headlines (“” and “Your red has range. So does our makeup.”). One clear main headline is easier for people and search engines.

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

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 111 pages on redheadrevolution.us and 8 external pages.

https://redheadrevolution.com/blogs/tutorials/shade-comparison-with-maddie 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://redheadrevolution.com/blogs/tutorials/shade-comparison-with-maddie all use the title “Makeup for Redheads: Mascara, Brow Gel & Lip Color Redhead Revolution”. Search engines can't tell which page to show for a search, so each competes with the others.

https://redheadrevolution.com/pages/rewards, https://redheadrevolution.com/collections/all and https://redheadrevolution.com/pages/about-us have no meta description, so Google writes the search snippet from whatever text it finds.

https://redheadrevolution.com/pages/rewards and https://redheadrevolution.com/pages/faq have no <h1> headline, so visitors and search engines get no clear main topic.

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

Social proof on the homepage: 49 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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.

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