Website review, no card needed
cleannutra.com website review
Visit site (opens in a new tab)Reviewed 9 November 202636 issues · 87 checks
This review found 36 issues worth fixing on cleannutra.com, 9 of them high impact, across 87 checks. The most urgent: improve image delivery. 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
86B- #11,077 of 112,035 reviewed websitesbeats 86%
- #6,872 of 64,189 online storesbeats 85%
- #6,670 of 58,648 Shopify storesbeats 84%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 2.0 s |
| May 30, 2026 | 2.0 s |
| Jun 6, 2026 | 2.0 s |
| Jun 13, 2026 | 2.1 s |
| Jun 20, 2026 | 2.1 s |
| Jun 27, 2026 | 2.2 s |
| Jul 4, 2026 | 2.1 s |
| Jul 11, 2026 | 2.0 s |
| Jul 18, 2026 | 1.9 s |
| Jul 25, 2026 | 1.9 s |
| Aug 1, 2026 | 1.9 s |
| Aug 8, 2026 | 1.9 s |
| Aug 15, 2026 | 2.0 s |
| Aug 22, 2026 | 2.0 s |
| Aug 29, 2026 | 2.0 s |
| Sep 5, 2026 | 2.0 s |
| Sep 12, 2026 | 2.0 s |
| Sep 19, 2026 | 2.0 s |
| Sep 26, 2026 | 2.0 s |
| Oct 3, 2026 | 2.1 s |
| Oct 10, 2026 | 2.1 s |
| Oct 17, 2026 | 2.1 s |
| Oct 24, 2026 | 2.1 s |
| Oct 31, 2026 | 2.1 s |
| Nov 7, 2026 | 2.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 138 ms |
| May 30, 2026 | 143 ms |
| Jun 6, 2026 | 145 ms |
| Jun 13, 2026 | 145 ms |
| Jun 20, 2026 | 145 ms |
| Jun 27, 2026 | 146 ms |
| Jul 4, 2026 | 144 ms |
| Jul 11, 2026 | 143 ms |
| Jul 18, 2026 | 141 ms |
| Jul 25, 2026 | 139 ms |
| Aug 1, 2026 | 141 ms |
| Aug 8, 2026 | 141 ms |
| Aug 15, 2026 | 145 ms |
| Aug 22, 2026 | 141 ms |
| Aug 29, 2026 | 139 ms |
| Sep 5, 2026 | 138 ms |
| Sep 12, 2026 | 138 ms |
| Sep 19, 2026 | 138 ms |
| Sep 26, 2026 | 142 ms |
| Oct 3, 2026 | 145 ms |
| Oct 10, 2026 | 154 ms |
| Oct 17, 2026 | 163 ms |
| Oct 24, 2026 | 170 ms |
| Oct 31, 2026 | 170 ms |
| Nov 7, 2026 | 158 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
Speed
Improve image delivery
2.6 s · 3.0 MB18 images could be 3.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.6 s faster on a phone.
Reduce unused JavaScript
900 ms · 168 KiBAbout 168 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 900 ms faster on a phone.
Mobile performance score: 65
65/100Your mobile performance score is 65. Pages that score under 90 lose visitors before the first paint.
Use efficient cache lifetimes
500 ms · 86 KiB17 files are served with short cache lifetimes, so returning visitors download them again (86 KiB).
Render-blocking requests
450 ms6 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.
1,803 HTML elements
The page has 1,803 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 (Shopify, 506.io and mountain.com and others), adding 592 KiB and 172 ms of main-thread time.
Legacy JavaScript
150 ms · 22 KiBPolyfills for old browsers add 22 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
1 long task on the main thread
1 long task block the main thread while loading, the longest for 89 ms. During a long task the page ignores taps.
Minify JavaScript
13 KiB13 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.
2 checks passed
Main-thread work: 1.7 s
A phone's processor spends 1.7 s on main-thread work while loading, 860 ms of it running JavaScript. That is comfortably low.
Server response: 13 ms
13 msYour server sent the HTML in 13 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 22.2 s
22.2 sYour largest element takes 22.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Clean Nutra supplements”.
Time to Interactive: 23.2 s
23.2 sThe page becomes fully interactive after 23.2 s. Good is under 3.8 s.
Speed Index: 6.2 s
6.2 sVisually, the page fills in at 6.2 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.7 s
2.7 sThe first text or image appears after 2.7 s on a phone. Good is under 1.8 s.
2 images without width and height
2 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 17% slower for real visitors
+17%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 138 ms to 158 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+3%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 2.0 s to 2.1 s 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: 2.0 s
2.0 sReal visitors wait 2.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 90 ms
90 msReal visitors wait 90 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.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 663 ms
663 msReal visitors wait 663 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.023
0.023The layout barely moves while loading (CLS 0.023, good is under 0.1).
Total Blocking Time: 39 ms
39 msScripts block the page for only 39 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 6.4 MB in 231 requests
6.4 MBYour homepage downloads 6.4 MB in 231 requests on a phone: images 4.6 MB (37), other files 826 KiB (100) and scripts 628 KiB (72). Under 2 MB keeps phones on slow connections fast.
13 images far larger than shown
2.6 MB13 images are downloaded at several times the size a phone draws them, for example 0adbf87bd5210f2f05c7189af1562342365239bb.jpg at 2,000 px wide, shown at 163 px. Resized copies would save about 2.6 MB.
An image on the first screen is lazy-loaded
e5e7e3724c4a5ad12dc646d3d6e397238a7fd286.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
1 image below the first screen load straight away
1 image further down the page (83 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 1.8 g of CO₂ per visit
1.81 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.81 g of CO₂e: 217.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
2 buttons without a name
2 buttons have no accessible name, so screen readers announce just “button”.
23 text elements with low contrast
23 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (24 elements)
All page content should be contained by landmarks: 24 elements on the page fail this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.
Banner landmark should not be contained in another landmark (1 element)
Banner 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 banner landmark (1 element)
Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
The skip-link target should exist and be focusable (1 element)
The skip-link target should exist and be focusable: 1 element on the page fails 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 and 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. (1 element).
2 checks passed
Every image has alt text
All 49 images in the HTML carry an alt attribute.
45 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: 45 passed and 10 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (20 characters)
Your title is only 20 characters: “Clean Nutraceuticals”. 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.
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.
75 internal links, 3 external
The homepage links to 75 pages on cleannutra.com and 3 external pages.
6 checks passed
Meta description: 123 characters
Your meta description is 123 characters: “The one stop shop for all your nutraceuticals that you can count on being clean. Made in the USA and proudly a USA Comp…”.
One H1 headline
Your main headline reads: “Your Health, Simplified”.
Canonical URL set
The canonical URL is https://cleannutra.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://cleannutra.com/sitemap.xml.
AI search readiness
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://cleannutra.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
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 (797 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page hidden from search
https://cleannutra.com/a/loop_subscriptions/customer is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
2 pages share a title
/ and https://cleannutra.com/a/loop_subscriptions/customer all use the title “Clean Nutraceuticals”. 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://cleannutra.com/collections/all and https://cleannutra.com/a/loop_subscriptions/customer have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://cleannutra.com/a/loop_subscriptions/customer has 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 37 found) and read each the way a search engine does.
3 checks passed
Linked pages load
4 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 title
All 4 pages that loaded have a <title>.
Best practices
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “❌ [WAIT-FOR-UTILS] Growi cookie utilities not loaded after 5 retries (500ms total)”.
3 distorted images
3 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
2 checks passed
Tap targets are thumb-sized
39 of 46 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 993 words of copy
The homepage carries about 993 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” and “TRACK ORDER”.
22 calls to action
The homepage has 22 calls to action, for example “Shop”, “Track Order” and “SHOP NOW”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 19 testimonial or review blocks, 1 customer or partner logo, a star rating and “1M+ Customers”.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, Microsoft Clarity and TikTok Pixel.
Privacy and tracking
11 trackers load before any consent
11Before a visitor clicks anything, the page loads Amazon Ads, Google Ads, Google Analytics, Google Tag Manager and Klaviyo and 6 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.
44 cookies set on arrival
44Opening the homepage sets 44 cookies, 5 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 cleannutra.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 19 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Pandectes Gdpr · Blotout Edgetag · Eg Auto Add To Cart · Judge Me Reviews · Mntn · Triplewhale · Klaviyo Email Marketing Sms · Growi Creator Management · Postscript Sms Marketing · Gdpr Cookie Consent · Applovin Shop Integration · Aftersell · Isonomy · Test Sms · trustpilot.com · hextom.com · socialsnowball.io · kount.com · archive-digger.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
- Tailwind CSS
- E-commerce
- Shopify
- Analytics
- Google Analytics | Google Tag Manager | Microsoft Clarity
- Hosting
- Shopify
Hiring
- Hiring
- 2 open roles
- Teams
- Operations (2)
- Job board
- bamboohr
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 36 issues on cleannutra.com, including 11 speed issues, 3 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.