Website review, no card needed
visionbody.com website review
Visit site (opens in a new tab)Reviewed 7 November 202629 issues · 107 checks
This review found 29 issues worth fixing on visionbody.com, 9 of them high impact, across 107 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
84B- #15,753 of 88,417 reviewed websitesbeats 77%
- #9,533 of 45,912 online storesbeats 73%
- #9,212 of 41,188 Shopify storesbeats 71%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 3.4 s |
| May 23, 2026 | 3.4 s |
| May 30, 2026 | 3.5 s |
| Jun 6, 2026 | 3.5 s |
| Jun 13, 2026 | 3.6 s |
| Jun 20, 2026 | 3.6 s |
| Jun 27, 2026 | 3.6 s |
| Jul 4, 2026 | 3.6 s |
| Jul 11, 2026 | 3.5 s |
| Jul 18, 2026 | 3.3 s |
| Jul 25, 2026 | 2.9 s |
| Aug 1, 2026 | 2.6 s |
| Aug 8, 2026 | 2.4 s |
| Aug 15, 2026 | 2.7 s |
| Aug 22, 2026 | 3.2 s |
| Aug 29, 2026 | 3.5 s |
| Sep 5, 2026 | 3.5 s |
| Sep 12, 2026 | 3.6 s |
| Sep 19, 2026 | 3.5 s |
| Sep 26, 2026 | 2.9 s |
| Oct 3, 2026 | 2.5 s |
| Oct 10, 2026 | 2.0 s |
| Oct 17, 2026 | 1.7 s |
| Oct 24, 2026 | 1.6 s |
| Oct 31, 2026 | 1.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 235 ms |
| May 23, 2026 | 228 ms |
| May 30, 2026 | 230 ms |
| Jun 6, 2026 | 243 ms |
| Jun 13, 2026 | 251 ms |
| Jun 20, 2026 | 255 ms |
| Jun 27, 2026 | 255 ms |
| Jul 4, 2026 | 236 ms |
| Jul 11, 2026 | 219 ms |
| Jul 18, 2026 | 167 ms |
| Jul 25, 2026 | 128 ms |
| Aug 1, 2026 | 113 ms |
| Aug 8, 2026 | 116 ms |
| Aug 15, 2026 | 137 ms |
| Aug 22, 2026 | 180 ms |
| Aug 29, 2026 | 215 ms |
| Sep 5, 2026 | 216 ms |
| Sep 12, 2026 | 246 ms |
| Sep 19, 2026 | 240 ms |
| Sep 26, 2026 | 190 ms |
| Oct 3, 2026 | 161 ms |
| Oct 10, 2026 | 119 ms |
| Oct 17, 2026 | 95 ms |
| Oct 24, 2026 | 97 ms |
| Oct 31, 2026 | 98 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
How it loaded on a phone
0.6 s
1.2 s
1.7 s
2.3 s
2.9 s
3.5 s
4.0 s
4.6 s
visionbody.com does not allow embedding, so this is Google's rendering of the page.
Speed
Reduce unused JavaScript
1.4 s · 300 KiBAbout 300 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.4 s faster on a phone.
Mobile performance score: 59
59/100Your mobile performance score is 59. Pages that score under 90 lose visitors before the first paint.
Use efficient cache lifetimes
350 ms · 121 KiB8 files are served with short cache lifetimes, so returning visitors download them again (121 KiB).
Improve image delivery
350 ms · 57 KiB7 images could be 57 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.
Hotjar adds 319 ms
319 msHotjar costs a phone 319 ms of main-thread work and 261 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.
Main-thread work: 2.2 s
A phone's processor spends 2.2 s on main-thread work while loading, 936 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
2,043 HTML elements
The page has 2,043 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (Hotjar, Klaviyo and Facebook and others), adding 900 KiB and 478 ms of main-thread time.
Legacy JavaScript
200 ms · 31 KiBPolyfills for old browsers add 31 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.
Render-blocking requests
150 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 150 ms.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 117 ms. During a long task the page ignores taps.
Reduce unused CSS
18 KiBAbout 18 KiB of CSS is downloaded but never applied on this page.
Minify JavaScript
9 KiB9 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: 21 ms
21 msYour server sent the HTML in 21 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 11.2 s
11.2 sYour largest element takes 11.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Muscle is Life. Muscle is Strength. Muscle is Longevity. Bi…”.
First Contentful Paint: 5.3 s
5.3 sThe first text or image appears after 5.3 s on a phone. Good is under 1.8 s.
Time to Interactive: 11.7 s
11.7 sThe page becomes fully interactive after 11.7 s. Good is under 3.8 s.
Speed Index: 6.6 s
6.6 sVisually, the page fills in at 6.6 s (Speed Index). Good is under 3.4 s.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
10 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 sReal visitors wait 1.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 94 ms
94 msReal visitors wait 94 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.5 s
1.5 sReal visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 781 ms
781 msReal visitors wait 781 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 58% faster for real visitors
-58%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 235 ms to 98 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 53% faster for real visitors
-53%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 3.4 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 81 ms
81 msScripts block the page for only 81 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.014
0.014The layout barely moves while loading (CLS 0.014, good is under 0.1).
Images and page weight
Page weight: 2.2 MB in 216 requests
2.2 MBYour homepage downloads 2.2 MB in 216 requests on a phone: scripts 913 KiB (75), other files 776 KiB (105) and images 298 KiB (18). Under 2 MB keeps phones on slow connections fast.
2 images in older formats
2 images (93 KiB) 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.
About 0.6 g of CO₂ per visit
0.62 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.62 g of CO₂e: 74.3 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
21 tap targets too small
21 tap targets are too small or too close together to hit reliably with a finger.
12 text elements with low contrast
12 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Scrollable region must have keyboard access (5 elements)
Scrollable region must have keyboard access: 5 elements on the page fail this check, rated serious by axe-core.
All page content should be contained by landmarks (12 elements)
All page content should be contained by landmarks: 12 elements on the page fail this check, rated moderate 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.
Headings skip levels
Headings skip levels (h2 → 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. (3 elements).
2 checks passed
Every image has alt text
All 164 images in the HTML carry an alt attribute.
51 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 5 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (68 characters)
Your title is 68 characters, so Google will cut it off around 60: “Visionbody Wireless EMS-EMA System | Full-Body Training – VB USA LLC”.
Meta description is long (309 characters)
Your meta description is 309 characters; Google truncates after about 160, so the end of your pitch is cut.
2 links crawlers can't follow
2 links have no real href, so search engines can't follow them.
58 internal links, 2 external
The homepage links to 58 pages on visionbody.com and 2 external pages.
6 checks passed
One H1 headline
Your main headline reads: “Muscle is Life. Muscle is Strength. Muscle is Longevity.”.
Canonical URL set
The canonical URL is https://visionbody.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://visionbody.com/sitemap.xml.
AI search readiness
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, description and contact details; sameAs (social profiles) would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (4,324 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
2 pages without a meta description
/pages/stories and /blogs/news have no meta description, so Google writes the search snippet from whatever text it finds.
4 pages without an H1
/products/ems-personal-system-with-ultimate-powersuit, /pages/why-visionbody, /pages/b2b and /pages/stories 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 22 found) and read each the way a search engine does.
5 checks passed
Linked pages load
6 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.
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 6 pages that loaded have a <title>.
Best practices
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
19 of 19 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Security and trust
Short HSTS lifetime
HSTS is set, but max-age is 91 days; one year is the recommended minimum.
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 (visionbody.com).
Valid certificate (69 days left)
The certificate from Let's Encrypt · YE2 verifies for visionbody.com and is valid for another 69 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://visionbody.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 29 links work
All 29 links checked from your homepage (27 internal, 2 external) answered without errors.
Domain and trust
No CAA record
visionbody.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.
DNSSEC is off
visionbody.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.
2 checks passed
Domain is 18 years old
18 yearsvisionbody.com was registered in Feb 2008 through GoDaddy.com, LLC. An established domain carries more trust with email providers and search engines.
Registered until Feb 2027
visionbody.com is registered until Feb 2027.
Content and conversion
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 analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
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 4,018 words of copy
The homepage carries about 4,018 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “ORDER NOW”.
15 calls to action
The homepage has 15 calls to action, for example “ORDER NOW”, “Apply” and “Order Now”.
5 short forms
5 short forms (1 field at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 39 testimonial or review blocks, 3 customer or partner logos, 6 trust badges and “More than 25.000 happy customers”.
Phone number on the homepage
Your phone number is on the homepage.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Email authentication
No SPF record
visionbody.com has no SPF record, so mail servers can't tell which servers may send email as you. Your mail lands in spam more often, and anyone can send mail pretending to be you.
DMARC is monitor-only (p=none)
DMARC is set to p=none, so mail pretending to be visionbody.com is still delivered. Reports are on, so moving to quarantine is the next step.
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: 25/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.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Klaviyo and 3 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.
17 cookies set on arrival
17Opening the homepage sets 17 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.
31 other companies contacted
Loading the homepage contacts 31 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 7 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
Klaviyo Email Marketing Sms · Simprosys Google Shopping Feed · Geoip Country Redirect · Delta Pixels 2 · b-cdn.net · dualsidedapp.com · visionbody.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
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 29 issues on visionbody.com, including 12 speed issues, 3 SEO issues and 2 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.