Website review, no card needed

mindvalleystates.com logo

mindvalleystates.com website review

Visit site (opens in a new tab)Reviewed 7 November 202626 issues · 97 checks

This review found 26 issues worth fixing on mindvalleystates.com, 6 of them high impact, across 97 checks. The most urgent: vWO adds 2.3 s. 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
1.5 s841 msMay 16Oct 311.4 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.1 s
May 23, 20261.1 s
May 30, 20261.1 s
Jun 6, 20261.2 s
Jun 13, 20261.3 s
Jun 20, 20261.2 s
Jun 27, 20261.1 s
Jul 4, 20261.1 s
Jul 11, 2026913 ms
Jul 18, 2026947 ms
Jul 25, 20261.0 s
Aug 1, 20261.1 s
Aug 8, 20261.1 s
Aug 15, 20261.1 s
Aug 22, 20261.1 s
Aug 29, 20261.1 s
Sep 5, 20261.1 s
Sep 12, 20261.0 s
Sep 19, 20261.0 s
Sep 26, 20261.1 s
Oct 3, 20261.1 s
Oct 10, 20261.2 s
Oct 17, 20261.2 s
Oct 24, 20261.3 s
Oct 31, 20261.4 s
Real-visitor tap response (INP)75th percentile, phones
102 ms76 msMay 16Oct 3199 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202683 ms
May 23, 202684 ms
May 30, 202684 ms
Jun 6, 202687 ms
Jun 13, 202695 ms
Jun 20, 202696 ms
Jun 27, 202695 ms
Jul 4, 202694 ms
Jul 11, 202687 ms
Jul 18, 202686 ms
Jul 25, 202685 ms
Aug 1, 202684 ms
Aug 8, 202687 ms
Aug 15, 202692 ms
Aug 22, 202696 ms
Aug 29, 202696 ms
Sep 5, 202689 ms
Sep 12, 202688 ms
Sep 19, 202684 ms
Sep 26, 202681 ms
Oct 3, 202679 ms
Oct 10, 202687 ms
Oct 17, 202695 ms
Oct 24, 202696 ms
Oct 31, 202699 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 mindvalleystates.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. mindvalleystates.com at 1.2 s1.2 s
  2. mindvalleystates.com at 2.4 s2.4 s
  3. mindvalleystates.com at 3.6 s3.6 s
  4. mindvalleystates.com at 4.8 s4.8 s
  5. mindvalleystates.com at 6.0 s6.0 s
  6. mindvalleystates.com at 7.2 s7.2 s
  7. mindvalleystates.com at 8.4 s8.4 s
  8. mindvalleystates.com at 9.6 s9.6 s

mindvalleystates.com does not allow embedding, so this is Google's rendering of the page.

Speed

8 to fix50
  • VWO adds 2.3 s

    2.3 s

    VWO costs a phone 2.3 s of main-thread work and 235 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Main-thread work: 11.1 s

    A phone's processor spends 11.1 s on main-thread work while loading, 5.4 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 (VWO, Facebook and Segment and others), adding 590 KiB and 3.2 s of main-thread time.

  • Use efficient cache lifetimes

    800 ms · 325 KiB

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

  • Mobile performance score: 50

    50/100

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

  • Render-blocking requests

    650 ms

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

  • 20 long tasks on the main thread

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

  • Facebook adds 404 ms

    404 ms

    Facebook costs a phone 404 ms of main-thread work and 153 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

    150 ms · 71 KiB

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

  • Reduce unused JavaScript

    178 KiB

    About 178 KiB of JavaScript is downloaded but never used on this page.

  • Minify JavaScript

    28 KiB

    28 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    13 KiB

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

  • Reduce unused CSS

    11 KiB

    About 11 KiB of CSS is downloaded but never applied on this page.

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

    2 KiB

    2 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 16 ms

    16 ms

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

Core Web Vitals

5 to fix100
  • Total Blocking Time: 2.4 s

    2.4 s

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

  • Time to Interactive: 11.7 s

    11.7 s

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

  • Largest Contentful Paint: 5.4 s

    5.4 s

    Your largest element takes 5.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “PRECISION MOOD DESIGN Choose the state you're in. Focus, ca…”.

  • Largest content (LCP) got 23% slower for real visitors

    +23%

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

  • Speed Index: 3.7 s

    3.7 s

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

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

    +17%

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

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.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: 120 ms

    120 ms

    Real visitors wait 120 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.

  • Real-user FCP: 1.6 s

    1.6 s

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

  • Real-user TTFB: 520 ms

    520 ms

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

  • First Contentful Paint: 1.3 s

    1.3 s

    The first text or image appears after 1.3 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix85
  • Page weight: 2.0 MB in 116 requests

    2.0 MB

    Your homepage downloads 2.0 MB in 116 requests on a phone: scripts 677 KiB (51), other files 609 KiB (30) and images 361 KiB (21). Under 2 MB keeps phones on slow connections fast.

  • About 0.6 g of CO₂ per visit

    0.58 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.58 g of CO₂e: 69.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

