Website review, no card needed

sugarbearpro.com logo

sugarbearpro.com website review

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

This review found 41 issues worth fixing on sugarbearpro.com, 10 of them high impact, across 87 checks. The most urgent: page weight: 44.8 MB in 218 requests. 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.5 s1.8 sMay 30Nov 141.9 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.4 s
Jun 6, 20262.4 s
Jun 13, 20262.3 s
Jun 20, 20262.3 s
Jun 27, 20262.2 s
Jul 4, 20262.0 s
Jul 11, 20262.0 s
Jul 18, 20261.9 s
Jul 25, 20261.9 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.9 s
Oct 3, 20261.9 s
Oct 10, 20261.9 s
Oct 17, 20262.0 s
Oct 24, 20262.0 s
Oct 31, 20262.0 s
Nov 7, 20262.0 s
Nov 14, 20261.9 s
Real-visitor tap response (INP)75th percentile, phones
450 ms157 msMay 30Nov 14207 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026402 ms
Jun 6, 2026406 ms
Jun 13, 2026388 ms
Jun 20, 2026404 ms
Jun 27, 2026416 ms
Jul 4, 2026410 ms
Jul 11, 2026384 ms
Jul 18, 2026380 ms
Jul 25, 2026354 ms
Aug 1, 2026318 ms
Aug 8, 2026290 ms
Aug 15, 2026242 ms
Aug 22, 2026217 ms
Aug 29, 2026196 ms
Sep 5, 2026202 ms
Sep 12, 2026204 ms
Sep 19, 2026196 ms
Sep 26, 2026195 ms
Oct 3, 2026191 ms
Oct 10, 2026197 ms
Oct 17, 2026211 ms
Oct 24, 2026218 ms
Oct 31, 2026221 ms
Nov 7, 2026216 ms
Nov 14, 2026207 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 sugarbearpro.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. sugarbearpro.com at 0.7 s0.7 s
  2. sugarbearpro.com at 1.3 s1.3 s
  3. sugarbearpro.com at 1.9 s1.9 s
  4. sugarbearpro.com at 2.6 s2.6 s
  5. sugarbearpro.com at 3.2 s3.2 s
  6. sugarbearpro.com at 3.9 s3.9 s
  7. sugarbearpro.com at 4.5 s4.5 s
  8. sugarbearpro.com at 5.2 s5.2 s

Speed

10 to fix60
  • Reduce unused JavaScript

    2.9 s · 478 KiB

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

  • Improve image delivery

    250 ms · 2.4 MB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Shopify and TikTok and others), adding 1.6 MB and 875 ms of main-thread time.

  • Mobile performance score: 60

    60/100

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

  • Google Tag Manager adds 513 ms

    513 ms

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

  • Render-blocking requests

    500 ms

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

  • Use efficient cache lifetimes

    300 ms · 73 KiB

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

  • Main-thread work: 2.3 s

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

  • 2,088 HTML elements

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

  • Shopify adds 125 ms

    125 ms

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

  • Reduce unused CSS

    150 ms · 22 KiB

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

  • 6 long tasks on the main thread

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

  • Minify CSS

    150 ms · 4 KiB

    4 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

    31 KiB

    31 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    9 KiB

    Polyfills for old browsers add 9 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: 31 ms

    31 ms

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

Core Web Vitals

9 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: 22.8 s

    22.8 s

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

  • Time to Interactive: 23.5 s

    23.5 s

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

  • Speed Index: 6.1 s

    6.1 s

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

  • Real-user INP: 246 ms

    246 ms

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

  • Real-user FCP: 1.9 s

    1.9 s

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

  • Real-user TTFB: 1.2 s

    1.2 s

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

  • First Contentful Paint: 2.7 s

    2.7 s

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

  • Total Blocking Time: 277 ms

    277 ms

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

5 checks passed
  • Real-user LCP: 2.0 s

    2.0 s

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

  • Real-user CLS: 0.00

    0.00

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

  • Tap response (INP) got 48% faster for real visitors

    -48%

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

  • Largest content (LCP) got 19% faster for real visitors

    -19%

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

4 to fix31
  • Page weight: 44.8 MB in 218 requests

    44.8 MB

    Your homepage downloads 44.8 MB in 218 requests on a phone: media 39.7 MB (6), images 3.1 MB (77) and scripts 1.5 MB (91). Under 2 MB keeps phones on slow connections fast.

  • 18 images far larger than shown

    2.0 MB

    18 images are downloaded at several times the size a phone draws them, for example 8_jamie-kenedym.webp at 390 px wide, shown at 104 px. Resized copies would save about 2.0 MB.

  • 30 images in older formats

    30 images (6.0 MB) 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.

  • An image on the first screen is lazy-loaded

    FINAL_HAIR_MOBILE_POSTER.webp 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).

  • About 12.7 g of CO₂ per visit

    12.69 g

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

