Website review, no card needed

betterbodyco.shop logo

betterbodyco.shop website review

Visit site (opens in a new tab)Reviewed 16 November 202644 issues · 84 checks

This review found 44 issues worth fixing on betterbodyco.shop, 15 of them high impact, across 84 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

Full-page screenshot of betterbodyco.shop (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. betterbodyco.shop at 1.0 s1.0 s
  2. betterbodyco.shop at 1.9 s1.9 s
  3. betterbodyco.shop at 2.9 s2.9 s
  4. betterbodyco.shop at 3.9 s3.9 s
  5. betterbodyco.shop at 4.9 s4.9 s
  6. betterbodyco.shop at 5.8 s5.8 s
  7. betterbodyco.shop at 6.8 s6.8 s
  8. betterbodyco.shop at 7.8 s7.8 s

Speed

14 to fix44
  • Reduce unused JavaScript

    3.4 s · 942 KiB

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

  • Use efficient cache lifetimes

    1.4 s · 583 KiB

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

  • Render-blocking requests

    1.0 s

    12 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.0 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: 7.9 s

    A phone's processor spends 7.9 s on main-thread work while loading, 4.5 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, recart.com and ZenDesk and others), adding 10.5 MB and 1.3 s of main-thread time.

  • Shopify adds 64 ms

    64 ms

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

  • Improve image delivery

    300 ms · 603 KiB

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

  • Reduce unused CSS

    450 ms · 87 KiB

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

  • 17 long tasks on the main thread

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

  • Google Tag Manager adds 325 ms

    325 ms

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

  • Legacy JavaScript

    300 ms · 57 KiB

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

  • recart.com adds 323 ms

    323 ms

    recart.com costs a phone 323 ms of main-thread work and 230 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.

  • ZenDesk adds 209 ms

    209 ms

    ZenDesk costs a phone 209 ms of main-thread work and 431 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.

  • Font display

    100 ms

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

  • 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

    3 KiB

    3 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 10 ms

    10 ms

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

Core Web Vitals

6 to fix46
  • Largest Contentful Paint: 16.7 s

    16.7 s

    Your largest element takes 16.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.5 s

    22.5 s

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

  • Speed Index: 9.0 s

    9.0 s

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

  • Total Blocking Time: 789 ms

    789 ms

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

  • First Contentful Paint: 2.4 s

    2.4 s

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

  • 29 images without width and height

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

1 checks passed
  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix70
  • Page weight: 13.7 MB in 415 requests

    13.7 MB

    Your homepage downloads 13.7 MB in 415 requests on a phone: media 8.7 MB (2), scripts 2.4 MB (126) and other files 1.1 MB (221). Under 2 MB keeps phones on slow connections fast.

  • About 3.9 g of CO₂ per visit

    3.87 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

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

  • Images are sized for phones

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

Accessibility

8 to fixGoogle 8590
  • 14 text elements with low contrast

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

  • Summary elements must have discernible text (1 element)

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

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

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

  • Document should not have more than one banner landmark (1 element)

    Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

  • 8 links without text

    8 visible links have no text or label, so screen readers cannot say where they go.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 43 images in the HTML carry an alt attribute.

  • 41 automated accessibility rules passed

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

SEO

4 to fixGoogle 7772
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No H1 headline

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

  • Canonical points to another host

    Your canonical URL points to thebbco.com, not betterbodyco.shop, so Google may credit that host instead.

  • Structured data has 3 problems

    Structured data found (ItemList, Organization and WebSite) but with 3 problems, for example “Organization: url points at a different host (https://betterbody.co)”.

  • 69 internal links, 62 external

    The homepage links to 69 pages on betterbodyco.shop and 62 external pages.

4 checks passed
  • Title: 55 characters

    Your title is a healthy 55 characters: “BB Company - Natural Supplements To Build A Better Body”.

  • 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://betterbodyco.shop/sitemap.xml.

AI search readiness

1 to fix83
  • Parts of the site are closed to 2 AI crawlers

    Your robots.txt lets ChatGPT search (OAI-SearchBot) and ChatGPT (ChatGPT-User) read the homepage but closes other sections to them, so answers about those pages can't cite you.

3 checks passed
  • Organization data: 6 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

3 to fix83
  • 14 pages share 7 titles

    https://betterbodyco.shop/products/provitalize and https://betterbodyco.shop/collections/shop-our-popular-supplements/products/provitalize all use the title “Provitalize | Probiotic for Menopause Weight Loss | BB Company”, and 6 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 15 pages without a meta description

    https://betterbodyco.shop/products/provitalize, https://betterbodyco.shop/collections/shop-our-popular-supplements/products/provitalize, https://betterbodyco.shop/products/radiancy, https://betterbodyco.shop/collections/shop-our-popular-supplements/products/radiancy, https://betterbodyco.shop/products/calmagain and https://betterbodyco.shop/collections/shop-our-popular-supplements/products/calmagain and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://betterbodyco.shop/pages/shop has no <h1> headline, so visitors and search engines get no clear main topic.

  • 4 pages slow to respond

    https://betterbodyco.shop/collections/shop-our-popular-supplements/products/provitalize, https://betterbodyco.shop/products/radiancy, https://betterbodyco.shop/collections/shop-our-popular-supplements/products/radiancy and https://betterbodyco.shop/collections/shop-our-popular-supplements-copy/products/slim-gut-starter-pack took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

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

  • 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 9687
  • 7 small tap targets

    7 of 35 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 4 JavaScript errors while loading

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix72
  • 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.

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • 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 opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • About 886 words of copy

    The homepage carries about 886 words of visible text.

5 checks passed
  • 19 calls to action

    The homepage has 19 calls to action, for example “Shop”, “Contact Us” and “Track Your Order”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 157 testimonial or review blocks and a star rating.

  • Analytics in place

    Analytics detected: Microsoft Clarity.

  • 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
  • 9 trackers load before any consent

    9

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

  • 36 cookies set on arrival

    36

    Opening the homepage sets 36 cookies, 2 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.

  • 61 other companies contacted

    Loading the homepage contacts 61 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 betterbodyco.shop, 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 16 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Consentmo Gdpr · Smart Seo · Microsoft Clarity · Okendo · Recart Sms List Growth · Elevar Conversion Tracking · Eg Auto Add To Cart · Klaviyo Email Marketing Sms · Gdpr Backpack · Applovin Shop Integration · nofraud.com · cloudfront.net · nfcube.com · goaffpro.com · amazonaws.com · usefomo.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
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 44 issues on betterbodyco.shop, including 20 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