Website review, no card needed

revolutionbeauty.com logo

revolutionbeauty.com website review

Visit site (opens in a new tab)Reviewed 18 November 202638 issues · 87 checks

This review found 38 issues worth fixing on revolutionbeauty.com, 14 of them high impact, across 87 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
2.0 s1.7 sMay 30Nov 141.8 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20261.9 s
Jun 6, 20261.9 s
Jun 13, 20261.9 s
Jun 20, 20262.0 s
Jun 27, 20262.0 s
Jul 4, 20262.0 s
Jul 11, 20262.0 s
Jul 18, 20262.0 s
Jul 25, 20262.0 s
Aug 1, 20262.0 s
Aug 8, 20262.0 s
Aug 15, 20262.0 s
Aug 22, 20262.0 s
Aug 29, 20261.9 s
Sep 5, 20261.9 s
Sep 12, 20261.9 s
Sep 19, 20261.9 s
Sep 26, 20261.8 s
Oct 3, 20261.8 s
Oct 10, 20261.8 s
Oct 17, 20261.9 s
Oct 24, 20261.9 s
Oct 31, 20261.8 s
Nov 7, 20261.8 s
Nov 14, 20261.8 s
Real-visitor tap response (INP)75th percentile, phones
371 ms146 msMay 30Nov 14238 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026172 ms
Jun 6, 2026175 ms
Jun 13, 2026181 ms
Jun 20, 2026188 ms
Jun 27, 2026194 ms
Jul 4, 2026196 ms
Jul 11, 2026203 ms
Jul 18, 2026212 ms
Jul 25, 2026241 ms
Aug 1, 2026285 ms
Aug 8, 2026323 ms
Aug 15, 2026345 ms
Aug 22, 2026328 ms
Aug 29, 2026308 ms
Sep 5, 2026287 ms
Sep 12, 2026267 ms
Sep 19, 2026262 ms
Sep 26, 2026259 ms
Oct 3, 2026259 ms
Oct 10, 2026257 ms
Oct 17, 2026259 ms
Oct 24, 2026255 ms
Oct 31, 2026252 ms
Nov 7, 2026249 ms
Nov 14, 2026238 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of revolutionbeauty.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. revolutionbeauty.com at 0.7 s0.7 s
  2. revolutionbeauty.com at 1.4 s1.4 s
  3. revolutionbeauty.com at 2.1 s2.1 s
  4. revolutionbeauty.com at 2.8 s2.8 s
  5. revolutionbeauty.com at 3.5 s3.5 s
  6. revolutionbeauty.com at 4.2 s4.2 s
  7. revolutionbeauty.com at 4.9 s4.9 s
  8. revolutionbeauty.com at 5.6 s5.6 s

Speed

12 to fix61
  • Reduce unused JavaScript

    2.7 s · 620 KiB

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

  • Use efficient cache lifetimes

    2.2 s · 621 KiB

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

  • Main-thread work: 7.3 s

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

  • 3,725 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, Noibu and notify-me.io and others), adding 9.2 MB and 806 ms of main-thread time.

  • Mobile performance score: 61

    61/100

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

  • videowise.com adds 97 ms

    97 ms

    videowise.com costs a phone 97 ms of main-thread work and 7.6 MB 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.

  • Reduce unused CSS

    600 ms · 120 KiB

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

  • Render-blocking requests

    700 ms

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

  • Improve image delivery

    200 ms · 323 KiB

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

  • Shopify adds 160 ms

    160 ms

    Shopify costs a phone 160 ms of main-thread work and 476 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 adds 106 ms

    106 ms

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

  • 10 long tasks on the main thread

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

  • Font display

    50 ms

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

  • Legacy JavaScript

    19 KiB

    Polyfills for old browsers add 19 KiB JavaScript that modern phones do not need.

  • Chained critical requests

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

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

  • Minify JavaScript

    4 KiB

    4 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 91 ms

    91 ms

    Your server sent the HTML in 91 ms, well inside Google's 600 ms guideline.

Core Web Vitals

9 to fix33
  • Fails Core Web Vitals for real visitors

    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.

  • Largest Contentful Paint: 17.1 s

    17.1 s

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

  • Time to Interactive: 25.5 s

    25.5 s

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

  • Speed Index: 8.1 s

    8.1 s

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

  • Real-user LCP: 3.2 s

    3.2 s

    Real visitors wait 3.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 320 ms

    320 ms

    Real visitors wait 320 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Tap response (INP) got 40% slower for real visitors

    +40%

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

  • Total Blocking Time: 273 ms

    273 ms

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

  • 1 image without width and height

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

  • Largest content (LCP) held steady for real visitors

    -6%

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