Accessibility

7 to fixGoogle 9392
  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  • 6 images without alt text

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

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

  • Alternative text of images should not be repeated as text (24 elements)

    Alternative text of images should not be repeated as text: 24 elements on the page fail this check, rated minor 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.

  • 1 link without text

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

  • ARIA role should be appropriate for the element (2 elements)

    ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h1 → h4), 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. (9 elements).

1 checks passed
  • 51 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: 51 passed and 6 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 9296
  • Structured data has 1 problem

    Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: logo is not an absolute URL ("Liquid error (layout/theme line 40): invalid url input")”.

  • 57 internal links, 7 external

    The homepage links to 57 pages on sugarbearpro.com and 7 external pages.

7 checks passed
  • Meta description: 160 characters

    Your meta description is 160 characters: “Discover SugarbearPRO®, home of the iconic Hair Vitamin Gummies since 2015. Shop vegan, cruelty-free hair, prenatal hai…”.

  • One H1 headline

    Your main headline reads: “SugarbearPRO®”.

  • Title: 59 characters

    Your title is a healthy 59 characters: “SugarbearPRO® | Hair Vitamins, Sleep, Prenatal, Lash & Brow”.

  • Canonical URL set

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

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

AI search readiness

100
  • Opted out of AI training for 1 crawler

    robots.txt blocks GPTBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

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, logo, sameAs (social profiles) and description; contact details would complete it.

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

7 to fix55
  • 1 page without a title

    https://sugarbearpro.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

  • 1 linked page hidden from search

    https://sugarbearpro.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 4 pages share 2 titles

    https://sugarbearpro.com/products/sugarbearpro-hair-vitamin-gummies-1month-v3 and https://sugarbearpro.com/products/sugarbearpro-hair-biotin-vitamin-gummies-1month all use the title “Vegan Hair Vitamin Gummies, 1-Month Supply | SugarBearPRO”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 1 page without a meta description

    https://sugarbearpro.com/customer_authentication/redirect has no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages share a meta description

    https://sugarbearpro.com/products/sugarbearpro-hair-vitamin-gummies-1month-v3 and https://sugarbearpro.com/products/sugarbearpro-hair-biotin-vitamin-gummies-1month use the same meta description. A description written for each page earns more clicks.

  • 4 links to non-canonical URLs

    Your homepage links to 4 pages by a URL that isn't their canonical one, for example https://sugarbearpro.com/products/sugarbearpro-prenatal-hair-vitamin-gummies-70ct-1-month-dtc-v1-parent, whose canonical is https://sugarbearpro.com/products/prenatal-hair-vitamin-gummies-1-month. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 8 pages without an H1

    https://sugarbearpro.com/collections/haircare, https://sugarbearpro.com/collections/sleepcare, https://sugarbearpro.com/collections/lashcare, https://sugarbearpro.com/collections/browcare, https://sugarbearpro.com/collections/shop-all and https://sugarbearpro.com/collections/buy-more-save and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

1 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

Best practices

1 to fixGoogle 9293
  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • Requests the notification permission on page load

    Requests the notification permission on page load.

2 checks passed
  • Tap targets are thumb-sized

    39 of 44 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix93
  • 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.

  • About 571 words of copy

    The homepage carries about 571 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: “EFFECTIVE INGREDIENTS. LEARN MORE”.

  • 38 calls to action

    The homepage has 38 calls to action, for example “Shop Hair”, “Shop Sleep” and “Shop LashCare”.

  • 3 short forms

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

  • Social proof on the page

    Social proof on the homepage: 103 testimonial or review blocks, 42 customer or partner logos and 12 trust badges.

  • Analytics in place

    Analytics detected: PostHog.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

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.

  • 29 cookies set on arrival

    29

    Opening the homepage sets 29 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.

  • 41 other companies contacted

    Loading the homepage contacts 41 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 sugarbearpro.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

Pagefly Ai Page Builder · Elevar Conversion Tracking · Postscript Sms Marketing · Okendo · Beast Currency Converter · Glo Color Swatch · Test Sms · Page Speed Optimizer · Pushowl · In Cart Upsell · luckyorange.com · govx.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
Cloudflare

Company

Headquarters
Oakland Park

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 sugarbearpro.com, including 19 speed issues, 1 SEO issue and 1 conversion gap. 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