eacanimalcare.com website review

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

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

About 814 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.

8 third-party services load with your homepage (Shopify, Bold Commerce and Clarity and others), adding 1.8 MB and 882 ms of main-thread time.

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

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

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

Bold Commerce costs a phone 236 ms of main-thread work and 484 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 1,801 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

azurefd.net costs a phone 61 ms of main-thread work and 331 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.

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

About 52 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 images could be 154 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Polyfills for old browsers add 36 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.

5 KiB JavaScript is shipped twice across bundles.

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

5 KiB could be saved by minifying JavaScript.

Your largest element takes 7.7 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 16.6 s. Good is under 3.8 s.

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

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

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

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

3 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' largest content (lcp) went from 2.4 s to 2.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 3.7 MB in 300 requests on a phone: scripts 1.8 MB (116), images 900 KiB (38) and other files 708 KiB (87). Under 2 MB keeps phones on slow connections fast.

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

Delayed refresh under 20 hours must not be used: 1 element on the page fails this check, rated critical by axe-core.

1 image has no alt text, which hurts accessibility and image search.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

4 elements hidden from screen readers can still receive keyboard focus.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

1 tap target is too small or too close together to hit reliably with a finger.

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

Your title is 69 characters, so Google will cut it off around 60: “Horse & Pet Care Supplements For Health & Wellbeing – EAC Animal Care”.

There are 2 <h1> headlines (“” and “Cyber week early access”). One clear main headline is easier for people and search engines.

Your meta description is 165 characters; Google truncates after about 160, so the end of your pitch is cut.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

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

The homepage links to 123 pages on eacanimalcare.com and 10 external pages.

https://eacanimalcare.com/collections/all, https://eacanimalcare.com/collections/pet-care-range, https://eacanimalcare.com/collections/equine-range, https://eacanimalcare.com/collections/vet-range, https://eacanimalcare.com/pages/bundles and https://eacanimalcare.com/pages/about and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://eacanimalcare.com/collections/pet-range/products/dog-probiotics-gut-health-inside-out, whose canonical is https://eacanimalcare.com/products/dog-probiotics-gut-health-inside-out. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://eacanimalcare.com/pages/store-locator-1, https://eacanimalcare.com/pages/bundles, https://eacanimalcare.com/pages/rspca-x-eac-pet and https://eacanimalcare.com/pages/auto-ship-faq have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 429 ()”.

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage has only about 10 words of visible text; thin pages give Google and first-time buyers little to go on.

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

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 2 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.