Website review, no card needed

advancepet.com.au logo

advancepet.com.au website review

Visit site (opens in a new tab)Reviewed 17 November 202641 issues · 91 checks

This review found 41 issues worth fixing on advancepet.com.au, 13 of them high impact, across 91 checks. The most urgent: page weight: 25.1 MB in 106 requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
2.6 s1.5 sJun 6Nov 142.0 s
Show as table
DateReal-visitor load time (LCP)
Jun 6, 20261.8 s
Jun 13, 20262.3 s
Jun 20, 20262.3 s
Jun 27, 20262.5 s
Aug 29, 20262.0 s
Sep 5, 20261.7 s
Sep 12, 20261.6 s
Sep 19, 20261.6 s
Sep 26, 20261.6 s
Oct 3, 20261.7 s
Oct 10, 20261.7 s
Oct 17, 20261.7 s
Oct 24, 20261.7 s
Oct 31, 20261.8 s
Nov 7, 20261.9 s
Nov 14, 20262.0 s
Real-visitor tap response (INP)75th percentile, phones
120 ms92 msSep 5Nov 14108 ms
Show as table
DateReal-visitor tap response (INP)
Sep 5, 2026102 ms
Sep 12, 2026110 ms
Sep 19, 2026113 ms
Sep 26, 2026113 ms
Oct 3, 2026117 ms
Oct 10, 2026104 ms
Oct 17, 2026101 ms
Oct 24, 202695 ms
Oct 31, 202697 ms
Nov 7, 2026103 ms
Nov 14, 2026108 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of advancepet.com.au (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. advancepet.com.au at 0.5 s0.5 s
  2. advancepet.com.au at 1.0 s1.0 s
  3. advancepet.com.au at 1.5 s1.5 s
  4. advancepet.com.au at 2.0 s2.0 s
  5. advancepet.com.au at 2.5 s2.5 s
  6. advancepet.com.au at 3.1 s3.1 s
  7. advancepet.com.au at 3.6 s3.6 s
  8. advancepet.com.au at 4.1 s4.1 s

Speed

8 to fix85
  • Render-blocking requests

    1.0 s

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

  • Improve image delivery

    23.0 MB

    24 images could be 23.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Mobile performance score: 85

    85/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and Clarity and others), adding 1.1 MB and 602 ms of main-thread time.

  • Reduce unused JavaScript

    457 KiB

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

  • Reduce unused CSS

    300 ms · 86 KiB

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

  • Use efficient cache lifetimes

    352 KiB

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

  • Google Tag Manager adds 282 ms

    282 ms

    Google Tag Manager costs a phone 282 ms of main-thread work and 523 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.

  • 6 long tasks on the main thread

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

  • Font display

    100 ms

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

  • Document request latency

    69 KiB

    The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

  • Legacy JavaScript

    20 KiB

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

  • Chained critical requests

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

2 checks passed
  • Main-thread work: 1.6 s

    A phone's processor spends 1.6 s on main-thread work while loading, 809 ms of it running JavaScript. That is comfortably low.

  • Server response: 18 ms

    18 ms

    Your server sent the HTML in 18 ms, well inside Google's 600 ms guideline.

Core Web Vitals

4 to fix100
  • Speed Index: 20.0 s

    20.0 s

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

  • Time to Interactive: 36.1 s

    36.1 s

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

  • Largest Contentful Paint: 2.7 s

    2.7 s

    Your largest element takes 2.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “From expert nutrition to total wellbeing, we're here to sup…”. Most of its time is element render delay (2.4 s).

  • 10 images without width and height

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

  • Tap response (INP) held steady for real visitors

    0%

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

  • Largest content (LCP) held steady for real visitors

    -2%

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

8 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.8 s

    1.8 s

    Real visitors wait 1.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 91 ms

    91 ms

    Real visitors wait 91 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.01

    0.01

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

  • Real-user FCP: 1.7 s

    1.7 s

    Real visitors see the first content after 1.7 s (75th percentile). Good is under 1.8 s.

  • First Contentful Paint: 1.7 s

    1.7 s

    The first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.

  • Total Blocking Time: 104 ms

    104 ms

    Scripts block the page for only 104 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0.042

    0.042

    The layout barely moves while loading (CLS 0.042, good is under 0.1).

