Website review, no card needed

myherbalife.com logo

myherbalife.com website review

Visit site (opens in a new tab)Reviewed 11 October 202653 issues · 88 checks

This review found 53 issues worth fixing on myherbalife.com, 16 of them high impact, across 88 checks. The most urgent: use efficient cache lifetimes. 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
5.3 s4.5 sApr 18Oct 34.7 s
Show as table
DateReal-visitor load time (LCP)
Apr 18, 20265.3 s
Apr 25, 20265.1 s
May 2, 20264.9 s
May 9, 20264.8 s
May 16, 20264.8 s
May 23, 20264.8 s
May 30, 20264.8 s
Jun 6, 20264.8 s
Jun 13, 20264.8 s
Jun 20, 20264.8 s
Jun 27, 20264.8 s
Jul 4, 20264.8 s
Jul 11, 20264.8 s
Jul 18, 20264.8 s
Aug 1, 20264.7 s
Aug 8, 20264.7 s
Aug 15, 20264.7 s
Aug 22, 20264.7 s
Aug 29, 20264.7 s
Sep 5, 20264.7 s
Sep 12, 20264.6 s
Sep 19, 20264.7 s
Sep 26, 20264.7 s
Oct 3, 20264.7 s
Real-visitor tap response (INP)75th percentile, phones
353 ms264 msApr 18Oct 3274 ms
Show as table
DateReal-visitor tap response (INP)
Apr 18, 2026317 ms
Apr 25, 2026318 ms
May 2, 2026327 ms
May 9, 2026336 ms
May 16, 2026341 ms
May 23, 2026343 ms
May 30, 2026336 ms
Jun 6, 2026330 ms
Jun 13, 2026325 ms
Jun 20, 2026324 ms
Jun 27, 2026323 ms
Jul 4, 2026324 ms
Jul 11, 2026324 ms
Jul 18, 2026322 ms
Aug 1, 2026313 ms
Aug 8, 2026310 ms
Aug 15, 2026305 ms
Aug 22, 2026304 ms
Aug 29, 2026304 ms
Sep 5, 2026305 ms
Sep 12, 2026305 ms
Sep 19, 2026302 ms
Sep 26, 2026296 ms
Oct 3, 2026274 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 myherbalife.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

10 to fix41
  • Use efficient cache lifetimes

    6.4 s · 1.5 MB

    48 files are served with short cache lifetimes, so returning visitors download them again (1.5 MB).

  • Reduce unused JavaScript

    4.0 s · 655 KiB

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

  • Render-blocking requests

    4.4 s

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

  • Mobile performance score: 41

    41/100

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

  • Reduce unused CSS

    760 ms · 124 KiB

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

  • Improve image delivery

    590 KiB

    1 image could be 590 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Adobe Tag Manager, Quantum Metric and jQuery CDN and others), adding 1.2 MB and 393 ms of main-thread time.

  • Minify JavaScript

    310 ms · 45 KiB

    45 KiB could be saved by minifying JavaScript.

  • Main-thread work: 3.3 s

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

  • Adobe Tag Manager adds 202 ms

    202 ms

    Adobe Tag Manager costs a phone 202 ms of main-thread work and 451 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

    250 ms

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

  • 14 long tasks on the main thread

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

  • Legacy JavaScript

    150 ms · 23 KiB

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

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

Core Web Vitals

10 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: 18.0 s

    18.0 s

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

  • First Contentful Paint: 7.5 s

    7.5 s

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

  • Time to Interactive: 18.2 s

    18.2 s

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

  • Speed Index: 7.5 s

    7.5 s

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

  • Total Blocking Time: 681 ms

    681 ms

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

  • Real-user LCP: 2.8 s

    2.8 s

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

  • Real-user FCP: 2.5 s

    2.5 s

    Real visitors see the first content after 2.5 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.

  • 3 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    -9%

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

4 checks passed
  • Real-user INP: 162 ms

    162 ms

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

  • 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 10% faster for real visitors

    -10%

    Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' tap response (inp) went from 317 ms to 274 ms 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

