Website review, no card needed

blackopalbeauty.com logo

blackopalbeauty.com website review

Visit site (opens in a new tab)Reviewed 16 November 202641 issues · 81 checks

This review found 41 issues worth fixing on blackopalbeauty.com, 16 of them high impact, across 81 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
1.9 s1.6 sMay 30Nov 141.7 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20261.7 s
Jun 6, 20261.8 s
Jun 13, 20261.8 s
Jun 20, 20261.9 s
Jun 27, 20261.8 s
Jul 4, 20261.8 s
Jul 11, 20261.8 s
Jul 18, 20261.7 s
Jul 25, 20261.7 s
Aug 1, 20261.7 s
Aug 8, 20261.7 s
Aug 15, 20261.7 s
Aug 22, 20261.7 s
Aug 29, 20261.8 s
Sep 5, 20261.8 s
Sep 12, 20261.9 s
Sep 19, 20261.8 s
Sep 26, 20261.8 s
Oct 3, 20261.8 s
Oct 10, 20261.8 s
Oct 17, 20261.9 s
Oct 24, 20261.8 s
Oct 31, 20261.7 s
Nov 7, 20261.7 s
Nov 14, 20261.7 s
Real-visitor tap response (INP)75th percentile, phones
195 ms156 msMay 30Nov 14179 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026164 ms
Jun 6, 2026178 ms
Jun 13, 2026171 ms
Jun 20, 2026172 ms
Jun 27, 2026169 ms
Jul 4, 2026162 ms
Jul 11, 2026163 ms
Jul 18, 2026160 ms
Jul 25, 2026163 ms
Aug 1, 2026170 ms
Aug 8, 2026171 ms
Aug 15, 2026173 ms
Aug 22, 2026172 ms
Aug 29, 2026171 ms
Sep 5, 2026178 ms
Sep 12, 2026185 ms
Sep 19, 2026185 ms
Sep 26, 2026190 ms
Oct 3, 2026187 ms
Oct 10, 2026187 ms
Oct 17, 2026187 ms
Oct 24, 2026185 ms
Oct 31, 2026181 ms
Nov 7, 2026185 ms
Nov 14, 2026179 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 blackopalbeauty.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. blackopalbeauty.com at 0.7 s0.7 s
  2. blackopalbeauty.com at 1.5 s1.5 s
  3. blackopalbeauty.com at 2.2 s2.2 s
  4. blackopalbeauty.com at 3.0 s3.0 s
  5. blackopalbeauty.com at 3.7 s3.7 s
  6. blackopalbeauty.com at 4.5 s4.5 s
  7. blackopalbeauty.com at 5.2 s5.2 s
  8. blackopalbeauty.com at 6.0 s6.0 s

Speed

15 to fix44
  • Reduce unused JavaScript

    6.6 s · 1.3 MB

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

  • Use efficient cache lifetimes

    3.3 s · 686 KiB

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

  • Improve image delivery

    1.8 s · 1.0 MB

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

  • Render-blocking requests

    2.5 s

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

  • Mobile performance score: 44

    44/100

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

  • Main-thread work: 4.2 s

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

  • 8 third-party services on the page

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

  • Reduce unused CSS

    730 ms · 135 KiB

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

  • Legacy JavaScript

    300 ms · 79 KiB

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

  • Google Tag Manager adds 322 ms

    322 ms

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

  • rebuyengine.com adds 185 ms

    185 ms

    rebuyengine.com costs a phone 185 ms of main-thread work and 654 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,257 HTML elements

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

  • Klaviyo adds 173 ms

    173 ms

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

  • poweredbyhue.app adds 107 ms

    107 ms

    poweredbyhue.app costs a phone 107 ms of main-thread work and 536 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.

  • LoyaltyLion adds 76 ms

    76 ms

    LoyaltyLion costs a phone 76 ms of main-thread work and 357 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.

  • 16 long tasks on the main thread

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

  • Minify CSS

    160 ms · 11 KiB

    11 KiB could be saved by minifying CSS.

  • Font display

    50 ms

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

  • Minify JavaScript

    17 KiB

    17 KiB could be saved by minifying JavaScript.

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