Images and page weight

5 to fix18
  • Page weight: 25.1 MB in 106 requests

    25.1 MB

    Your homepage downloads 25.1 MB in 106 requests on a phone: images 23.5 MB (45), scripts 1.2 MB (20) and fonts 144 KiB (7). Under 2 MB keeps phones on slow connections fast.

  • 14 images over 500 KB

    14 images weigh 22.2 MB together. On a phone connection a single image that size takes seconds.

  • 14 images far larger than shown

    18.7 MB

    14 images are downloaded at several times the size a phone draws them, for example Dry dog food_0.png at 2,000 px wide, shown at 211 px. Resized copies would save about 18.7 MB.

  • 24 images in older formats

    24 images (23.5 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.

  • 15 images below the first screen load straight away

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

  • About 7.1 g of CO₂ per visit

    7.11 g

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

Accessibility

12 to fixGoogle 7184
  • Invalid ARIA attributes

    8 elements use ARIA attributes their role does not allow, which confuses screen readers.

  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 1 text element with low contrast

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

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • Orphan list items

    Some list items are not inside a list.

  • 8 images without alt text

    8 images have no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (2 elements)

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

  • Contentinfo landmark should not be contained in another landmark (1 element)

    Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Document should not have more than one contentinfo landmark (1 element)

    Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    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.

  • The skip-link target should exist and be focusable (1 element)

    The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

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

1 checks passed
  • 43 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 12 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 7788
  • Meta description is long (172 characters)

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

  • No social preview image

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

  • 13 links crawlers can't follow

    13 links have no real href, so search engines can't follow them.

  • 1 link with vague text

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

  • No X (Twitter) card tag

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

  • 157 internal links, 21 external

    The homepage links to 157 pages on advancepet.com.au and 21 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “From expert nutrition to total wellbeing, we're here to support your pet through every life stage”.

  • Title: 61 characters

    Your title is a healthy 61 characters: “Premium Dog & Cat Food Australia | Vet Recommended | ADVANCE™”.

  • Canonical URL set

    The canonical URL is https://advancepet.com.au/index.php/.

  • Structured data in place

    Structured data found: WebPage and WebSite.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://advancepet.com.au/sitemap.xml.

AI search readiness

1 to fix88
  • No Organization structured data

    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.

  • No llms.txt

    There is no https://advancepet.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.

2 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,063 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 1 page without a meta description

    https://advancepet.com.au/index.php/food-recommender has no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 links to non-canonical URLs

    Your homepage links to 15 pages by a URL that isn't their canonical one, for example https://advancepet.com.au/index.php/dog/nutrition, whose canonical is https://advancepet.com.au/dog/nutrition. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 4 pages slow to respond

    https://advancepet.com.au/index.php/collections/dogs, https://advancepet.com.au/index.php/food-recommender, https://advancepet.com.au/index.php/cat/nutrition and https://advancepet.com.au/index.php/cat/wellbeing took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

3 to fixGoogle 7785
  • 85 small tap targets

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

  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • 3 JavaScript errors while loading

    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 404 ()”.

  • Browser-reported issues

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • No social proof

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

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

  • About 861 words of copy

    The homepage carries about 861 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Where To Buy” and “Shop Dogs”.

  • 11 calls to action

    The homepage has 11 calls to action, for example “Where To Buy”, “Shop Dogs” and “Shop Cats”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity and 1 more (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.

  • 11 cookies set on arrival

    11

    Opening the homepage sets 11 cookies (measured from a US location before any click).

  • 24 other companies contacted

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

1 checks passed
  • Consent tool: OneTrust

    A consent management tool (OneTrust) loads with the page.

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at advancepet.com.au, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
Drupal
Framework
jQuery
Analytics
Google Tag Manager
Hosting
CloudFront

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 41 issues on advancepet.com.au, including 12 speed issues, 4 SEO issues and 2 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25