Website review, no card needed

healthletic.io logo

healthletic.io website review

Visit site (opens in a new tab)Reviewed 17 November 202624 issues · 83 checks

This review found 24 issues worth fixing on healthletic.io, 12 of them high impact, across 83 checks. The most urgent: page weight: 66.5 MB in 341 requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
3.0 s2.5 sMay 30Nov 142.6 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.8 s
Jun 6, 20262.8 s
Jun 13, 20262.8 s
Jun 20, 20262.8 s
Jun 27, 20262.7 s
Jul 4, 20262.7 s
Jul 11, 20262.7 s
Jul 18, 20262.8 s
Jul 25, 20262.9 s
Aug 1, 20262.9 s
Aug 8, 20262.9 s
Aug 15, 20262.9 s
Aug 22, 20262.8 s
Aug 29, 20262.9 s
Sep 5, 20262.9 s
Sep 12, 20262.9 s
Sep 19, 20263.0 s
Sep 26, 20262.9 s
Oct 3, 20262.7 s
Oct 10, 20262.7 s
Oct 17, 20262.6 s
Oct 24, 20262.5 s
Oct 31, 20262.6 s
Nov 7, 20262.6 s
Nov 14, 20262.6 s
Real-visitor tap response (INP)75th percentile, phones
220 ms155 msMay 30Nov 14171 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026208 ms
Jun 6, 2026204 ms
Jun 13, 2026204 ms
Jun 20, 2026204 ms
Jun 27, 2026205 ms
Jul 4, 2026210 ms
Jul 11, 2026212 ms
Jul 18, 2026208 ms
Jul 25, 2026204 ms
Aug 1, 2026203 ms
Aug 8, 2026196 ms
Aug 15, 2026197 ms
Aug 22, 2026194 ms
Aug 29, 2026179 ms
Sep 5, 2026172 ms
Sep 12, 2026162 ms
Sep 19, 2026165 ms
Sep 26, 2026172 ms
Oct 3, 2026171 ms
Oct 10, 2026179 ms
Oct 17, 2026173 ms
Oct 24, 2026177 ms
Oct 31, 2026178 ms
Nov 7, 2026172 ms
Nov 14, 2026171 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

Full-page screenshot of healthletic.io (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. healthletic.io at 0.6 s0.6 s
  2. healthletic.io at 1.2 s1.2 s
  3. healthletic.io at 1.9 s1.9 s
  4. healthletic.io at 2.5 s2.5 s
  5. healthletic.io at 3.1 s3.1 s
  6. healthletic.io at 3.7 s3.7 s
  7. healthletic.io at 4.3 s4.3 s
  8. healthletic.io at 5.0 s5.0 s

Speed

7 to fix59
  • Reduce unused JavaScript

    1.4 s · 273 KiB

    About 273 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.4 s faster on a phone.

  • Use efficient cache lifetimes

    1.4 s · 214 KiB

    18 files are served with short cache lifetimes, so returning visitors download them again (214 KiB).

  • Render-blocking requests

    1.4 s

    20 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Clarity, Klaviyo and Shopify and others), adding 63.6 MB and 465 ms of main-thread time.

  • Shopify adds 64 ms

    64 ms

    Shopify costs a phone 64 ms of main-thread work and 63.1 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.

  • Mobile performance score: 59

    59/100

    Your mobile performance score is 59. Pages that score under 90 lose visitors before the first paint.

  • Main-thread work: 2.4 s

    A phone's processor spends 2.4 s on main-thread work while loading, 993 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Improve image delivery

    168 KiB

    19 images could be 168 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 5 long tasks on the main thread

    5 long tasks block the main thread while loading, the longest for 66 ms. During a long task the page ignores taps.

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

  • Reduce unused CSS

    20 ms · 21 KiB

    About 21 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 20 ms faster on a phone.

  • Legacy JavaScript

    30 KiB

    Polyfills for old browsers add 30 KiB JavaScript that modern phones do not need.

  • Minify CSS

    20 ms · 5 KiB

    5 KiB could be saved by minifying CSS.

  • Minify JavaScript

    6 KiB

    6 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: 12 ms

    12 ms

    Your server sent the HTML in 12 ms, well inside Google's 600 ms guideline.

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 17.6 s

    17.6 s

    Your largest element takes 17.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Become Healthletic Scientific formulas designed to elevate …”.

  • Time to Interactive: 17.8 s

    17.8 s

    The page becomes fully interactive after 17.8 s. Good is under 3.8 s.

  • First Contentful Paint: 4.5 s

    4.5 s

    The first text or image appears after 4.5 s on a phone. Good is under 1.8 s.

  • Speed Index: 7.9 s

    7.9 s

    Visually, the page fills in at 7.9 s (Speed Index). Good is under 3.4 s.

  • 62 images without width and height

    62 images have no width and height attributes, so the layout jumps as each one loads.

  • Largest content (LCP) held steady for real visitors

    -6%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 2.8 s to 2.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

