Website review, no card needed

drbrightenessentials.com logo

drbrightenessentials.com website review

Visit site (opens in a new tab)Reviewed 10 November 202637 issues · 85 checks

This review found 37 issues worth fixing on drbrightenessentials.com, 15 of them high impact, across 85 checks. The most urgent: improve image delivery. 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.6 sMay 23Nov 71.9 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.8 s
May 30, 20261.8 s
Jun 6, 20261.8 s
Jun 13, 20261.9 s
Jun 20, 20261.9 s
Jun 27, 20261.9 s
Jul 4, 20261.9 s
Jul 11, 20261.9 s
Jul 18, 20261.8 s
Jul 25, 20261.8 s
Aug 1, 20261.7 s
Aug 8, 20261.7 s
Aug 15, 20261.8 s
Aug 22, 20261.7 s
Aug 29, 20261.8 s
Sep 5, 20261.9 s
Sep 12, 20261.9 s
Sep 19, 20261.9 s
Sep 26, 20262.0 s
Oct 3, 20261.9 s
Oct 10, 20261.8 s
Oct 17, 20261.9 s
Oct 24, 20261.9 s
Oct 31, 20262.0 s
Nov 7, 20261.9 s
Real-visitor tap response (INP)75th percentile, phones
159 ms104 msMay 23Nov 7146 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026111 ms
May 30, 2026113 ms
Jun 6, 2026116 ms
Jun 13, 2026119 ms
Jun 20, 2026118 ms
Jun 27, 2026120 ms
Jul 4, 2026121 ms
Jul 11, 2026120 ms
Jul 18, 2026121 ms
Jul 25, 2026120 ms
Aug 1, 2026116 ms
Aug 8, 2026118 ms
Aug 15, 2026113 ms
Aug 22, 2026112 ms
Aug 29, 2026110 ms
Sep 5, 2026113 ms
Sep 12, 2026116 ms
Sep 19, 2026125 ms
Sep 26, 2026125 ms
Oct 3, 2026121 ms
Oct 10, 2026129 ms
Oct 17, 2026143 ms
Oct 24, 2026146 ms
Oct 31, 2026153 ms
Nov 7, 2026146 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 drbrightenessentials.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. drbrightenessentials.com at 0.4 s0.4 s
  2. drbrightenessentials.com at 0.8 s0.8 s
  3. drbrightenessentials.com at 1.1 s1.1 s
  4. drbrightenessentials.com at 1.5 s1.5 s
  5. drbrightenessentials.com at 1.9 s1.9 s
  6. drbrightenessentials.com at 2.3 s2.3 s
  7. drbrightenessentials.com at 2.6 s2.6 s
  8. drbrightenessentials.com at 3.0 s3.0 s

Speed

9 to fix64
  • Improve image delivery

    1.6 s · 686 KiB

    28 images could be 686 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.6 s faster on a phone.

  • Main-thread work: 6.3 s

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

  • 3,222 HTML elements

    The page has 3,222 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, Clarity and Facebook and others), adding 1.3 MB and 918 ms of main-thread time.

  • Mobile performance score: 64

    64/100

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

  • Render-blocking requests

    650 ms

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

  • Reduce unused JavaScript

    150 ms · 402 KiB

    About 402 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • Shopify adds 292 ms

    292 ms

    Shopify costs a phone 292 ms of main-thread work and 605 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.

  • Use efficient cache lifetimes

    259 KiB

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

  • Reduce unused CSS

    150 ms · 69 KiB

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

  • 12 long tasks on the main thread

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

  • Legacy JavaScript

    31 KiB

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

1 checks passed
  • Server response: 8 ms

    8 ms

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

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 10.7 s

    10.7 s

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

  • Time to Interactive: 22.3 s

    22.3 s

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

  • Speed Index: 6.0 s

    6.0 s

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

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

    +33%

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

  • Total Blocking Time: 236 ms

    236 ms

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

  • First Contentful Paint: 1.8 s

    1.8 s

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

  • Largest content (LCP) held steady for real visitors

    +7%

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

