purityfeed.ca website review

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

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

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

8 third-party services load with your homepage (Shopify, Google Tag Manager and speaz.com and others), adding 960 KiB and 638 ms of main-thread time.

Shopify costs a phone 346 ms of main-thread work and 518 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 images could be 310 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

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

Polyfills for old browsers add 26 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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

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

6 KiB could be saved by minifying CSS.

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.

3 KiB JavaScript is shipped twice across bundles.

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

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

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

Your homepage downloads 3.1 MB in 231 requests on a phone: images 1.2 MB (35), scripts 1.1 MB (87) and other files 695 KiB (85). Under 2 MB keeps phones on slow connections fast.

MOUSE_92ee0434-a3ea-4007-93bc-242880ac922d.jpg 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 further down the page (74 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

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

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

All page content should be contained by landmarks: 2 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.

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

Your title is 70 characters, so Google will cut it off around 60: “Kamloops Farm & Ranch, Pet Store, Garden Centre | Purity Feed Kamloops”.

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

The homepage links to 300 pages on purityfeed.ca and 10 external pages.

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

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

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

https://purityfeed.ca/customer_authentication/redirect, https://purityfeed.ca/collections/rabbit, https://purityfeed.ca/collections/farm-ranch and https://purityfeed.ca/collections/agriculture have no meta description, so Google writes the search snippet from whatever text it finds.

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

https://purityfeed.ca/collections/agricultural-pesticides took over 3 s to send its HTML from our server.

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

2 errors were logged to the browser console while the page loaded, for example “gtag is not defined”.

Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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