5 checks passed
  • Real-user CLS: 0.04

    0.04

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

  • Real-user FCP: 1.6 s

    1.6 s

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

  • Real-user TTFB: 682 ms

    682 ms

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

  • First Contentful Paint: 1.7 s

    1.7 s

    The first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0.001

    0.001

    The layout barely moves while loading (CLS 0.001, good is under 0.1).

Images and page weight

2 to fix60
  • Page weight: 13.1 MB in 610 requests

    13.1 MB

    Your homepage downloads 13.1 MB in 610 requests on a phone: media 7.0 MB (3), images 2.1 MB (129) and scripts 1.9 MB (172). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    19 KiB

    1 image is downloaded at several times the size a phone draws it, for example hp-cruelty-free-img-01.gif at 160 px wide, shown at 48 px. Resized copies would save about 19 KiB.

  • 1 image in older formats

    1 image (100 KiB) is 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.

  • About 3.7 g of CO₂ per visit

    3.71 g

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

1 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

6 to fixGoogle 9092
  • 36 text elements with low contrast

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

  • 7 tap targets too small

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

  • Frames without titles

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

  • All page content should be contained by landmarks (8 elements)

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    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.

  • 1 form field without a label

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

  • Headings skip levels

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

  • Elements with visible text labels do not have matching accessible names.

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

2 checks passed
  • Every image has alt text

    All 206 images in the HTML carry an alt attribute.

  • 52 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 57 WCAG 2.2 A/AA and best-practice rules on the phone render: 52 passed and 5 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

Google 100100
  • 499 internal links, 0 external

    The homepage links to 499 pages on revolutionbeauty.com and 0 external pages.

8 checks passed
  • Meta description: 137 characters

    Your meta description is 137 characters: “Explore Revolution Beauty's range of makeup, skincare & haircare — cruelty-free, cutting-edge, and made for every beaut…”.

  • One H1 headline

    Your main headline reads: “Revolution Beauty”.

  • Title: 56 characters

    Your title is a healthy 56 characters: “Revolution Beauty | Cruelty-Free Makeup, Skincare & Hair”.

  • Canonical URL set

    The canonical URL is https://www.revolutionbeauty.com/.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.revolutionbeauty.com/sitemap.xml.

AI search readiness

1 to fix75
  • Most text only appears after JavaScript runs

    14%

    A phone browser shows 596 words, but the HTML your server sends has only 82. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

3 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

  • llms.txt published

    The site publishes https://www.revolutionbeauty.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix90
  • 1 page without a meta description

    https://www.revolutionbeauty.com/collections/most-wanted-sale has no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 pages without an H1

    https://www.revolutionbeauty.com/collections/trending, https://www.revolutionbeauty.com/collections/hair, https://www.revolutionbeauty.com/collections/sale, https://www.revolutionbeauty.com/collections/makeup-sale, https://www.revolutionbeauty.com/collections/skincare-sale and https://www.revolutionbeauty.com/collections/haircare-sale and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 pages with very little text

    https://www.revolutionbeauty.com/collections/trending, https://www.revolutionbeauty.com/collections/hair, https://www.revolutionbeauty.com/collections/sale, https://www.revolutionbeauty.com/collections/makeup-sale, https://www.revolutionbeauty.com/collections/skincare-sale and https://www.revolutionbeauty.com/collections/haircare-sale and 9 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9678
  • 1 broken image

    1 image failed to load on a phone, for example https://www.revolutionbeauty.com/.

  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “Invalid or unexpected token”.

2 checks passed
  • Tap targets are thumb-sized

    123 of 132 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix75
  • Thin social proof

    Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

  • About 596 words of copy

    The homepage carries about 596 words of visible text.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP NOW”.

  • 56 calls to action

    The homepage has 56 calls to action, for example “Shop now”, “shop now” and “Shop All New In”.

  • 67 short forms

    67 short forms (1 field at most) are right on the homepage.

Privacy and tracking

1 to fix
  • 7 trackers load before any consent

    7

    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.

  • 23 cookies set on arrival

    23

    Opening the homepage sets 23 cookies (measured from a US location before any click).

  • No consent tool detected

    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.

  • 51 other companies contacted

    Loading the homepage contacts 51 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at revolutionbeauty.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 15 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Vex Auto Add To Cart · Starapps Variant Image · Bm Country Blocker Ip Blocker · Videowise Connect · Yotpo Product Reviews · Fast Bundle Upsell · Klaviyo Email Marketing Sms · Google Youtube · Simprosys Google Shopping Feed · Smart Seo · Noibupixel · Boostymark Regionblock · revolutionbeauty.com · trustpilot.com · amazonaws.com

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

E-commerce
Shopify
Hosting
Shopify

Company

Headquarters
Queenborough

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 38 issues on revolutionbeauty.com, including 21 speed issues and 3 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25