7 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.6 s

    1.6 s

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

  • Real-user INP: 141 ms

    141 ms

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

  • Real-user CLS: 0.02

    0.02

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

  • Real-user FCP: 1.1 s

    1.1 s

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

  • Real-user TTFB: 481 ms

    481 ms

    Real visitors wait 481 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

4 to fix52
  • Page weight: 5.0 MB in 457 requests

    5.0 MB

    Your homepage downloads 5.0 MB in 457 requests on a phone: scripts 1.6 MB (186), images 1.5 MB (49) and other files 1,015 KiB (180). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    B-Active_Plus_b180c474-5771-47de-a8ae-4571ff7a1571_1.jpg 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).

  • 10 images in older formats

    10 images (732 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.

  • 8 images below the first screen load straight away

    8 images further down the page (564 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.4 g of CO₂ per visit

    1.42 g

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

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

10 to fixGoogle 7586
  • ARIA attributes must conform to valid values (10 elements)

    ARIA attributes must conform to valid values: 10 elements on the page fail this check, rated critical by axe-core.

  • Certain ARIA roles must contain particular children (2 elements)

    Certain ARIA roles must contain particular children: 2 elements on the page fail this check, rated critical by axe-core.

  • ARIA roles used must conform to valid values (1 element)

    ARIA roles used must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

  • Orphan list items

    Some list items are not inside a list.

  • Hidden but focusable

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

  • 1 tap target too small

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

  • 12 images without alt text

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

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

    All page content should be contained by landmarks: 5 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.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

1 checks passed
  • 51 automated accessibility rules passed

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

SEO

4 to fixGoogle 8576
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is short (23 characters)

    Your title is only 23 characters: “Dr. Brighten Essentials”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is long (174 characters)

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

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

  • 424 internal links, 11 external

    The homepage links to 424 pages on drbrightenessentials.com and 11 external pages.

5 checks passed
  • Canonical URL set

    The canonical URL is https://drbrightenessentials.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://drbrightenessentials.com/sitemap.xml.

AI search readiness

100
4 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: 5 of 6 facts

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

  • Text is in the HTML

    Your server sends the page's text in the HTML (3,526 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

1 to fix95
  • 15 pages without a meta description

    /collections/supplement-kit, /policies/privacy-policy, /policies/terms-of-service, /collections/all, /collections/periods-pms and /collections/stress-energy-sleep and 9 others 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 77 found) and read each the way a search engine does.

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

  • 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 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 7391
  • 1 third-party cookie

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

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Cannot set properties of undefined (setting 'slidesPerView')”.

  • Browser-reported issues

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

2 checks passed
  • Tap targets are thumb-sized

    61 of 68 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

100
  • 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 2,102 words of copy

    The homepage carries about 2,102 words of visible text.

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop our supplement kits →”.

  • 24 calls to action

    The homepage has 24 calls to action, for example “Shop our supplement kits →”, “Shop by concern expand_more” and “Shop all products →”.

  • 11 short forms

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

  • Social proof on the page

    Social proof on the homepage: 45 testimonial or review blocks and 6 customer or partner logos.

  • Analytics in place

    Analytics detected: Google Tag Manager and Microsoft Clarity.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 2 email links.

Privacy and tracking

1 to fix
  • 8 trackers load before any consent

    8

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 3 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.

  • 25 cookies set on arrival

    25

    Opening the homepage sets 25 cookies, 1 of them by other companies (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.

  • 45 other companies contacted

    Loading the homepage contacts 45 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 drbrightenessentials.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 11 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Klaviyo Email Marketing Sms · Microsoft Clarity · Pagefly Ai Page Builder · Stape Remix · Freegifts · rechargecdn.com · nfcube.com · gorgias.chat · snapchat.com · bogos.io · 9gtb.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

CMS
WordPress
Framework
jQuery
E-commerce
Shopify
Analytics
Google Tag Manager | Microsoft Clarity
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 37 issues on drbrightenessentials.com, including 15 speed issues and 4 SEO issues. 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