Website review, no card needed

jjvirginstore.com logo

jjvirginstore.com website review

Visit site (opens in a new tab)Reviewed 8 November 202638 issues · 87 checks

This review found 38 issues worth fixing on jjvirginstore.com, 12 of them high impact, across 87 checks. The most urgent: mobile performance score: 43. 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.4 s1.4 sMay 16Oct 311.5 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.1 s
May 23, 20262.2 s
May 30, 20262.1 s
Jun 6, 20262.1 s
Jun 13, 20262.0 s
Jun 20, 20262.0 s
Jun 27, 20262.3 s
Jul 4, 20262.1 s
Jul 11, 20262.1 s
Jul 18, 20262.1 s
Jul 25, 20261.9 s
Aug 1, 20261.9 s
Aug 8, 20262.0 s
Aug 15, 20262.0 s
Aug 22, 20262.0 s
Aug 29, 20262.0 s
Sep 5, 20261.9 s
Sep 12, 20261.8 s
Sep 19, 20261.8 s
Sep 26, 20261.9 s
Oct 3, 20261.9 s
Oct 10, 20262.0 s
Oct 17, 20261.8 s
Oct 24, 20261.6 s
Oct 31, 20261.5 s
Real-visitor tap response (INP)75th percentile, phones
142 ms100 msMay 16Oct 31129 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026105 ms
May 23, 2026105 ms
May 30, 2026106 ms
Jun 6, 2026113 ms
Jun 13, 2026108 ms
Jun 20, 2026112 ms
Jun 27, 2026116 ms
Jul 4, 2026113 ms
Jul 11, 2026116 ms
Jul 18, 2026112 ms
Jul 25, 2026114 ms
Aug 1, 2026117 ms
Aug 8, 2026127 ms
Aug 15, 2026130 ms
Aug 22, 2026132 ms
Aug 29, 2026129 ms
Sep 5, 2026128 ms
Sep 12, 2026128 ms
Sep 19, 2026129 ms
Sep 26, 2026137 ms
Oct 3, 2026136 ms
Oct 10, 2026136 ms
Oct 17, 2026137 ms
Oct 24, 2026129 ms
Oct 31, 2026129 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 jjvirginstore.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. jjvirginstore.com at 0.7 s0.7 s
  2. jjvirginstore.com at 1.5 s1.5 s
  3. jjvirginstore.com at 2.2 s2.2 s
  4. jjvirginstore.com at 2.9 s2.9 s
  5. jjvirginstore.com at 3.7 s3.7 s
  6. jjvirginstore.com at 4.4 s4.4 s
  7. jjvirginstore.com at 5.1 s5.1 s
  8. jjvirginstore.com at 5.9 s5.9 s

Speed

13 to fix43
  • Mobile performance score: 43

    43/100

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

  • Main-thread work: 7.2 s

    A phone's processor spends 7.2 s on main-thread work while loading, 3.6 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, amaicdn.com and econcierge.solutions and others), adding 3.1 MB and 1.6 s of main-thread time.

  • Reduce unused JavaScript

    150 ms · 1.7 MB

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

  • Use efficient cache lifetimes

    350 ms · 603 KiB

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

  • Render-blocking requests

    950 ms

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

  • Google Tag Manager adds 360 ms

    360 ms

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

  • amaicdn.com adds 300 ms

    300 ms

    amaicdn.com costs a phone 300 ms of main-thread work and 420 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.

  • Improve image delivery

    50 ms · 282 KiB

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

  • 20 long tasks on the main thread

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

  • econcierge.solutions adds 194 ms

    194 ms

    econcierge.solutions costs a phone 194 ms of main-thread work and 732 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.

  • Klaviyo adds 182 ms

    182 ms

    Klaviyo costs a phone 182 ms of main-thread work and 391 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 178 ms

    178 ms

    rebuyengine.com costs a phone 178 ms of main-thread work and 297 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 · 134 KiB

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

  • Legacy JavaScript

    112 KiB

    Polyfills for old browsers add 112 KiB JavaScript that modern phones do not need.

  • Minify JavaScript

    27 KiB

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

  • 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: 14 ms

    14 ms

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

