byheart.com website review

About 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.8 s faster on a phone.

Your mobile performance score is 30. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

8 third-party services load with your homepage (Amplitude Mobile Analytics, Google Tag Manager and Accessibe Accessibility Overlay and others), adding 1.2 MB and 1.5 s of main-thread time.

20 long tasks block the main thread while loading, the longest for 1.2 s. During a long task the page ignores taps.

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

Amplitude Mobile Analytics costs a phone 461 ms of main-thread work and 100 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.

4 files block the first paint until they finish downloading. Deferring or inlining them could save about 350 ms.

Google Tag Manager costs a phone 286 ms of main-thread work and 202 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 costs a phone 230 ms of main-thread work and 359 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.

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

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

73 KiB could be saved by minifying JavaScript.

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Your largest element takes 19.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

Scripts block taps and scrolling for 2.2 s in total while the page loads. Good is under 200 ms.

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

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

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

Your homepage downloads 4.8 MB in 241 requests on a phone: scripts 2.2 MB (83), images 855 KiB (16) and other files 817 KiB (121). Under 2 MB keeps phones on slow connections fast.

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

Images must have alternative text: 2 elements on the page fail this check, rated critical by axe-core.

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: 10 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 on the page fails this check, rated moderate by axe-core.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

Headings skip levels (h2 → h5), which makes the page harder to scan with a screen reader.

Elements with visible text labels do not have matching accessible names. (1 element).

There is no <h1>, so neither visitors nor Google get a clear main headline.

24 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 48 pages on byheart.com and 11 external pages.

https://byheart.com/products/whole-nutrition-formula declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

https://byheart.com/pages/the-path-forward-our-commitment-to-action and https://byheart.com/pages/bio-dr-dr-donald-zink are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

/ and https://byheart.com/products/whole-nutrition-formula all use the title “ByHeart Whole Nutrition Infant Formula”. Search engines can't tell which page to show for a search, so each competes with the others.

https://byheart.com/pages/important-recall-information, https://byheart.com/pages/byheart-faqs, https://byheart.com/pages/newsroom, https://byheart.com/pages/testing, https://byheart.com/pages/the-path-forward-our-commitment-to-action and https://byheart.com/pages/bio-mansour-samadpour and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://byheart.com/pages/important-recall-information, https://byheart.com/pages/jan-23-2026-important-update-on-root-cause-investigation, https://byheart.com/pages/byheart-faqs, https://byheart.com/pages/newsroom, https://byheart.com/pages/tracking and https://byheart.com/products/whole-nutrition-formula and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://byheart.com/products/whole-nutrition-formula took over 3 s to send its HTML from our server.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=187084959&tm=gtm002&Ver=2&mid=65b2cc3f-6581-47c8-bd9e-de350f80816d&bo=1&sid=40bee4a0de1c11f1b94ba933a88c7e52&vid=40beec10de1c11f180dd77bf196354ce&vids=1&msclkid=N&gtm_.

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

6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

There is no form on the homepage, so every lead has to click through to another page first.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 2,634 words of visible text.

Before a visitor clicks anything, the page loads Amplitude, 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.

Opening the homepage sets 44 cookies (measured from a US location before any click).

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.

Loading the homepage contacts 66 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.