Website review, no card needed
supplebodies.com website review
Visit site (opens in a new tab)Reviewed 10 November 202628 issues · 70 checks
This review found 28 issues worth fixing on supplebodies.com, 8 of them high impact, across 70 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
One score from every part of this review. How it works
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Reduce unused JavaScript
3.1 s · 635 KiBAbout 635 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.1 s faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Shopify and rebuyengine.com and others), adding 1.8 MB and 1.2 s of main-thread time.
Mobile performance score: 53
53/100Your mobile performance score is 53. Pages that score under 90 lose visitors before the first paint.
Use efficient cache lifetimes
700 ms · 197 KiB15 files are served with short cache lifetimes, so returning visitors download them again (197 KiB).
Render-blocking requests
700 ms13 files block the first paint until they finish downloading. Deferring or inlining them could save about 700 ms.
Google Tag Manager adds 409 ms
409 msGoogle Tag Manager costs a phone 409 ms of main-thread work and 359 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.
Shopify adds 222 ms
222 msShopify costs a phone 222 ms of main-thread work and 779 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.7 s
A phone's processor spends 2.7 s on main-thread work while loading, 1.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
rebuyengine.com adds 170 ms
170 msrebuyengine.com costs a phone 170 ms of main-thread work and 330 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
250 ms · 69 KiB2 images could be 69 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 250 ms faster on a phone.
Reduce unused CSS
200 ms · 43 KiBAbout 43 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 200 ms faster on a phone.
9 long tasks on the main thread
9 long tasks block the main thread while loading, the longest for 192 ms. During a long task the page ignores taps.
Legacy JavaScript
100 ms · 49 KiBPolyfills for old browsers add 49 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 100 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.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
Minify CSS
3 KiB3 KiB could be saved by minifying CSS.
1 checks passed
Server response: 8 ms
8 msYour server sent the HTML in 8 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 17.7 s
17.7 sYour largest element takes 17.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Time to Interactive: 19.7 s
19.7 sThe page becomes fully interactive after 19.7 s. Good is under 3.8 s.
Speed Index: 8.3 s
8.3 sVisually, the page fills in at 8.3 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 471 ms
471 msScripts block taps and scrolling for 471 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 2.3 s
2.3 sThe first text or image appears after 2.3 s on a phone. Good is under 1.8 s.
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
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 3.1 MB in 281 requests
3.1 MBYour homepage downloads 3.1 MB in 281 requests on a phone: scripts 1.6 MB (89), other files 841 KiB (146) and images 466 KiB (14). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
28 KiB1 image is downloaded at several times the size a phone draws it, for example supple-drink-glass-knee-joint-pfti.webp at 1,200 px wide, shown at 358 px. Resized copies would save about 28 KiB.
1 image in older formats
1 image (139 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.87 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.87 g of CO₂e: 104.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
Headings skip levels
Headings skip levels (h1 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 7 images in the HTML carry an alt attribute.
43 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 44 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 1 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (80 characters)
Your title is 80 characters, so Google will cut it off around 60: “Chondroitin & Glucosamine Joint Health Supplement Drink | Supple® – Supple Drink”.
14 H1 headlines
There are 14 <h1> headlines (“”, “Supple Joint Health Supplements with Premium Chon…” and “Supple Joint Health Supplements with Premium Chon…”). One clear main headline is easier for people and search engines.
Structured data has 1 problem
Structured data found (Organization and WebSite) but with 1 problem, for example “WebSite: url is not an absolute URL ("supplebodies.com")”.
54 internal links, 12 external
The homepage links to 54 pages on supplebodies.com and 12 external pages.
5 checks passed
Meta description: 158 characters
Your meta description is 158 characters: “Supple is a joint health supplement drink that delivers premium European pharma-grade chondroitin, glucosamine, and bos…”.
Canonical URL set
The canonical URL is https://supplebodies.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://supplebodies.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: 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 (1,483 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://supplebodies.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 pages point its canonical at the homepage
https://supplebodies.com/products/supple-drink-instant-12-stick-sample and https://supplebodies.com/pages/supple-drink-reviews declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.
3 pages share a title
/, https://supplebodies.com/products/supple-drink-instant-12-stick-sample and https://supplebodies.com/pages/supple-drink-reviews all use the title “Chondroitin & Glucosamine Joint Health Supplement Drink | Supple® – S…”. Search engines can't tell which page to show for a search, so each competes with the others.
2 pages without a meta description
https://supplebodies.com/collections/all and https://supplebodies.com/pages/supple-drink-reviews-customer-experiences-testimonials have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://supplebodies.com/products/supple-drink-instant-12-stick-sample and https://supplebodies.com/pages/supple-drink-reviews use the same meta description. A description written for each page earns more clicks.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 16 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.
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 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=187161880&Ver=2&mid=233e8d09-74f2-4de6-94bc-137cca8640d0&bo=1&sid=f8610da0dd0e11f1b52933d2335cc1f2&vid=f8612ab0dd0e11f1855873bc3e57f3f0&vids=1&msclkid=N&pi=918639831&l.
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
7 of 7 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 288 words of copy
The homepage carries about 288 words of visible text.
4 checks passed
18 calls to action
The homepage has 18 calls to action, for example “Shop”, “Shop Supple Now” and “Shop Supple Instant”.
1 short form
A short form (0 fields at most) is right on the homepage.
Analytics in place
Analytics detected: Google Analytics.
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
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel 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.
24 cookies set on arrival
24Opening the homepage sets 24 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.
43 other companies contacted
Loading the homepage contacts 43 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 supplebodies.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 8 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Pagefly Ai Page Builder · Littledata The Data Layer · Seo Manager Venntov · Freegifts · rechargecdn.com · bogos.io · rebuyengine.com · cloudfront.net
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 Analytics
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 28 issues on supplebodies.com, including 14 speed issues, 3 SEO issues 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.