Core Web Vitals

7 to fix100
  • Time to Interactive: 36.1 s

    36.1 s

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

  • Largest Contentful Paint: 6.9 s

    6.9 s

    Your largest element takes 6.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “NEW FROM JJ VIRGIN Muscle is the Key to Reigniting Your Wel…”.

  • Total Blocking Time: 1.4 s

    1.4 s

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

  • Speed Index: 7.3 s

    7.3 s

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

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

    +23%

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

  • First Contentful Paint: 2.0 s

    2.0 s

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

  • 8 images without width and height

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

8 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.5 s

    1.5 s

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

  • Real-user INP: 129 ms

    129 ms

    Real visitors wait 129 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: 416 ms

    416 ms

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

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

    -29%

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

  • Cumulative Layout Shift: 0.026

    0.026

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

Images and page weight

3 to fix53
  • Page weight: 6.3 MB in 407 requests

    6.3 MB

    Your homepage downloads 6.3 MB in 407 requests on a phone: scripts 3.5 MB (159), other files 934 KiB (162) and fonts 866 KiB (22). Under 2 MB keeps phones on slow connections fast.

  • 5 images below the first screen load straight away

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

  • 1 image far larger than shown

    50 KiB

    1 image is downloaded at several times the size a phone draws it, for example ReigniteWellness-Logo_2023.png at 4,320 px wide, shown at 350 px. Resized copies would save about 50 KiB.

  • 1 image in older formats

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

    1.78 g

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

Accessibility

6 to fixGoogle 8691
  • 34 text elements with low contrast

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

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • 1 tap target too small

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

  • 31 images without alt text

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

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

  • 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
  • 49 automated accessibility rules passed

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

SEO

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

  • 113 internal links, 16 external

    The homepage links to 113 pages on jjvirginstore.com and 16 external pages.

8 checks passed
  • Meta description: 154 characters

    Your meta description is 154 characters: “Reignite Wellness offers functional medicine support, clean supplements, and wellness programs for women’s health, horm…”.

  • One H1 headline

    Your main headline reads: “Muscle is the Key toReigniting Your Wellness.”.

  • Title: 53 characters

    Your title is a healthy 53 characters: “Reignite Wellness – Functional Supplements for Health”.

  • Canonical URL set

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

AI search readiness

100
  • No llms.txt

    There is no https://reignitewellness.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.

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

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

  • Text is in the HTML

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

Other pages

1 to fix95
  • 7 pages without an H1

    https://reignitewellness.com/collections/all, https://reignitewellness.com/collections/shakes, https://reignitewellness.com/collections/creatine, https://reignitewellness.com/collections/supplements, https://reignitewellness.com/collections/kits and https://reignitewellness.com/collections/books and 1 other 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 29 found) and read each the way a search engine does.

6 checks passed
  • Linked pages load

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

  • Every page has a meta description

    All 8 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 8 pages that loaded have a <title>.

Best practices

3 to fixGoogle 5488
  • 2 third-party cookies

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

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 5 JavaScript errors while loading

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

  • Browser-reported issues

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

2 checks passed
  • Tap targets are thumb-sized

    49 of 52 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix71
  • 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: 2 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.

  • About 926 words of copy

    The homepage carries about 926 words of visible text.

4 checks passed
  • 17 calls to action

    The homepage has 17 calls to action, for example “Shop”, “Why Buy From Us” and “Register”.

  • 36 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager and 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
  • 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.

  • 23 cookies set on arrival

    23

    Opening the homepage sets 23 cookies, 4 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 jjvirginstore.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 10 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Helium Customer Fields · Klaviyo Email Marketing Sms · Aftersell · Stack Discounts Pro · amazonaws.com · smile.io · nofraud.com · rechargecdn.com · govx.com · rebuyengine.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 Tag Manager | Microsoft Clarity
Hosting
Shopify

Company

Headquarters
Rancho Mirage

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 38 issues on jjvirginstore.com, including 20 speed issues, 1 SEO issue and 3 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