therapetmd.com website review

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, JSDelivr CDN and Clarity and others), adding 1.6 MB and 3.1 s of main-thread time.

16 images could be 1.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Google Tag Manager costs a phone 941 ms of main-thread work and 705 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.

JSDelivr CDN costs a phone 923 ms of main-thread work and 38 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.

Clarity costs a phone 459 ms of main-thread work and 29 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.

Facebook costs a phone 290 ms of main-thread work and 284 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.

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

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

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

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

2 KiB could be saved by minifying CSS.

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

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.

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

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

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

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

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

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

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

7 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 173 ms to 192 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 8.1 MB in 418 requests on a phone: images 4.6 MB (57), scripts 2.2 MB (120) and other files 919 KiB (182). Under 2 MB keeps phones on slow connections fast.

5 images weigh 7.1 MB together. On a phone connection a single image that size takes seconds.

15 images are downloaded at several times the size a phone draws them, for example Dog-diffuser.webp at 2,934 px wide, shown at 302 px. Resized copies would save about 7.0 MB.

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

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

Homepage_3_1.webp is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

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

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

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

<svg> elements with an img or image role must have alternative text: 2 elements on the page fail this check, rated serious by axe-core.

Your title is 69 characters, so Google will cut it off around 60: “TheraPetMD — Create A Peaceful, Stress-Free Environment For Your Pet!”.

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

Your <h1> is empty.

The homepage links to 51 pages on therapetmd.com and 17 external pages.

Your robots.txt lets ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User) read the homepage but closes other sections to them, so answers about those pages can't cite you.

https://therapetmd.com/en-us/pages/aboutus and https://therapetmd.com/pages/aboutus all use the title “About TheraPet – TheraPetMD”, and 2 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://therapetmd.com/collections/all, https://therapetmd.com/en-us/policies/shipping-policy, https://therapetmd.com/en-us/collections/dog, https://therapetmd.com/en-us/collections/cat, https://therapetmd.com/en-us/pages/faqs and https://therapetmd.com/en-us/pages/tracking-page and 3 others use the same meta description. A description written for each page earns more clicks.

Your homepage links to 4 pages by a URL that isn't their canonical one, for example https://therapetmd.com/collections/all, whose canonical is https://therapetmd.com/en-us/collections/all. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://therapetmd.com/en-us/pages/faqs, https://therapetmd.com/en-us/pages/aboutus, https://therapetmd.com/en-us/pages/tracking-page, https://therapetmd.com/pages/tracking-page and https://therapetmd.com/pages/aboutus have no <h1> headline, so visitors and search engines get no clear main topic.

https://therapetmd.com/collections/all, https://therapetmd.com/en-us/collections/dog, https://therapetmd.com/en-us/collections/cat, https://therapetmd.com/en-us/pages/faqs, https://therapetmd.com/en-us/pages/aboutus and https://therapetmd.com/pages/aboutus and 6 others 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 21 found) and read each the way a search engine does.

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

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

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

3 errors were logged to the browser console while the page loaded, for example “Invalid left-hand side in assignment”.

Chrome logged issues while loading the page (“Cookie”).

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

The homepage carries about 1,103 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Klaviyo, Microsoft Clarity and Pinterest Tag 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 24 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 35 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.