3 to fix60
  • 1 image over 500 KB

    li-couple-managing-business-1393890859.jpg weighs 737 KiB. On a phone connection a single image that size takes seconds.

  • Page weight: 3.2 MB in 101 requests

    3.2 MB

    Your homepage downloads 3.2 MB in 101 requests on a phone: scripts 1.7 MB (42), images 820 KiB (14) and fonts 504 KiB (6). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

    1 image (737 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 0.9 g of CO₂ per visit

    0.90 g

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

2 checks passed
  • 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

9 to fixGoogle 8686
  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • <html> element must have a lang attribute (1 element)

    <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

  • 2 images without alt text

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

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

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

  • Contentinfo landmark should not be contained in another landmark (1 element)

    Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

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

    Document should not have more than one contentinfo landmark: 1 element on the page fails 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.

  • 4 form fields without a label

    4 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

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

    Elements with visible text labels do not have matching accessible names. (1 element).

1 checks passed
  • 35 automated accessibility rules passed

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

SEO

10 to fixGoogle 7351
  • 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.

  • Title is short (15 characters)

    Your title is only 15 characters: “myHerbalife.com”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

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

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No XML sitemap

    No XML sitemap at https://www.myherbalife.com/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

    There is no robots.txt at myherbalife.com/robots.txt, the first file search crawlers ask for.

  • Only 3 internal links

    The homepage links to only 3 pages on your own site, so visitors and crawlers find few routes into the rest of it.

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

AI search readiness

1 to fix88
  • 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://www.myherbalife.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.

2 checks passed
  • AI answer engines may read the site

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

  • Text is in the HTML

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

Other pages

3 to fix83
  • 4 pages share a title

    /, https://www.myherbalife.com/Home/RedirectToProfileLogin, https://www.myherbalife.com/en-US/ed/ds/pages/public/privacy_policy.html and https://www.myherbalife.com/en-US/ed/ds/pages/public/cookie_policy.html all use the title “myHerbalife.com”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 3 pages without a meta description

    https://www.myherbalife.com/Home/RedirectToProfileLogin, https://www.myherbalife.com/en-US/ed/ds/pages/public/privacy_policy.html and https://www.myherbalife.com/en-US/ed/ds/pages/public/cookie_policy.html have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages without an H1

    https://www.myherbalife.com/Home/RedirectToProfileLogin, https://www.myherbalife.com/en-US/ed/ds/pages/public/privacy_policy.html and https://www.myherbalife.com/en-US/ed/ds/pages/public/cookie_policy.html have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages with very little text

    https://www.myherbalife.com/en-US/ed/ds/pages/public/privacy_policy.html and https://www.myherbalife.com/en-US/ed/ds/pages/public/cookie_policy.html 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.

  • 3 internal pages checked

    We fetched 3 pages linked from your homepage and read each the way a search engine does.

4 checks passed
  • Linked pages load

    All 3 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 3 pages that loaded have a <title>.

Best practices

3 to fixGoogle 7385
  • 6 small tap targets

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

  • 2 third-party cookies

    2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Access to CSS stylesheet at 'https://assets.herbalifenutrition.com/content/dam/herbalife/sites/myherbalife/site-structu…”.

  • Browser-reported issues

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

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix71
  • Thin social proof

    Social proof on the homepage: 1 customer or partner logo. 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.

  • Only about 159 words

    The homepage has only about 159 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
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Sign Up”.

  • 1 call to action

    The homepage has 1 call to action, for example “Sign Up”.

  • 1 short form

    A short form (0 fields at most) is right on the homepage.

Privacy and tracking

  • 19 cookies set on arrival

    19

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

  • 13 other companies contacted

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

2 checks passed
  • Consent tool: OneTrust

    A consent management tool (OneTrust) loads with the page.

  • 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 myherbalife.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Go beyond the website

What your $25 Growth Playbook adds

This review found 53 issues on myherbalife.com, including 20 speed issues, 10 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