Website review, no card needed
pickles.com.au website review
Visit site (opens in a new tab)Reviewed 28 October 202653 issues · 99 checks
This review found 53 issues worth fixing on pickles.com.au, 20 of them high impact, across 99 checks. The most urgent: improve image delivery. 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
65DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 1.6 s |
| May 16, 2026 | 1.6 s |
| May 23, 2026 | 1.6 s |
| May 30, 2026 | 1.5 s |
| Jun 6, 2026 | 1.5 s |
| Jun 13, 2026 | 1.5 s |
| Jun 20, 2026 | 1.5 s |
| Jun 27, 2026 | 1.5 s |
| Jul 4, 2026 | 1.5 s |
| Jul 11, 2026 | 1.5 s |
| Jul 18, 2026 | 1.5 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.5 s |
| Aug 29, 2026 | 1.5 s |
| Sep 5, 2026 | 1.5 s |
| Sep 12, 2026 | 1.5 s |
| Sep 19, 2026 | 1.5 s |
| Sep 26, 2026 | 1.5 s |
| Oct 3, 2026 | 1.6 s |
| Oct 10, 2026 | 1.6 s |
| Oct 17, 2026 | 1.6 s |
| Oct 24, 2026 | 1.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 214 ms |
| May 16, 2026 | 213 ms |
| May 23, 2026 | 213 ms |
| May 30, 2026 | 212 ms |
| Jun 6, 2026 | 213 ms |
| Jun 13, 2026 | 213 ms |
| Jun 20, 2026 | 216 ms |
| Jun 27, 2026 | 218 ms |
| Jul 4, 2026 | 221 ms |
| Jul 11, 2026 | 229 ms |
| Jul 18, 2026 | 238 ms |
| Jul 25, 2026 | 246 ms |
| Aug 1, 2026 | 252 ms |
| Aug 8, 2026 | 253 ms |
| Aug 15, 2026 | 254 ms |
| Aug 22, 2026 | 259 ms |
| Aug 29, 2026 | 258 ms |
| Sep 5, 2026 | 259 ms |
| Sep 12, 2026 | 258 ms |
| Sep 19, 2026 | 260 ms |
| Sep 26, 2026 | 262 ms |
| Oct 3, 2026 | 265 ms |
| Oct 10, 2026 | 271 ms |
| Oct 17, 2026 | 275 ms |
| Oct 24, 2026 | 279 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
0.4 s
0.9 s
1.3 s
1.7 s
2.1 s
2.6 s
3.0 s
3.4 s
Speed
Improve image delivery
1.3 s · 13.0 MB32 images could be 13.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.3 s faster on a phone.
Render-blocking requests
1.8 s10 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.8 s.
Mobile performance score: 26
26/100Your mobile performance score is 26 (desktop: 42). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 4.5 s
A phone's processor spends 4.5 s on main-thread work while loading, 2.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Use efficient cache lifetimes
450 ms · 984 KiB28 files are served with short cache lifetimes, so returning visitors download them again (984 KiB).
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and Insider and others), adding 1.1 MB and 1.2 s of main-thread time.
Reduce unused JavaScript
600 ms · 579 KiBAbout 579 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.
Google Tag Manager adds 623 ms
623 msGoogle Tag Manager costs a phone 623 ms of main-thread work and 546 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.
Reduce unused CSS
600 ms · 76 KiBAbout 76 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.
17 long tasks on the main thread
17 long tasks block the main thread while loading, the longest for 620 ms. During a long task the page ignores taps.
Font display
500 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 500 ms).
Facebook adds 289 ms
289 msFacebook costs a phone 289 ms of main-thread work and 230 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.
2,145 HTML elements
The page has 2,145 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Legacy JavaScript
31 KiBPolyfills for old browsers add 31 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.
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: 9 ms
9 msYour server sent the HTML in 9 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
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.
Largest Contentful Paint: 17.2 s
17.2 sYour largest element takes 17.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Unreserved Defence Auction”.
Time to Interactive: 64.4 s
64.4 sThe page becomes fully interactive after 64.4 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.436
0.436The layout shifts by 0.436 while loading, so content jumps under the reader's thumb. Good is under 0.1.
First Contentful Paint: 3.8 s
3.8 sThe first text or image appears after 3.8 s on a phone. Good is under 1.8 s.
Speed Index: 7.3 s
7.3 sVisually, the page fills in at 7.3 s (Speed Index). Good is under 3.4 s.
Real-user INP: 304 ms
304 msReal visitors wait 304 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.11
0.11For real visitors the layout shifts by 0.11 (75th percentile). Good is under 0.1.
Tap response (INP) got 30% slower for real visitors
+30%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 214 ms to 279 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user TTFB: 806 ms
806 msReal visitors wait 806 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 569 ms
569 msScripts block taps and scrolling for 569 ms in total while the page loads. Good is under 200 ms.
13 images without width and height
13 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
+2%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.6 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user LCP: 2.4 s
2.4 sReal visitors wait 2.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 1.5 s
1.5 sReal visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.
Images and page weight
Page weight: 19.1 MB in 134 requests
19.1 MBYour homepage downloads 19.1 MB in 134 requests on a phone: images 16.9 MB (57), scripts 1.5 MB (30) and fonts 485 KiB (8). Under 2 MB keeps phones on slow connections fast.
5 images over 500 KB
5 images weigh 13.0 MB together. On a phone connection a single image that size takes seconds.
22 images in older formats
22 images (1.7 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.
5 images below the first screen load straight away
5 images further down the page (468 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
1 image far larger than shown
6 KiB1 image is downloaded at several times the size a phone draws it, for example f_auto,q_80 at 920 px wide, shown at 295 px. Resized copies would save about 6 KiB.
About 5.4 g of CO₂ per visit
5.40 gBy the Sustainable Web Design model, a visit to your homepage emits about 5.40 g of CO₂e: 648.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Certain ARIA roles must contain particular children (2 elements)
Certain ARIA roles must contain particular children: 2 elements on the page fail this check, rated critical by axe-core.
2 buttons without a name
2 buttons have no accessible name, so screen readers announce just “button”.
5 text elements with low contrast
5 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
ARIA input fields must have an accessible name (2 elements)
ARIA input fields must have an accessible name: 2 elements on the page fail this check, rated serious by axe-core.
<html> element must have a lang attribute (1 element)
<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (78 elements)
All page content should be contained by landmarks: 78 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
13 form fields without a label
13 form fields have no label, so screen readers announce an empty box and autofill guesses.
10 links without text
10 visible links have no text or label, so screen readers cannot say where they go.
No page language
The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h6, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
33 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 45 WCAG 2.2 A/AA and best-practice rules on the phone render: 33 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
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
Structured data has 1 problem
Structured data found (LocalBusiness) but with 1 problem, for example “LocalBusiness: sameAs is not an absolute URL ("pickles.com.au")”.
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.
15 links crawlers can't follow
15 links have no real href, so search engines can't follow them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
379 internal links, 11 external
The homepage links to 379 pages on pickles.com.au and 11 external pages.
5 checks passed
Meta description: 155 characters
Your meta description is 155 characters: “Wide range of car auctions in Australia. Buy, sell used cars, trucks, trailers, government cars, damaged cars, machiner…”.
One H1 headline
Your main headline reads: “Thousands of items waiting to be discovered – with Pickles”.
Title: 61 characters
Your title is a healthy 61 characters: “Online Auctions. Buy & Sell Cars, Trucks, Damage - Pickles AU”.
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.pickles.com.au/api/services/sitemap/v1/sitemap.
AI search readiness
No llms.txt
There is no https://www.pickles.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.
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.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, sameAs (social profiles) and contact details; logo and description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (2,322 words), so crawlers that don't run JavaScript still read it.
Other pages
6 pages slow to respond
https://www.pickles.com.au/pickles-cars, https://www.pickles.com.au/government-vehicles, https://www.pickles.com.au/campaigns/electric-hybrid-cars, https://www.pickles.com.au/campaigns/prestige-luxury, https://www.pickles.com.au/pickles-industrial and https://www.pickles.com.au/campaigns/agricultural took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 73 found) and read each the way a search engine does.
7 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 15 pages that loaded have a meta description.
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
10 broken images
10 images failed to load on a phone, for example https://www.pickles.com.au/.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://website-content.prd.pickles.com.au/aksprod/assets/toolkit/styles/toolkit.css?v1792…”.
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
97 of 99 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
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 map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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 593 words of copy
The homepage carries about 593 words of visible text.
7 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Buy” and “START SELLING”.
40 calls to action
The homepage has 40 calls to action, for example “Buy”, “Cars to Buy Now” and “Trucks to Buy Now”.
1 short form
A short form (3 fields at most) is right on the homepage.
Social proof on the page
Social proof on the homepage: 11 testimonial or review blocks and 10 customer or partner logos.
Analytics in place
Analytics detected: Google Tag Manager and Cloudflare Web Analytics.
Opening hours shown
Your opening hours are on the homepage.
LocalBusiness structured data
Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads FullStory, Google Ads, Google Analytics, Google Tag Manager and LinkedIn Insight and 3 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.
32 other companies contacted
Loading the homepage contacts 32 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 pickles.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
- Analytics
- Google Tag Manager | Microsoft Clarity
- Hosting
- Cloudflare
Company
- Founded
- 1964
- Headquarters
- Sydney
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 53 issues on pickles.com.au, including 25 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.