wellnesspet.com website review

7 images could be 4.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.9 s faster on a phone.

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

audioeye.com costs a phone 1.6 s of main-thread work and 300 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

7 third-party services load with your homepage (audioeye.com, Google Tag Manager and Cookiebot and others), adding 781 KiB and 1.8 s of main-thread time.

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

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

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

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

Polyfills for old browsers add 17 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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

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 15.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “happy pug and her owner”.

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

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

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

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

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

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

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

Your homepage downloads 7.9 MB in 63 requests on a phone: images 6.4 MB (24), scripts 737 KiB (17) and fonts 622 KiB (5). Under 2 MB keeps phones on slow connections fast.

4 images weigh 4.7 MB together. On a phone connection a single image that size takes seconds.

2 images are downloaded at several times the size a phone draws them, for example TYDTWD-2026-Group-Photo-1-scaled-e1785269777632.jpg at 1,783 px wide, shown at 330 px. Resized copies would save about 854 KiB.

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

8 images further down the page (4.5 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

2 tap targets are too small or too close together to hit reliably with a finger.

Some lists contain elements other than list items, which screen readers announce wrongly.

Some list items are not inside a list.

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children. (1 element).

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.

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

Your title is only 27 characters: “Home - Wellness Pet Company”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 4 <h1> headlines (“Home”, “Wellness pet company” and “pet lovers”). One clear main headline is easier for people and search engines.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 33 pages on wellnesspet.com and 25 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

There is no https://www.wellnesspet.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.

Your homepage links to https://www.wellnesspet.com/terms, which answers with an error. Visitors hit a dead end and search engines drop it.

https://www.wellnesspet.com/wellness-pet-leaders and https://www.wellnesspet.com/wellpet-leaders all use the title “Leaders - Wellness Pet Company”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.wellnesspet.com/wellness-pet-leaders and https://www.wellnesspet.com/wellpet-leaders use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.wellnesspet.com/wellpet-leaders, whose canonical is https://www.wellnesspet.com/wellness-pet-leaders. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.wellnesspet.com/our-story took over 3 s to send its HTML from our server.

We fetched 9 pages linked from your homepage and read each the way a search engine does.

4 errors were logged to the browser console while the page loaded, for example “Syntax error, unrecognized expression: #Burlington,%20MA”.

Social proof on the homepage: 7 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

Before a visitor clicks anything, the page loads Google Ads and Google Tag Manager (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 1 cookie (measured from a US location before any click).

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