Website review, no card needed
cheribundi.com website review
Visit site (opens in a new tab)Reviewed 5 November 202641 issues · 95 checks
This review found 41 issues worth fixing on cheribundi.com, 18 of them high impact, across 95 checks. The most urgent: audioeye.com adds 1.8 s. 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
76C- #73,347 of 120,375 reviewed websitesbeats 34%
- #47,216 of 68,150 online storesbeats 26%
- #44,779 of 62,105 Shopify storesbeats 23%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.1 s |
| May 23, 2026 | 2.1 s |
| May 30, 2026 | 2.0 s |
| Jun 6, 2026 | 2.1 s |
| Jun 13, 2026 | 2.2 s |
| Jun 20, 2026 | 2.4 s |
| Jun 27, 2026 | 2.5 s |
| Jul 4, 2026 | 2.4 s |
| Jul 11, 2026 | 2.4 s |
| Jul 18, 2026 | 2.3 s |
| Jul 25, 2026 | 2.1 s |
| Aug 1, 2026 | 1.9 s |
| Aug 8, 2026 | 1.7 s |
| Aug 15, 2026 | 1.7 s |
| Aug 22, 2026 | 1.8 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.0 s |
| Oct 10, 2026 | 1.9 s |
| Oct 17, 2026 | 1.7 s |
| Oct 24, 2026 | 1.6 s |
| Oct 31, 2026 | 1.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 147 ms |
| May 23, 2026 | 157 ms |
| May 30, 2026 | 161 ms |
| Jun 6, 2026 | 169 ms |
| Jun 13, 2026 | 167 ms |
| Jun 20, 2026 | 170 ms |
| Jun 27, 2026 | 170 ms |
| Jul 4, 2026 | 158 ms |
| Jul 11, 2026 | 157 ms |
| Jul 18, 2026 | 159 ms |
| Jul 25, 2026 | 146 ms |
| Aug 1, 2026 | 144 ms |
| Aug 8, 2026 | 137 ms |
| Aug 15, 2026 | 132 ms |
| Aug 22, 2026 | 152 ms |
| Aug 29, 2026 | 161 ms |
| Sep 5, 2026 | 187 ms |
| Sep 12, 2026 | 204 ms |
| Sep 19, 2026 | 211 ms |
| Sep 26, 2026 | 192 ms |
| Oct 3, 2026 | 178 ms |
| Oct 10, 2026 | 170 ms |
| Oct 17, 2026 | 155 ms |
| Oct 24, 2026 | 160 ms |
| Oct 31, 2026 | 163 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
1.9 s
3.9 s
5.8 s
7.7 s
9.7 s
11.6 s
13.5 s
15.4 s
Speed
audioeye.com adds 1.8 s
1.8 saudioeye.com costs a phone 1.8 s of main-thread work and 303 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: 9.8 s
A phone's processor spends 9.8 s on main-thread work while loading, 4.9 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 (audioeye.com, Clarity and Klaviyo and others), adding 1.2 MB and 2.6 s of main-thread time.
Reduce unused JavaScript
770 ms · 310 KiBAbout 310 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 770 ms faster on a phone.
Mobile performance score: 53
53/100Your mobile performance score is 53. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
400 ms · 593 KiB5 images could be 593 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 400 ms faster on a phone.
Render-blocking requests
550 ms11 files block the first paint until they finish downloading. Deferring or inlining them could save about 550 ms.
Use efficient cache lifetimes
300 ms · 148 KiB25 files are served with short cache lifetimes, so returning visitors download them again (148 KiB).
Clarity adds 297 ms
297 msClarity costs a phone 297 ms of main-thread work and 29 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 219 ms
219 msKlaviyo costs a phone 219 ms of main-thread work and 399 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.
1,772 HTML elements
The page has 1,772 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
13 long tasks on the main thread
13 long tasks block the main thread while loading, the longest for 189 ms. During a long task the page ignores taps.
Minify JavaScript
150 ms · 30 KiB30 KiB could be saved by minifying JavaScript.
Reduce unused CSS
140 ms · 36 KiBAbout 36 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 140 ms faster on a phone.
Legacy JavaScript
50 ms · 54 KiBPolyfills for old browsers add 54 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 50 ms faster on a phone.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Minify CSS
20 ms · 6 KiB6 KiB could be saved by minifying CSS.
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: 9 ms
9 msYour server sent the HTML in 9 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Largest Contentful Paint: 16.2 s
16.2 sYour largest element takes 16.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 16.3 s
16.3 sVisually, the page fills in at 16.3 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 20.6 s
20.6 sThe page becomes fully interactive after 20.6 s. Good is under 3.8 s.
Real-user CLS: 0.12
0.12For real visitors the layout shifts by 0.12 (75th percentile). Good is under 0.1.
First Contentful Paint: 2.5 s
2.5 sThe first text or image appears after 2.5 s on a phone. Good is under 1.8 s.
Total Blocking Time: 353 ms
353 msScripts block taps and scrolling for 353 ms in total while the page loads. Good is under 200 ms.
4 images without width and height
4 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+6%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 147 ms to 163 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user LCP: 1.2 s
1.2 sReal visitors wait 1.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 105 ms
105 msReal visitors wait 105 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.0 s
1.0 sReal visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 510 ms
510 msReal visitors wait 510 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 25% faster for real visitors
-25%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
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 5.6 MB in 498 requests
5.6 MBYour homepage downloads 5.6 MB in 498 requests on a phone: images 2.4 MB (51), scripts 1.3 MB (110) and other files 1.3 MB (302). Under 2 MB keeps phones on slow connections fast.
3 images in older formats
3 images (154 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.
1 image below the first screen load straight away
1 image further down the page (49 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 1.6 g of CO₂ per visit
1.57 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.57 g of CO₂e: 188.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Certain ARIA roles must be contained by particular parents (8 elements)
Certain ARIA roles must be contained by particular parents: 8 elements on the page fail this check, rated critical by axe-core.
Invalid ARIA attributes
3 elements use ARIA attributes their role does not allow, which confuses screen readers.
Certain ARIA roles must contain particular children (3 elements)
Certain ARIA roles must contain particular children: 3 elements on the page fail this check, rated critical by axe-core.
ARIA attributes must conform to valid values (3 elements)
ARIA attributes must conform to valid values: 3 elements on the page fail this check, rated critical by axe-core.
Images must have alternative text (1 element)
Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.
ARIA input fields must have an accessible name (5 elements)
ARIA input fields must have an accessible name: 5 elements on the page fail this check, rated serious by axe-core.
ARIA tab nodes must have an accessible name (4 elements)
ARIA tab nodes must have an accessible name: 4 elements on the page fail this check, rated serious by axe-core.
4 text elements with low contrast
4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Interactive controls must not be nested (3 elements)
Interactive controls must not be nested: 3 elements on the page fail this check, rated serious by axe-core.
Links must have discernible text (1 element)
Links must have discernible text: 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.
Elements marked as presentational should be consistently ignored (3 elements)
Elements marked as presentational should be consistently ignored: 3 elements on the page fail 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
51 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 63 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 12 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
2 H1 headlines
There are 2 <h1> headlines (“Faster Recovery, now at” and “Become a Cheribundi Athlete Ambassador”). One clear main headline is easier for people and search engines.
89 internal links, 8 external
The homepage links to 89 pages on cheribundi.com and 8 external pages.
6 checks passed
Title: 40 characters
Your title is a healthy 40 characters: “100% Pure Tart Cherry Juice | Cheribundi”.
Canonical URL set
The canonical URL is https://cheribundi.com/.
Structured data in place
Structured data found: BreadcrumbList and Organization.
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://cheribundi.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,248 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://cheribundi.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
13 pages without a meta description
https://cheribundi.com/products/pure-tart-cherry-juice, https://cheribundi.com/products/original-tart-cherry-juice, https://cheribundi.com/products/pure-gummies, https://cheribundi.com/products/pure-concentrate, https://cheribundi.com/products/pure-multiserve-concentrate and https://cheribundi.com/products/recovery and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.
10 pages without an H1
https://cheribundi.com/products/pure-tart-cherry-juice, https://cheribundi.com/products/original-tart-cherry-juice, https://cheribundi.com/products/pure-gummies, https://cheribundi.com/products/pure-concentrate, https://cheribundi.com/products/pure-multiserve-concentrate and https://cheribundi.com/products/recovery and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.
4 pages slow to respond
https://cheribundi.com/products/pure-concentrate, https://cheribundi.com/products/pure-multiserve-concentrate, https://cheribundi.com/products/recovery and https://cheribundi.com/products/sleep-tart-cherry-juice took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 26 found) and read each the way a search engine does.
5 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.
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
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'dataset') U.updatePrice (https://cheribundi.com/cdn/shop/t/314/assets/global.m…”.
2 checks passed
Tap targets are thumb-sized
40 of 42 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
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 phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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 975 words of copy
The homepage carries about 975 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 NOW” and “SHOP ALL”.
22 calls to action
The homepage has 22 calls to action, for example “Shop Now”, “Subscribe” and “Shop All”.
8 short forms
8 short forms (2 fields at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 17 testimonial or review blocks and “4530+ reviews”.
Analytics in place
Analytics detected: Google Tag Manager, Microsoft Clarity and Hotjar.
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.
21 cookies set on arrival
21Opening 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.
46 other companies contacted
Loading the homepage contacts 46 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 cheribundi.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 7 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Justuno Email Sms Pop Ups · Elevate Ab Testing · Klaviyo Email Marketing Sms · Redo · revenuehunt.com · juniphq.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
- The footer still says © 2016.
Stack
- Framework
- jQuery
- E-commerce
- Shopify
- Analytics
- Google Tag Manager | Hotjar | Microsoft Clarity
- Hosting
- Shopify
Company
- Headquarters
- Portland
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 41 issues on cheribundi.com, including 19 speed issues, 2 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.