petland.ca website review

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

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

8 third-party services load with your homepage (pxucdn.com, productcustomizer.com and maestra-static.io and others), adding 1.0 MB and 1.6 s of main-thread time.

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

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

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

pxucdn.com costs a phone 606 ms of main-thread work and 88 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.

productcustomizer.com costs a phone 369 ms of main-thread work and 25 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.

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

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

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

Shopify costs a phone 183 ms of main-thread work and 502 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.

9 KiB could be saved by minifying JavaScript.

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

13 KiB JavaScript is shipped twice across bundles.

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

The page becomes fully interactive after 18.1 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 image.

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

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

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

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

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

Your homepage downloads 4.0 MB in 307 requests on a phone: images 1.4 MB (41), scripts 1.3 MB (148) and other files 782 KiB (94). Under 2 MB keeps phones on slow connections fast.

Free_Shipping_Hero_Banner_dee46eef-d221-42db-a8a6-c8dd21554e 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).

3 images are downloaded at several times the size a phone draws them, for example 2026Nov-Nutrience-NW.jpg at 1,600 px wide, shown at 390 px. Resized copies would save about 167 KiB.

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

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

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

All page content should be contained by landmarks: 14 elements on the page fail this check, rated moderate by axe-core.

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.

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

Your title is 87 characters, so Google will cut it off around 60: “Canada’s Trusted Source for Pets, Pet Products & Pet Care Information! – Petland Canada”.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 642 pages on petland.ca and 2 external pages.

The HTML your server sends has 216 of the 478 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

https://www.petland.ca/pages/wishlist, https://www.petland.ca/collections/reptile-food and https://www.petland.ca/collections/dog-raw-frozen-food have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.petland.ca/collections/dog-food-center, https://www.petland.ca/collections/dog-food-center/Dry-Food, https://www.petland.ca/collections/dog-food-center/Wet-Food, https://www.petland.ca/collections/dog-food-center/Freeze-Dried-Food, https://www.petland.ca/collections/dog-food-center/Food-Toppers and https://www.petland.ca/collections/dog-food-center/Dehydrated-Food use the same meta description. A description written for each page earns more clicks.

Your homepage links to 5 pages by a URL that isn't their canonical one, for example https://www.petland.ca/collections/dog-food-center/Dry-Food, whose canonical is https://www.petland.ca/collections/dog-food-center/dry-food. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.petland.ca/pages/free-shipping-with-100-orders, https://www.petland.ca/pages/wishlist, https://www.petland.ca/collections/dog, https://www.petland.ca/collections/cat, https://www.petland.ca/collections/bird and https://www.petland.ca/collections/fish and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.petland.ca/pages/free-shipping-with-100-orders, https://www.petland.ca/pages/wishlist, https://www.petland.ca/collections/dog, https://www.petland.ca/collections/cat, https://www.petland.ca/collections/bird and https://www.petland.ca/collections/fish 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 196 found) and read each the way a search engine does.

1 error was logged to the browser console while the page loaded, for example “xLocalizationForm is not defined”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

Large scripts ship without source maps.

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

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

Opening the homepage sets 5 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 16 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.