Website review, no card needed
healifeco.com website review
Visit site (opens in a new tab)Reviewed 5 November 202638 issues · 86 checks
This review found 38 issues worth fixing on healifeco.com, 10 of them high impact, across 86 checks. The most urgent: mobile performance score: 44. 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
74C- #87,469 of 125,377 reviewed websitesbeats 26%
- #54,759 of 70,167 online storesbeats 18%
- #51,415 of 63,757 Shopify storesbeats 16%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 3.0 s |
| May 23, 2026 | 3.1 s |
| May 30, 2026 | 3.3 s |
| Jun 6, 2026 | 3.3 s |
| Jun 13, 2026 | 3.6 s |
| Jun 20, 2026 | 3.7 s |
| Jun 27, 2026 | 3.7 s |
| Jul 4, 2026 | 3.6 s |
| Jul 11, 2026 | 3.3 s |
| Jul 18, 2026 | 2.8 s |
| Jul 25, 2026 | 2.8 s |
| Aug 1, 2026 | 2.9 s |
| Aug 8, 2026 | 3.0 s |
| Aug 15, 2026 | 3.6 s |
| Aug 22, 2026 | 3.9 s |
| Aug 29, 2026 | 3.7 s |
| Sep 5, 2026 | 3.6 s |
| Sep 12, 2026 | 3.5 s |
| Sep 19, 2026 | 3.3 s |
| Sep 26, 2026 | 3.4 s |
| Oct 3, 2026 | 3.6 s |
| Oct 10, 2026 | 3.7 s |
| Oct 17, 2026 | 3.5 s |
| Oct 24, 2026 | 3.4 s |
| Oct 31, 2026 | 3.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 350 ms |
| May 23, 2026 | 334 ms |
| May 30, 2026 | 327 ms |
| Jun 6, 2026 | 319 ms |
| Jun 13, 2026 | 335 ms |
| Jun 20, 2026 | 345 ms |
| Jun 27, 2026 | 349 ms |
| Jul 4, 2026 | 346 ms |
| Jul 11, 2026 | 327 ms |
| Jul 18, 2026 | 301 ms |
| Jul 25, 2026 | 297 ms |
| Aug 1, 2026 | 301 ms |
| Aug 8, 2026 | 293 ms |
| Aug 15, 2026 | 298 ms |
| Aug 22, 2026 | 305 ms |
| Aug 29, 2026 | 295 ms |
| Sep 5, 2026 | 322 ms |
| Sep 12, 2026 | 339 ms |
| Sep 19, 2026 | 335 ms |
| Sep 26, 2026 | 334 ms |
| Oct 3, 2026 | 318 ms |
| Oct 10, 2026 | 310 ms |
| Oct 17, 2026 | 327 ms |
| Oct 24, 2026 | 380 ms |
| Oct 31, 2026 | 410 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.8 s
2.4 s
3.0 s
3.5 s
4.1 s
4.7 s
Speed
Mobile performance score: 44
44/100Your mobile performance score is 44. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 7.4 s
A phone's processor spends 7.4 s on main-thread work while loading, 3.6 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 (Shopify, alia-prod.com and Facebook and others), adding 3.0 MB and 1.9 s of main-thread time.
Reduce unused JavaScript
790 ms · 1,011 KiBAbout 1,011 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 790 ms faster on a phone.
Use efficient cache lifetimes
50 ms · 758 KiB23 files are served with short cache lifetimes, so returning visitors download them again (758 KiB).
Shopify adds 392 ms
392 msShopify costs a phone 392 ms of main-thread work and 1.4 MB 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
446 KiB11 images could be 446 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
alia-prod.com adds 382 ms
382 msalia-prod.com costs a phone 382 ms of main-thread work and 336 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.
Facebook adds 323 ms
323 msFacebook costs a phone 323 ms of main-thread work and 313 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 321 ms. During a long task the page ignores taps.
Google Tag Manager adds 284 ms
284 msGoogle Tag Manager costs a phone 284 ms of main-thread work and 319 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.
2,242 HTML elements
The page has 2,242 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
cloudfront.net adds 152 ms
152 mscloudfront.net costs a phone 152 ms of main-thread work and 387 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.
Render-blocking requests
200 ms8 files block the first paint until they finish downloading. Deferring or inlining them could save about 200 ms.
Reduce unused CSS
30 ms · 50 KiBAbout 50 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 30 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).
Legacy JavaScript
49 KiBPolyfills for old browsers add 49 KiB JavaScript that modern phones do not need.
Minify JavaScript
30 ms · 14 KiB14 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: 22 ms
22 msYour server sent the HTML in 22 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: 10.6 s
10.6 sYour largest element takes 10.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 27.9 s
27.9 sThe page becomes fully interactive after 27.9 s. Good is under 3.8 s.
Speed Index: 7.3 s
7.3 sVisually, the page fills in at 7.3 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 927 ms
927 msScripts block taps and scrolling for 927 ms in total while the page loads. Good is under 200 ms.
Real-user LCP: 3.9 s
3.9 sReal visitors wait 3.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 239 ms
239 msReal visitors wait 239 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
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.
Real-user TTFB: 896 ms
896 msReal visitors wait 896 ms for your server to start answering (75th percentile). Good is under 800 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.
14 images without width and height
14 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 15% slower for real visitors
+15%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 350 ms to 410 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+8%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 3.0 s to 3.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0.001
0.001The layout barely moves while loading (CLS 0.001, good is under 0.1).
Images and page weight
Page weight: 5.6 MB in 471 requests
5.6 MBYour homepage downloads 5.6 MB in 471 requests on a phone: scripts 2.6 MB (109), other files 1.5 MB (308) and images 1.0 MB (33). Under 2 MB keeps phones on slow connections fast.
12 images in older formats
12 images (1.9 MB) 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.
2 images far larger than shown
102 KiB2 images are downloaded at several times the size a phone draws them, for example FP1_05719734-cf31-40ac-b169-e75d6703f702_1440x1440.webp at 1,440 px wide, shown at 390 px. Resized copies would save about 102 KiB.
About 1.6 g of CO₂ per visit
1.59 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.59 g of CO₂e: 190.5 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
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (34 elements)
All page content should be contained by landmarks: 34 elements on the page fail this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
4 form fields without a label
4 form fields have no label, so screen readers announce an empty box and autofill guesses.
2 checks passed
Every image has alt text
All 38 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 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 3 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 (9 characters)
Your title is only 9 characters: “Healifeco”. Between 30 and 65 characters leaves room to say what you do and for whom.
64 internal links, 8 external
The homepage links to 64 pages on healifeco.com and 8 external pages.
7 checks passed
Meta description: 94 characters
Your meta description is 94 characters: “Healifeco thrives to design and manufacture the most innovative health products on the market.”.
One H1 headline
Your main headline reads: “<img src="//www.healifeco.com/cdn/shop/files/2_d73e6932-7c4e-4ec4-8574-99edc19b1db9_170x.png?v=1666610458" srcset="//ww…”.
Canonical URL set
The canonical URL is https://www.healifeco.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://www.healifeco.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.healifeco.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.
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.
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 (790 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page without a meta description
https://www.healifeco.com/collections/shop has no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://www.healifeco.com/collections/shop has no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://www.healifeco.com/collections/shop has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 20 found) and read each the way a search engine does.
5 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.
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 4 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=343189480&tm=gtm002&Ver=2&mid=2f691045-18de-40a3-bf31-98db5eb7d433&bo=1&sid=5c0c8890d97411f1b7ebdf7bb230e0fc&vid=5c141fc0d97411f1877035d77b305980&vids=1&msclkid=N&pi=9.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_CERT_AUTHORITY_INVALID”.
2 checks passed
Tap targets are thumb-sized
11 of 12 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
About 446 words of copy
The homepage carries about 446 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 NOW”.
12 calls to action
The homepage has 12 calls to action, for example “Shop”, “Contact” and “Track Order”.
11 short forms
11 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 4 testimonial or review blocks and “Loved by 100,000+ Customers”.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Microsoft Clarity.
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
10 trackers load before any consent
10Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 5 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.
36 cookies set on arrival
36Opening the homepage sets 36 cookies, 1 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.
54 other companies contacted
Loading the homepage contacts 54 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 healifeco.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 17 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Gempages Builder · Yeps · Judge Me Reviews · Wingify · Klaviyo Email Marketing Sms · Gempages Cro · Affiliatery · Hoppy Countdown · Loop Subscriptions · Yuri Facebook Multi Pixels · Slide Cart · Zipify Oneclickupsell · trustpilot.com · opinew.com · gandalf.ee · cloudfront.net · onetext.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
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 healifeco.com, including 24 speed issues and 1 SEO issue. 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.