1 to fixGoogle 10099
  • ARIA role should be appropriate for the element (17 elements)

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

2 checks passed
  • Every image has alt text

    All 69 images in the HTML carry an alt attribute.

  • 52 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 52 passed and 1 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 9282
  • Title is short (17 characters)

    Your title is only 17 characters: “Mindvalley States”. 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.

  • Meta description is long (267 characters)

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

  • 14 links with vague text

    14 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 69 internal links, 4 external

    The homepage links to 69 pages on mindvalleystates.com and 4 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “Choose the state you're in.”.

  • Canonical URL set

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

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.

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.

  • Text is in the HTML

    Your server sends the page's text in the HTML (2,562 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
  • 8 pages without a meta description

    /pages/science, /pages/ebook, /blogs/states, /collections/all, /pages/support and /pages/refund-policy and 2 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 16 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

1 to fixGoogle 9693
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “condition rejected ()=>E(()=>qi().analyticsProcessingAllowed)”.

2 checks passed
  • Tap targets are thumb-sized

    10 of 12 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Security and trust

100
  • Short HSTS lifetime

    HSTS is set, but max-age is 91 days; one year is the recommended minimum.

  • 1 link through redirect chains

    1 link go through two or more redirects, for example https://www.mindvalleystates.com/account.

  • No Referrer-Policy

    No Referrer-Policy header, so full URLs can leak to the sites you link to.

  • No Permissions-Policy

    No Permissions-Policy header to switch off camera, microphone and location for embedded content.

  • Deprecated X-XSS-Protection

    X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

  • No security.txt

    There is no /.well-known/security.txt telling researchers how to report a security problem to you.

7 checks passed
  • Served over HTTPS

    The homepage is served over HTTPS (mindvalleystates.com).

  • Valid certificate (63 days left)

    The certificate from Let's Encrypt · YE2 verifies for mindvalleystates.com and is valid for another 63 days.

  • Protected from clickjacking

    X-Frame-Options or a frame-ancestors policy stops other sites framing yours.

  • Content-Security-Policy set

    A Content-Security-Policy is set, the main browser-side defence against injected scripts.

  • http:// redirects to https

    http://mindvalleystates.com redirects to the secure version.

  • HTTP/2 and HTTP/3

    The server speaks HTTP/2 and advertises HTTP/3, so browsers load many files over one connection.

  • All 22 links work

    All 22 links checked from your homepage (18 internal, 4 external) answered without errors; 3 did not answer within 5 s.

Domain and trust

  • DNSSEC is off

    mindvalleystates.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

3 checks passed
  • Domain is 3 years old

    3 years

    mindvalleystates.com was registered in Aug 2023 through Squarespace Domains II LLC. An established domain carries more trust with email providers and search engines.

  • Certificate issuers are restricted

    CAA records allow only ssl.com, digicert.com, globalsign.com and letsencrypt.org to issue certificates for mindvalleystates.com, so a mis-issued certificate from anyone else is refused.

  • Registered until Aug 2027

    mindvalleystates.com is registered until Aug 2027.

Content and conversion

1 to fix92
  • 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 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 1,808 words of copy

    The homepage carries about 1,808 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop all States”.

  • 15 calls to action

    The homepage has 15 calls to action, for example “Shop all States”, “Learn more →” and “Shop the Box Set →”.

  • 3 short forms

    3 short forms (2 fields at most) are right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 54 testimonial or review blocks and “5,000+ Happy Customers”.

  • Analytics in place

    Analytics detected: Segment.

Email authentication

2 to fix40
  • No DMARC policy

    mindvalleystates.com has no DMARC record, so nothing tells receivers what to do with mail that fails SPF or DKIM. Gmail and Yahoo require DMARC from bulk senders.

  • No DKIM key on the usual selectors

    We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

  • Email authentication score: 40/100

    Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

1 checks passed
  • SPF with a strict ending (-all)

    An SPF record lists your sending servers and tells receivers to reject anything else: “v=spf1 include:_spf.google.com include:mail.zendesk.com -all”.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

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

  • 21 cookies set on arrival

    21

    Opening the homepage sets 21 cookies (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.

  • 25 other companies contacted

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

Apps on your store

Your storefront loads 2 apps. Each one is code from another company running for your shoppers.

None of the apps your storefront loads is on the list of apps with a known security problem.

Apps your storefront loads

nice-team.net · sealsubscriptions.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

No signs of neglect in what was checked: the copyright year, CMS and plugin versions, and jQuery.

Stack

E-commerce
Shopify
Analytics
Segment
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 26 issues on mindvalleystates.com, including 13 speed issues, 4 SEO issues 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