Website review, no card needed
adcock.com.au website review
Visit site (opens in a new tab)Reviewed 17 November 202641 issues · 81 checks
This review found 41 issues worth fixing on adcock.com.au, 18 of them high impact, across 81 checks. The most urgent: use efficient cache lifetimes. 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
74CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 2.1 s |
| Jun 6, 2026 | 2.0 s |
| Jun 13, 2026 | 2.1 s |
| Aug 29, 2026 | 2.2 s |
| Sep 12, 2026 | 1.8 s |
| Sep 19, 2026 | 1.7 s |
| Oct 31, 2026 | 1.9 s |
| Nov 7, 2026 | 2.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 87 ms |
| Jun 6, 2026 | 94 ms |
| Jun 13, 2026 | 95 ms |
| Aug 29, 2026 | 103 ms |
| Sep 12, 2026 | 75 ms |
| Sep 19, 2026 | 71 ms |
| Oct 31, 2026 | 79 ms |
| Nov 7, 2026 | 80 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.6 s
1.3 s
1.9 s
2.6 s
3.2 s
3.8 s
4.5 s
5.1 s
Speed
Use efficient cache lifetimes
8.0 s · 4.2 MB55 files are served with short cache lifetimes, so returning visitors download them again (4.2 MB).
Improve image delivery
7.1 s · 3.4 MB18 images could be 3.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 7.1 s faster on a phone.
Render-blocking requests
3.3 s61 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.3 s.
Reduce unused JavaScript
450 ms · 648 KiBAbout 648 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.
Mobile performance score: 60
60/100Your mobile performance score is 60. 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 (YouTube, reapit.website and Google Tag Manager and others), adding 2.2 MB and 715 ms of main-thread time.
Reduce unused CSS
450 ms · 194 KiBAbout 194 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
YouTube adds 395 ms
395 msYouTube costs a phone 395 ms of main-thread work and 1,000 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.
Font display
350 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 350 ms).
reapit.website adds 168 ms
168 msreapit.website costs a phone 168 ms of main-thread work and 960 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 97 ms. During a long task the page ignores taps.
Legacy JavaScript
11 KiBPolyfills for old browsers add 11 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.
2 checks passed
Main-thread work: 1.7 s
A phone's processor spends 1.7 s on main-thread work while loading, 870 ms of it running JavaScript. That is comfortably low.
Server response: 3 ms
3 msYour server sent the HTML in 3 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 12.0 s
12.0 sYour largest element takes 12.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 16.2 s
16.2 sThe page becomes fully interactive after 16.2 s. Good is under 3.8 s.
Speed Index: 10.7 s
10.7 sVisually, the page fills in at 10.7 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.0 s
3.0 sThe first text or image appears after 3.0 s on a phone. Good is under 1.8 s.
Largest content (LCP) held steady for real visitors
-4%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 2.1 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
3 checks passed
Tap response (INP) got 12% faster for real visitors
-12%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 87 ms to 80 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 93 ms
93 msScripts block the page for only 93 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 6.1 MB in 123 requests
6.1 MBYour homepage downloads 6.1 MB in 123 requests on a phone: images 4.3 MB (22), scripts 1.2 MB (25) and stylesheets 276 KiB (61). Under 2 MB keeps phones on slow connections fast.
2 images over 500 KB
2 images weigh 2.0 MB together. On a phone connection a single image that size takes seconds.
4 images far larger than shown
2.3 MB4 images are downloaded at several times the size a phone draws them, for example Homepage-Photo-1-scaled.jpg at 2,560 px wide, shown at 390 px. Resized copies would save about 2.3 MB.
16 images in older formats
16 images (4.0 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.
4 images below the first screen load straight away
4 images further down the page (511 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.7 g of CO₂ per visit
1.72 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.72 g of CO₂e: 206.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Hidden but focusable
34 elements hidden from screen readers can still receive keyboard focus.
Elements must only use permitted ARIA attributes (3 elements)
Elements must only use permitted ARIA attributes: 3 elements on the page fail this check, rated serious by axe-core.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
8 images without alt text
8 images have no alt text, which hurts accessibility and image search.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
21 form fields without a label
21 form fields have no label, so screen readers announce an empty box and autofill guesses.
15 links without text
15 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h2 → h5), which makes the page harder to scan with a screen reader.
1 checks passed
49 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 58 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 9 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (25 characters)
Your title is only 25 characters: “Home - Adcock Real Estate”. Between 30 and 65 characters leaves room to say what you do and for whom.
5 links with vague text
5 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
120 internal links, 10 external
The homepage links to 120 pages on adcock.com.au and 10 external pages.
6 checks passed
Meta description: 160 characters
Your meta description is 160 characters: “Real Estate Agents and Property Managers in Balhannah, Ashton, Echunga, Glenside, Harrogate, Lobethal, Mylor, Nairne, O…”.
Canonical URL set
The canonical URL is https://www.adcock.com.au/.
Structured data in place
Structured data found: BreadcrumbList, Organization, Person, WebPage and WebSite.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
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.adcock.com.au/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
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,213 words), so crawlers that don't run JavaScript still read it.
Other pages
8 linked pages are broken
Your homepage links to https://www.adcock.com.au/buy/buyer-registration, https://www.adcock.com.au/buy/letter-of-offer, https://www.adcock.com.au/buy/sales-team, https://www.adcock.com.au/sell/recent-sales, https://www.adcock.com.au/resources and https://www.adcock.com.au/rent/appraisal and 2 others, which answer with an error. Visitors hit a dead end and search engines drop them.
5 pages without a meta description
https://www.adcock.com.au/buy/properties-for-sale, https://www.adcock.com.au/buy/open-for-inspection, https://www.adcock.com.au/buy/best-final-offer, https://www.adcock.com.au/sell/appraisal and https://www.adcock.com.au/rent/properties-for-rent have no meta description, so Google writes the search snippet from whatever text it finds.
5 pages without an H1
https://www.adcock.com.au/buy/properties-for-sale, https://www.adcock.com.au/buy/best-final-offer, https://www.adcock.com.au/sell/appraisal, https://www.adcock.com.au/sell/sold-prices and https://www.adcock.com.au/rent/properties-for-rent have no <h1> headline, so visitors and search engines get no clear main topic.
3 pages slow to respond
https://www.adcock.com.au/buy/open-for-inspection, https://www.adcock.com.au/buy/best-final-offer and https://www.adcock.com.au/rent/properties-for-rent took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 38 found) and read each the way a search engine does.
4 checks passed
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Titles are unique
Every page we checked has its own title.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 7 pages that loaded have a <title>.
Best practices
5 third-party cookies
5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_INVALID_URL”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
87 of 95 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 26 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
A 8-field form
Your longest form asks for 8 fields (0 required). Every extra field lowers completion.
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 1,478 words of copy
The homepage carries about 1,478 words of visible text.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “BUY” and “Maintenance Request”.
17 calls to action
The homepage has 17 calls to action, for example “BUY”, “Maintenance Request” and “Contact Us”.
Analytics in place
Analytics detected: Google Analytics.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (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.
3 cookies set on arrival
3Opening the homepage sets 3 cookies, 1 of them by other companies (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.
12 other companies contacted
Loading the homepage contacts 12 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 adcock.com.au, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Go beyond the website
What your $25 Growth Playbook adds
This review found 41 issues on adcock.com.au, including 14 speed issues, 3 SEO issues and 3 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.