1 checks passed
  • Server response: 9 ms

    9 ms

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

Core Web Vitals

8 to fix67
  • 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: 25.7 s

    25.7 s

    Your largest element takes 25.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “home page hero banner image”.

  • Time to Interactive: 30.6 s

    30.6 s

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

  • Speed Index: 9.4 s

    9.4 s

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

  • First Contentful Paint: 3.4 s

    3.4 s

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

  • Total Blocking Time: 657 ms

    657 ms

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

  • Real-user CLS: 0.11

    0.11

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

  • 3 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +6%

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

  • Largest content (LCP) held steady for real visitors

    -4%

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

5 checks passed
  • Real-user LCP: 1.7 s

    1.7 s

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

  • Real-user INP: 154 ms

    154 ms

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

  • Real-user FCP: 1.4 s

    1.4 s

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

  • Real-user TTFB: 533 ms

    533 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix33
  • Page weight: 5.8 MB in 317 requests

    5.8 MB

    Your homepage downloads 5.8 MB in 317 requests on a phone: scripts 3.0 MB (140), images 1.5 MB (30) and other files 776 KiB (110). Under 2 MB keeps phones on slow connections fast.

  • About 1.6 g of CO₂ per visit

    1.64 g

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

Accessibility

5 to fixGoogle 8786
  • Delayed refresh under 20 hours must not be used (1 element)

    Delayed refresh under 20 hours must not be used: 1 element on the page fails this check, rated critical by axe-core.

  • 10 images without alt text

    10 images have no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (1 element)

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

  • 2 text elements with low contrast

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

  • Headings should not be empty (1 element)

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

  • Headings skip levels

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

1 checks passed
  • 20 automated accessibility rules passed

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

SEO

4 to fixGoogle 7789
  • No structured data

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

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 2 links crawlers can't follow

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

  • 1 link with vague text

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

  • 104 internal links, 4 external

    The homepage links to 104 pages on blackopalbeauty.com and 4 external pages.

6 checks passed
  • Meta description: 125 characters

    Your meta description is 125 characters: “Explore the finest collection of beauty products and cosmetics for men and women of color with dark skin tones at Black…”.

  • One H1 headline

    Your main headline reads: “Your Cart”.

  • Title: 50 characters

    Your title is a healthy 50 characters: “BLK/OPL: Makeup and Skincare for Melanin Rich Skin”.

  • Canonical URL set

    The canonical URL is https://blackopalbeauty.com/.

  • 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://blackopalbeauty.com/sitemap.xml.

AI search readiness

1 to fix83
  • No Organization structured data

    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.

  • No llms.txt

    There is no https://blackopalbeauty.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

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

Other pages

1 to fix95
  • 2 pages without a meta description

    https://blackopalbeauty.com/collections/all and https://blackopalbeauty.com/pages/returns-exchange have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

    2 pages of 15 loaded without an error (the rest turned automated requests away).

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

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 2 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9289
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 429 ()”.

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix64
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • Thin social proof

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

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

  • Only about 10 words

    The homepage has only about 10 words of visible text; thin pages give Google and first-time buyers little to go on.

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

3 checks passed
  • 22 calls to action

    The homepage has 22 calls to action, for example “SHOP + -”, “SHOP” and “Shop All”.

  • 2 short forms

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

  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

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

  • 2 other companies contacted

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 blackopalbeauty.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 12 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Klaviyo Email Marketing Sms · Rebuy Personalization Engine · Sc Easy 404 Ai Redirects · Swatches Dotify · justuno.com · mlveda.com · widgetic.com · cloudfront.net · doofinder.com · nfcube.com · rebuyengine.com · bazaarvoice.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

Framework
jQuery
E-commerce
Shopify
Analytics
Google Analytics
Hosting
Shopify

Company

Headquarters
Chicago

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 41 issues on blackopalbeauty.com, including 23 speed issues, 4 SEO issues and 4 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