purina.com.au website review

About 1.4 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.7 s faster on a phone.

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

13 images could be 2.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.8 s faster on a phone.

41 files are served with short cache lifetimes, so returning visitors download them again (1.2 MB).

Google Tag Manager costs a phone 1.1 s of main-thread work and 1.5 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

Your mobile performance score is 13 (desktop: 41). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

8 third-party services load with your homepage (Google Tag Manager, Facebook and sprinklr.com and others), adding 2.9 MB and 1.9 s of main-thread time.

99 KiB could be saved by minifying JavaScript.

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

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

About 82 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

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

sprinklr.com costs a phone 146 ms of main-thread work and 468 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.

Optanon costs a phone 111 ms of main-thread work and 332 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.

41 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 200 ms faster on a phone.

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

12 KiB could be saved by minifying CSS.

Desktop scores 41 but mobile only 13. A gap that wide usually means heavy scripts and images that hit phones hardest.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Your largest element takes 14.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “A cheerful couple enjoying quality time with their golden r…”.

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

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

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

The layout shifts by 0.682 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

16 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-24, real Chrome visitors' tap response (inp) went from 144 ms to 139 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 5.9 MB in 117 requests on a phone: scripts 2.9 MB (41), images 2.5 MB (31) and fonts 225 KiB (13). Under 2 MB keeps phones on slow connections fast.

12 images (2.4 MB) are 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.

9 images further down the page (1.9 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

4 images are downloaded at several times the size a phone draws them, for example 15575250567198.jpg at 515 px wide, shown at 159 px. Resized copies would save about 36 KiB.

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

1 tap target is too small or too close together to hit reliably with a finger.

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

Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.

Structured data found (Article) but with 6 problems, for example “Article: missing name”.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 182 pages on purina.com.au and 8 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.

Your homepage links to 6 pages by a URL that isn't their canonical one, for example /finding-a-pet, whose canonical is /finding-a-pet.html. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/finding-a-pet/dog-articles-advice and /finding-a-pet/cat-articles-advice have no <h1> headline, so visitors and search engines get no clear main topic.

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

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

3 of 13 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

The page has no <!DOCTYPE html>, so browsers render it in quirks mode.

1 image is served at too low a resolution for sharp phone screens.

Chrome logged issues while loading the page (“Cookie”).

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

purina.com.au has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

purina.com.au's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Amazon Ads, Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 11 cookies, 1 of them by other companies (measured from a US location before any click).

Loading the homepage contacts 22 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.