Website review, no card needed
campbells.com.au website review
Visit site (opens in a new tab)Reviewed 23 October 202632 issues · 73 checks
This review found 32 issues worth fixing on campbells.com.au, 15 of them high impact, across 73 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
77CClosest competitors among Wix websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 1.4 s |
| May 9, 2026 | 1.4 s |
| May 16, 2026 | 1.4 s |
| May 23, 2026 | 1.3 s |
| May 30, 2026 | 1.3 s |
| Jun 6, 2026 | 1.4 s |
| Jun 13, 2026 | 1.4 s |
| Jun 20, 2026 | 1.4 s |
| Jun 27, 2026 | 1.4 s |
| Jul 4, 2026 | 1.4 s |
| Jul 11, 2026 | 1.4 s |
| Jul 18, 2026 | 1.4 s |
| Jul 25, 2026 | 1.5 s |
| Aug 1, 2026 | 1.5 s |
| Aug 8, 2026 | 1.5 s |
| Aug 15, 2026 | 1.5 s |
| Aug 22, 2026 | 1.4 s |
| Aug 29, 2026 | 1.4 s |
| Sep 5, 2026 | 1.4 s |
| Sep 12, 2026 | 1.4 s |
| Sep 19, 2026 | 1.4 s |
| Sep 26, 2026 | 1.4 s |
| Oct 3, 2026 | 1.4 s |
| Oct 10, 2026 | 1.4 s |
| Oct 17, 2026 | 1.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 138 ms |
| May 9, 2026 | 139 ms |
| May 16, 2026 | 144 ms |
| May 23, 2026 | 146 ms |
| May 30, 2026 | 149 ms |
| Jun 6, 2026 | 149 ms |
| Jun 13, 2026 | 149 ms |
| Jun 20, 2026 | 151 ms |
| Jun 27, 2026 | 150 ms |
| Jul 4, 2026 | 150 ms |
| Jul 11, 2026 | 146 ms |
| Jul 18, 2026 | 146 ms |
| Jul 25, 2026 | 150 ms |
| Aug 1, 2026 | 152 ms |
| Aug 8, 2026 | 154 ms |
| Aug 15, 2026 | 156 ms |
| Aug 22, 2026 | 160 ms |
| Aug 29, 2026 | 162 ms |
| Sep 5, 2026 | 162 ms |
| Sep 12, 2026 | 163 ms |
| Sep 19, 2026 | 163 ms |
| Sep 26, 2026 | 162 ms |
| Oct 3, 2026 | 164 ms |
| Oct 10, 2026 | 162 ms |
| Oct 17, 2026 | 162 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
How it loaded on a phone
1.5 s
3.1 s
4.6 s
6.2 s
7.7 s
9.2 s
10.8 s
12.3 s
Speed
Reduce unused JavaScript
4.2 s · 654 KiBAbout 654 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.2 s faster on a phone.
Use efficient cache lifetimes
1.8 s · 305 KiB11 files are served with short cache lifetimes, so returning visitors download them again (305 KiB).
Google Tag Manager adds 1.1 s
1.1 sGoogle Tag Manager costs a phone 1.1 s of main-thread work and 705 KiB 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.
Mobile performance score: 30
30/100Your mobile performance score is 30 (desktop: 46). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 8.3 s
A phone's processor spends 8.3 s on main-thread work while loading, 5.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3,566 HTML elements
The page has 3,566 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, dynatrace.com and Wix and others), adding 2.7 MB and 3.3 s of main-thread time.
Wix adds 679 ms
679 msWix costs a phone 679 ms of main-thread work and 1.4 MB 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.
dynatrace.com adds 782 ms
782 msdynatrace.com costs a phone 782 ms of main-thread work and 85 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 430 ms. During a long task the page ignores taps.
Legacy JavaScript
350 ms · 34 KiBPolyfills for old browsers add 34 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 350 ms faster on a phone.
Improve image delivery
200 ms · 32 KiB4 images could be 32 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 200 ms faster on a phone.
Duplicated JavaScript
31 KiB31 KiB JavaScript is shipped twice across bundles.
Reduce unused CSS
25 KiBAbout 25 KiB of CSS is downloaded but never applied on this page.
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.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 29 ms
29 msYour server sent the HTML in 29 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 28.5 s
28.5 sYour largest element takes 28.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “mobile_2”. Most of its time is element render delay (11.5 s).
Time to Interactive: 28.6 s
28.6 sThe page becomes fully interactive after 28.6 s. Good is under 3.8 s.
Total Blocking Time: 2.3 s
2.3 sScripts block taps and scrolling for 2.3 s in total while the page loads. Good is under 200 ms.
Speed Index: 7.9 s
7.9 sVisually, the page fills in at 7.9 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.6 s
3.6 sThe first text or image appears after 3.6 s on a phone. Good is under 1.8 s.
Tap response (INP) got 17% slower for real visitors
+17%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 138 ms to 162 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-10-17, real Chrome visitors' largest content (lcp) went from 1.4 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 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.4 s
1.4 sReal visitors wait 1.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 163 ms
163 msReal visitors wait 163 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.03
0.03For real visitors the layout shifts by 0.03 (75th percentile). Good is under 0.1.
Real-user FCP: 0.9 s
0.9 sReal visitors see the first content after 0.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 469 ms
469 msReal visitors wait 469 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.086
0.086The layout barely moves while loading (CLS 0.086, good is under 0.1).
Images and page weight
Page weight: 4.7 MB in 300 requests
4.7 MBYour homepage downloads 4.7 MB in 300 requests on a phone: scripts 2.2 MB (118), other files 1.1 MB (125) and fonts 830 KiB (9). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
mobile_2.png 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).
2 images below the first screen load straight away
2 images further down the page (86 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.3 g of CO₂ per visit
1.34 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.34 g of CO₂e: 160.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
9 text elements with low contrast
9 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Links must have discernible text (6 elements)
Links must have discernible text: 6 elements on the page fail this check, rated serious by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (3 elements)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 3 elements on the page fail this check, rated moderate by axe-core.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 95 images in the HTML carry an alt attribute.
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 4 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Title is short (26 characters)
Your title is only 26 characters: “Home | Campbells Marketing”. Between 30 and 65 characters leaves room to say what you do and for whom.
No social preview image
No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
Only 2 internal links
The homepage links to only 2 pages on your own site, so visitors and crawlers find few routes into the rest of it.
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.
5 checks passed
One H1 headline
Your main headline reads: “Australia’s Trusted Wholesale Partner Since 1933”.
Canonical URL set
The canonical URL is https://www.campbells.com.au/.
Structured data in place
Structured data found: 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://www.campbells.com.au/sitemap.xml.
AI search readiness
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.
3 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 (552 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.campbells.com.au/llms.txt (3 KiB, 3 links), a plain-text guide to the site for AI tools.
Best practices
4 small tap targets
4 of 20 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “The Content-Security-Policy directive name 'Content-Security-Policy-Report-Only:' contains one or more invalid characte…”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 281 words of copy
The homepage carries about 281 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: “Register” and “Register now”.
8 calls to action
The homepage has 8 calls to action, for example “Register now”, “Start Saving Now” and “Download”.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Meta Pixel and 2 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.
26 cookies set on arrival
26Opening the homepage sets 26 cookies (measured from a US location before any click).
No consent tool detected
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.
34 other companies contacted
Loading the homepage contacts 34 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
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 campbells.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
- Wix
- Framework
- React
- Analytics
- Google Tag Manager
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 32 issues on campbells.com.au, including 16 speed issues, 5 SEO issues and 1 conversion gap. 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.