Website review, no card needed
healthycell.com website review
Visit site (opens in a new tab)Reviewed 5 November 202638 issues · 85 checks
This review found 38 issues worth fixing on healthycell.com, 11 of them high impact, across 85 checks. The most urgent: main-thread work: 14.4 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
79C- #49,780 of 109,815 reviewed websitesbeats 49%
- #32,891 of 62,243 online storesbeats 41%
- #31,560 of 56,767 Shopify storesbeats 38%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.5 s |
| May 23, 2026 | 2.6 s |
| May 30, 2026 | 2.5 s |
| Jun 6, 2026 | 2.5 s |
| Jun 13, 2026 | 2.5 s |
| Jun 20, 2026 | 2.4 s |
| Jun 27, 2026 | 2.3 s |
| Jul 4, 2026 | 2.3 s |
| Jul 11, 2026 | 2.4 s |
| Jul 18, 2026 | 2.3 s |
| Jul 25, 2026 | 2.3 s |
| Aug 1, 2026 | 2.3 s |
| Aug 8, 2026 | 2.2 s |
| Aug 15, 2026 | 2.3 s |
| Aug 22, 2026 | 2.3 s |
| Aug 29, 2026 | 2.3 s |
| Sep 5, 2026 | 2.3 s |
| Sep 12, 2026 | 2.3 s |
| Sep 19, 2026 | 2.3 s |
| Sep 26, 2026 | 2.4 s |
| Oct 3, 2026 | 2.4 s |
| Oct 10, 2026 | 2.4 s |
| Oct 17, 2026 | 2.4 s |
| Oct 24, 2026 | 2.4 s |
| Oct 31, 2026 | 2.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 147 ms |
| May 23, 2026 | 146 ms |
| May 30, 2026 | 146 ms |
| Jun 6, 2026 | 146 ms |
| Jun 13, 2026 | 146 ms |
| Jun 20, 2026 | 145 ms |
| Jun 27, 2026 | 153 ms |
| Jul 4, 2026 | 155 ms |
| Jul 11, 2026 | 162 ms |
| Jul 18, 2026 | 162 ms |
| Jul 25, 2026 | 161 ms |
| Aug 1, 2026 | 160 ms |
| Aug 8, 2026 | 157 ms |
| Aug 15, 2026 | 162 ms |
| Aug 22, 2026 | 162 ms |
| Aug 29, 2026 | 168 ms |
| Sep 5, 2026 | 180 ms |
| Sep 12, 2026 | 196 ms |
| Sep 19, 2026 | 217 ms |
| Sep 26, 2026 | 229 ms |
| Oct 3, 2026 | 221 ms |
| Oct 10, 2026 | 214 ms |
| Oct 17, 2026 | 217 ms |
| Oct 24, 2026 | 220 ms |
| Oct 31, 2026 | 226 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.6 s
3.2 s
4.8 s
6.4 s
8.0 s
9.6 s
11.2 s
12.7 s
Speed
Main-thread work: 14.4 s
A phone's processor spends 14.4 s on main-thread work while loading, 4.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Render-blocking requests
1.2 s6 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.2 s.
4,459 HTML elements
The page has 4,459 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Use efficient cache lifetimes
1.6 MB56 files are served with short cache lifetimes, so returning visitors download them again (1.6 MB).
8 third-party services on the page
8 third-party services load with your homepage (alia-prod.com, rebuyengine.com and FullStory and others), adding 2.0 MB and 1.3 s of main-thread time.
Reduce unused JavaScript
150 ms · 1.3 MBAbout 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
Mobile performance score: 60
60/100Your mobile performance score is 60. Pages that score under 90 lose visitors before the first paint.
alia-prod.com adds 331 ms
331 msalia-prod.com costs a phone 331 ms of main-thread work and 486 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.
rebuyengine.com adds 197 ms
197 msrebuyengine.com costs a phone 197 ms of main-thread work and 778 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 221 ms. During a long task the page ignores taps.
Improve image delivery
137 KiB6 images could be 137 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Legacy JavaScript
107 KiBPolyfills for old browsers add 107 KiB JavaScript that modern phones do not need.
Minify JavaScript
97 KiB97 KiB could be saved by minifying JavaScript.
Reduce unused CSS
94 KiBAbout 94 KiB of CSS is downloaded but never applied on this page.
Minify CSS
21 KiB21 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: 17 ms
17 msYour server sent the HTML in 17 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.
Speed Index: 23.0 s
23.0 sVisually, the page fills in at 23.0 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 38.7 s
38.7 sThe page becomes fully interactive after 38.7 s. Good is under 3.8 s.
Total Blocking Time: 1.3 s
1.3 sScripts block taps and scrolling for 1.3 s in total while the page loads. Good is under 200 ms.
Real-user INP: 253 ms
253 msReal visitors wait 253 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 52% slower for real visitors
+52%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 147 ms to 226 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.0 s
2.0 sReal visitors see the first content after 2.0 s (75th percentile). Good is under 1.8 s.
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.
4 images without width and height
4 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
-3%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.5 s to 2.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 2.2 s
2.2 sReal visitors wait 2.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Real-user TTFB: 552 ms
552 msReal visitors wait 552 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 2.5 s
2.5 sYour largest element renders in 2.5 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Supplements that absorb 165% more.”.
Cumulative Layout Shift: 0.013
0.013The layout barely moves while loading (CLS 0.013, good is under 0.1).
Images and page weight
Page weight: 6.3 MB in 485 requests
6.3 MBYour homepage downloads 6.3 MB in 485 requests on a phone: scripts 3.4 MB (135), other files 1.1 MB (248) and images 765 KiB (67). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
15 KiB1 image is downloaded at several times the size a phone draws it, for example fruitful_yield_health_foods_logo_svg.svg at 140 px wide, shown at 40 px. Resized copies would save about 15 KiB.
1 image in older formats
1 image (225 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 1.8 g of CO₂ per visit
1.77 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.77 g of CO₂e: 212.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 load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
2 tap targets too small
2 tap targets are too small or too close together to hit reliably with a finger.
4 images without alt text
4 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (3 elements)
All page content should be contained by landmarks: 3 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 (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
11 form fields without a label
11 form fields have no label, so screen readers announce an empty box and autofill guesses.
6 links without text
6 visible links have no text or label, so screen readers cannot say where they go.
ARIA role should be appropriate for the element (1 element)
ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.
1 checks passed
51 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 57 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 6 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (26 characters)
Your title is only 26 characters: “HealthyCell | Absorb More™”. Between 30 and 65 characters leaves room to say what you do and for whom.
Structured data has 1 problem
Structured data found (WebSite) but with 1 problem, for example “ld+json block 1 is not valid JSON (Unexpected token 'h', ..."sameAs": [https://ww"... is not va)”.
7 links with vague text
7 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
110 internal links, 4 external
The homepage links to 110 pages on healthycell.com and 4 external pages.
6 checks passed
Meta description: 107 characters
Your meta description is 107 characters: “MicroGel™ supplements replace pills and allow you to absorb more nutrients so you can reach your potential.”.
One H1 headline
Your main headline reads: “Supplements that absorb 165% more.”.
Canonical URL set
The canonical URL is https://www.healthycell.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.healthycell.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.
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 (1,212 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.healthycell.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
4 pages without a meta description
https://www.healthycell.com/pages/quiz, https://www.healthycell.com/pages/which-multivitamin-is-right-for-you, https://www.healthycell.com/a/loop_subscriptions/bundle/b5b6d01e34f842448a6e445ab67cfa76 and https://www.healthycell.com/collections/bundle have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://www.healthycell.com/a/loop_subscriptions/bundle/b5b6d01e34f842448a6e445ab67cfa76 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 50 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
1 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=97148719&tm=shpfy_ui&Ver=2&mid=c8f80acf-0322-48ca-87d7-e575e7c6f81d&bo=1&sid=1c9c0300d90611f1a89d77b99edd3f42&vid=1c9c2490d90611f1833cd3c836e4cb12&vids=1&msclkid=N&pi=.
12 small tap targets
12 of 36 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'push')”.
Missing source maps
Large scripts ship without source maps.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
A 9-field form
Your longest form asks for 9 fields (0 required). Every extra field lowers completion.
About 768 words of copy
The homepage carries about 768 words of visible text.
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop all”.
14 calls to action
The homepage has 14 calls to action, for example “Shop”, “Shop All” and “Try Them All”.
Social proof on the page
Social proof on the homepage: 2 testimonial or review blocks and 18 customer or partner logos.
Analytics in place
Analytics detected: Google Analytics.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
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
11 trackers load before any consent
11Before a visitor clicks anything, the page loads FullStory, 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.
52 cookies set on arrival
52Opening the homepage sets 52 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.
80 other companies contacted
Loading the homepage contacts 80 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 healthycell.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
Intelligems A B Testing · Gorgias Live Chat Helpdesk · Depict Search Merchandising · Trynow Try Before You Buy · Jurni Ai Personalized Funnels · Klaviyo Email Marketing Sms · Rebuy Personalization Engine · Stape Remix · Cartz Social Group Buying · Applovin Shop Integration · mailchimp.com · chimpstatic.com · salesreps.io · onrender.com · amazonaws.com · retention.com · octaneai.com · cloudfront.net · instant.one
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
- E-commerce
- Shopify
- Analytics
- Google Analytics | FullStory
- Hosting
- Shopify
Company
- Headquarters
- Montclair
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 38 issues on healthycell.com, including 18 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.