pet-lab.com.au website review

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

A phone's processor spends 5.6 s on main-thread work while loading, 2.3 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.

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

8 third-party services load with your homepage (alia-prod.com, rebuyengine.com and Reviews.io and others), adding 2.0 MB and 685 ms of main-thread time.

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

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

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

rebuyengine.com costs a phone 148 ms of main-thread work and 671 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.

Reviews.io costs a phone 92 ms of main-thread work and 308 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 56 ms of main-thread work and 335 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.

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

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

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

14 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 20.7 s. Good is under 3.8 s.

Your largest element takes 6.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “The New Breakthrough Enzyme Formula That Rapidly Eliminates…”.

Visually, the page fills in at 6.4 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 115 ms to 145 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

The first text or image appears after 2.0 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 1.9 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 4.7 MB in 453 requests on a phone: scripts 2.1 MB (123), other files 1.1 MB (222) and images 983 KiB (69). Under 2 MB keeps phones on slow connections fast.

3 images are downloaded at several times the size a phone draws them, for example image_2932d004-635f-4d88-b0a5-f314772f18f2.jpg at 1,000 px wide, shown at 280 px. Resized copies would save about 80 KiB.

1 image (146 KiB) is 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.

1 image further down the page (20 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

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

Elements must only use permitted ARIA attributes: 12 elements on the page fail this check, rated serious by axe-core.

4 images have 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.

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

Elements with visible text labels do not have matching accessible names. (10 elements).

Your title is 67 characters, so Google will cut it off around 60: “Enzyme Cleaner For Pet Urine | #1 Enzymatic Cleaner in AU | PawLab™”.

There are 2 <h1> headlines (“Pet Enzyme Cleaner & Enzymatic Pet Urine Remover” and “Reviews”). One clear main headline is easier for people and search engines.

The homepage links to 183 pages on pet-lab.com.au and 3 external pages.

There is no https://pawlab.com.au/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.

https://pawlab.com.au/collections/artificial-grass-cleaner took over 3 s to send its HTML from our server.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=17521943&Ver=2&mid=06b0663e-9da1-40aa-a27c-3a6aaeec32b2&bo=1&sid=33857780dc1511f182fe93aa1b9bb993&vid=338595b0dc1511f1af9dad9934bc86f3&vids=1&msclkid=N&pi=918639831&lg.

1 error was logged to the browser console while the page loaded, for example “Uncaught SyntaxError: Identifier 'doRatingSnippetReq' has already been declared”.

The homepage carries about 3,156 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Klaviyo and 3 mores (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 34 cookies, 3 of them by other companies (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 53 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.