eternapure.com website review

A phone's processor spends 6.0 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 (posthog.com, Yotpo and gomega.ai and others), adding 2.3 MB and 1.6 s of main-thread time.

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

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

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

posthog.com costs a phone 534 ms of main-thread work and 259 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.

Yotpo costs a phone 260 ms of main-thread work and 463 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.

The page has 2,625 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

rebuyengine.com costs a phone 144 ms of main-thread work and 737 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.

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

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

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

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

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

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

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

18 KiB JavaScript is shipped twice across bundles.

18 KiB could be saved by minifying JavaScript.

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.

4 KiB could be saved by minifying CSS.

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.

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

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

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

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

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

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

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

Your homepage downloads 4.8 MB in 374 requests on a phone: scripts 2.9 MB (124), other files 986 KiB (200) and images 410 KiB (17). Under 2 MB keeps phones on slow connections fast.

SAH_Company_Banner_v3_SAH_Company_desktop_1_98e74ac6-37f6-40 weighs 649 KiB. On a phone connection a single image that size takes seconds.

6 images (1.2 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.

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

ARIA attributes must conform to valid names: 1 element on the page fails this check, rated critical by axe-core.

1 button has no accessible name, so screen readers announce just “button”.

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

Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one contentinfo landmark: 1 element on the page fails 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.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 2 <h1> headlines (“Science You Trust. Wellness They Feel.” and “Science-backed supplements and solutions you & yo…”). One clear main headline is easier for people and search engines.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 55 pages on eternapure.com and 8 external pages.

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.

https://www.summitanimalhealth.com/pages/summit 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.

/ and https://www.summitanimalhealth.com/pages/summit all use the title “Horse, Dog & Cat Supplements | Summit Animal Health”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.summitanimalhealth.com/pages/bundle-builder has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.summitanimalhealth.com/collections/summit-horse, https://www.summitanimalhealth.com/pages/bundle-builder, https://www.summitanimalhealth.com/blogs/ambassadors-summit and https://www.summitanimalhealth.com/pages/product-quiz have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.summitanimalhealth.com/pages/bundle-builder and https://www.summitanimalhealth.com/pages/product-quiz have 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.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_EMPTY_RESPONSE”.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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.

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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 854 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Heap, Klaviyo and Meta Pixel and 1 more (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 43 cookies, 2 of them by other companies (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 57 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.