pethonesty.com website review

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

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

8 third-party services load with your homepage (Unpkg, Yotpo and cloudfront.net and others), adding 1.4 MB and 1.1 s of main-thread time.

6 images could be 600 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.

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

About 491 KiB of JavaScript is downloaded but never used on this page.

Unpkg costs a phone 469 ms of main-thread work and 32 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.

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

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

Yotpo costs a phone 244 ms of main-thread work and 416 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 27 ms of main-thread work and 442 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.

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

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

About 16 KiB of CSS is downloaded but never applied on this page.

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

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

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

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

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

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

Your homepage downloads 3.6 MB in 293 requests on a phone: scripts 1.4 MB (116), other files 1.0 MB (128) and images 850 KiB (25). Under 2 MB keeps phones on slow connections fast.

logotype_3.png 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 1.02 g of CO₂e: 122.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

16 images have no alt text, which hurts accessibility and image search.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

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

Main 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 banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one main landmark: 1 element on the page fails this check, rated moderate by axe-core.

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

ARIA role should be appropriate for the element: 13 elements on the page fail this check, rated minor by axe-core.

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

The homepage links to 57 pages on pethonesty.com and 0 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.pethonesty.com/products/hip-joint-health-for-dogs-peanut-butter-flavor, https://www.pethonesty.com/collections/cat-squeezables, https://www.pethonesty.com/collections/shop-all-dog, https://www.pethonesty.com/collections/shop-all-cat, https://www.pethonesty.com/pages/about-us and https://www.pethonesty.com/pages/rewards and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.pethonesty.com/products/hip-joint-health-for-dogs-peanut-butter-flavor, https://www.pethonesty.com/collections/cat-squeezables, https://www.pethonesty.com/collections/shop-all-dog, https://www.pethonesty.com/collections/shop-all-cat, https://www.pethonesty.com/pages/about-us and https://www.pethonesty.com/pages/rewards and 9 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 31 found) and read each the way a search engine does.

10 images failed to load on a phone, for example https://www.pethonesty.com/.

9 of 22 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.”).

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://cdn-widget-assets.yotpo.com/ReviewsStarRatingsWidget/ExkLKzGht52V4WvW1K8KabJAX9GAl…”.

Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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

Before a visitor clicks anything, the page loads Klaviyo (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 7 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 29 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.