peta2z.com website review

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

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

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

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

Shopify costs a phone 184 ms of main-thread work and 476 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 third-party services load with your homepage (Shopify, omnisnippet1.com and nfcube.com and others), adding 735 KiB and 311 ms of main-thread time.

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

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

About 39 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 long tasks block the main thread while loading, the longest for 89 ms. During a long task the page ignores taps.

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

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.

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

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

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

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

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

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

Your homepage downloads 3.0 MB in 306 requests on a phone: scripts 1.2 MB (133), other files 759 KiB (95) and images 726 KiB (29). Under 2 MB keeps phones on slow connections fast.

By the Sustainable Web Design model, a visit to your homepage emits about 0.86 g of CO₂e: 102.9 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.

[role] values are not valid (1 element).

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

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

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

ARIA input fields do not have accessible names (1 element).

Elements use prohibited ARIA attributes (1 element).

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

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

SVG elements with an img role do not have an accessible text alternative (4 elements).

Elements with visible text labels do not have matching accessible names. (1 element).

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

The homepage links to 288 pages on peta2z.com and 16 external pages.

Your Organization JSON-LD is missing logo, 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.

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

https://peta2z.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://peta2z.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://peta2z.com/products/four-paws-magic-coat-professional-series-nourishing-oatmeal-dog-whitening-shampoo-239513 and https://peta2z.com/products/four-paws-magic-coat-professional-series-nourishing-oatmeal-hypoallergenic-dog-shampoo-239511 all use the title “Four Paws, Four Paws Magic Coat Professional Series Nourishing Oatmea…”. Search engines can't tell which page to show for a search, so each competes with the others.

https://peta2z.com/customer_authentication/redirect and https://peta2z.com/pages/wishlist have no meta description, so Google writes the search snippet from whatever text it finds.

https://peta2z.com/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.

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

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

Requests the notification permission on page load.

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.

Your longest form asks for 9 fields (0 required). Every extra field lowers completion.

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

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