9 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: 1.8 s

    1.8 s

    Real visitors wait 1.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 147 ms

    147 ms

    Real visitors wait 147 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.5 s

    1.5 s

    Real visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 718 ms

    718 ms

    Real visitors wait 718 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Tap response (INP) got 17% faster for real visitors

    -17%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 208 ms to 171 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

  • Total Blocking Time: 46 ms

    46 ms

    Scripts block the page for only 46 ms while loading. Good is under 200 ms.

Images and page weight

1 to fix70
  • Page weight: 66.5 MB in 341 requests

    66.5 MB

    Your homepage downloads 66.5 MB in 341 requests on a phone: media 62.9 MB (20), other files 1.3 MB (123) and scripts 1.1 MB (108). Under 2 MB keeps phones on slow connections fast.

  • About 18.9 g of CO₂ per visit

    18.85 g

    By the Sustainable Web Design model, a visit to your homepage emits about 18.85 g of CO₂e: 2262.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

6 to fixGoogle 8591
  • 14 text elements with low contrast

    14 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Scrollable region must have keyboard access (2 elements)

    Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.

  • 119 images without alt text

    119 images have no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (11 elements)

    All page content should be contained by landmarks: 11 elements on the page fail this check, rated moderate by axe-core.

  • 12 links without text

    12 visible links have no text or label, so screen readers cannot say where they go.

  • 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 (h1 → h5, h2 → h4 and h2 → h5), 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).

1 checks passed
  • 43 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 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

1 to fixGoogle 9295
  • 2 H1 headlines

    There are 2 <h1> headlines (“” and “Become Healthletic”). One clear main headline is easier for people and search engines.

  • 43 internal links, 12 external

    The homepage links to 43 pages on healthletic.io and 12 external pages.

7 checks passed
  • Meta description: 153 characters

    Your meta description is 153 characters: “Discover Healthletic supplements for brain health, recovery, gut support & longevity. 3rd party tested, science-backed,…”.

  • Title: 56 characters

    Your title is a healthy 56 characters: “Healthletic Supplements | Science-Backed for Peak Health”.

  • Canonical URL set

    The canonical URL is https://healthletic.io/.

  • 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://healthletic.io/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://healthletic.io/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: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,329 words), so crawlers that don't run JavaScript still read it.

Other pages

100
  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 20 found) and read each the way a search engine does.

7 checks passed
  • Linked pages load

    1 page 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 meta description

    All 1 page that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • 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 1 page that loaded have a <title>.

Best practices

3 to fixGoogle 9671
  • 2 broken images

    2 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=343224921&Ver=2&mid=f3a61685-e8e4-495a-abcf-3e1030247568&bo=2&sid=4f56afb0e22811f18da87f6b66af45cf&vid=4f56d8e0e22811f197921d3a067620e4&vids=1&msclkid=N&pi=918639831&l.

  • 6 small tap targets

    6 of 18 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

100
  • About 954 words of copy

    The homepage carries about 954 words of visible text.

7 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Contact Us” and “SHOP ALL PRODUCTS”.

  • 11 calls to action

    The homepage has 11 calls to action, for example “Contact Us”, “SHOP ALL PRODUCTS” and “START NOW”.

  • 4 short forms

    4 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 3 testimonial or review blocks, 18 customer or partner logos, 1 trust badge and “108,400+ Active Members”.

  • Analytics in place

    Analytics detected: Google Analytics, Microsoft Clarity and Hotjar.

  • 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

1 to fix
  • 8 trackers load before any consent

    8

    Before 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.

  • 43 cookies set on arrival

    43

    Opening the homepage sets 43 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.

  • 44 other companies contacted

    Loading the homepage contacts 44 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 healthletic.io, 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 11 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Blotout Edgetag · Judge Me Reviews · Elevate Ab Testing · Avada Seo Suite · Klaviyo Email Marketing Sms · Aftersell · Announcement Bar Maker By Apphero · Facebook Pixel · goaffpro.com · revenuehunt.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 | Hotjar | Microsoft Clarity
Hosting
Shopify

Company

Founded
2024

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 24 issues on healthletic.io, including 12 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25