Website review, no card needed
aussie.com.au website review
Visit site (opens in a new tab)Reviewed 26 October 202642 issues · 85 checks
This review found 42 issues worth fixing on aussie.com.au, 15 of them high impact, across 85 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
80BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.6 s |
| May 16, 2026 | 2.5 s |
| May 23, 2026 | 2.5 s |
| May 30, 2026 | 2.5 s |
| Jun 6, 2026 | 2.5 s |
| Jun 13, 2026 | 2.5 s |
| Jun 20, 2026 | 2.5 s |
| Jun 27, 2026 | 2.4 s |
| Jul 4, 2026 | 2.4 s |
| Jul 11, 2026 | 2.4 s |
| Jul 18, 2026 | 2.4 s |
| Jul 25, 2026 | 2.4 s |
| Aug 1, 2026 | 2.4 s |
| Aug 8, 2026 | 2.4 s |
| Aug 15, 2026 | 2.5 s |
| Aug 22, 2026 | 2.5 s |
| Aug 29, 2026 | 2.5 s |
| Sep 5, 2026 | 2.5 s |
| Sep 12, 2026 | 2.5 s |
| Sep 19, 2026 | 2.5 s |
| Sep 26, 2026 | 2.5 s |
| Oct 3, 2026 | 2.5 s |
| Oct 10, 2026 | 2.5 s |
| Oct 17, 2026 | 2.5 s |
| Oct 24, 2026 | 2.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 146 ms |
| May 16, 2026 | 146 ms |
| May 23, 2026 | 147 ms |
| May 30, 2026 | 150 ms |
| Jun 6, 2026 | 153 ms |
| Jun 13, 2026 | 154 ms |
| Jun 20, 2026 | 154 ms |
| Jun 27, 2026 | 154 ms |
| Jul 4, 2026 | 154 ms |
| Jul 11, 2026 | 154 ms |
| Jul 18, 2026 | 154 ms |
| Jul 25, 2026 | 156 ms |
| Aug 1, 2026 | 158 ms |
| Aug 8, 2026 | 161 ms |
| Aug 15, 2026 | 162 ms |
| Aug 22, 2026 | 162 ms |
| Aug 29, 2026 | 160 ms |
| Sep 5, 2026 | 159 ms |
| Sep 12, 2026 | 156 ms |
| Sep 19, 2026 | 155 ms |
| Sep 26, 2026 | 156 ms |
| Oct 3, 2026 | 156 ms |
| Oct 10, 2026 | 156 ms |
| Oct 17, 2026 | 157 ms |
| Oct 24, 2026 | 157 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.3 s
2.6 s
3.8 s
5.1 s
6.4 s
7.7 s
8.9 s
10.2 s
Speed
Improve image delivery
1.6 s · 1.4 MB8 images could be 1.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.6 s faster on a phone.
Render-blocking requests
2.3 s6 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.3 s.
Mobile performance score: 41
41/100Your mobile performance score is 41 (desktop: 64). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 4.7 s
A phone's processor spends 4.7 s on main-thread work while loading, 2.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Reduce unused JavaScript
150 ms · 1.5 MBAbout 1.5 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, lendicdn.net and Google Maps and others), adding 2.1 MB and 1.3 s of main-thread time.
Use efficient cache lifetimes
689 KiB15 files are served with short cache lifetimes, so returning visitors download them again (689 KiB).
Google Tag Manager adds 542 ms
542 msGoogle Tag Manager costs a phone 542 ms of main-thread work and 547 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.
lendicdn.net adds 285 ms
285 mslendicdn.net costs a phone 285 ms of main-thread work and 703 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.
18 long tasks on the main thread
18 long tasks block the main thread while loading, the longest for 346 ms. During a long task the page ignores taps.
Google Maps adds 124 ms
124 msGoogle Maps costs a phone 124 ms of main-thread work and 395 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.
Legacy JavaScript
81 KiBPolyfills for old browsers add 81 KiB JavaScript that modern phones do not need.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Minify JavaScript
15 KiB15 KiB could be saved by minifying JavaScript.
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.
1 checks passed
Server response: 369 ms
369 msYour server sent the HTML in 369 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 32.9 s
32.9 sThe page becomes fully interactive after 32.9 s. Good is under 3.8 s.
Speed Index: 9.7 s
9.7 sVisually, the page fills in at 9.7 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 5.9 s
5.9 sYour largest element takes 5.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Total Blocking Time: 981 ms
981 msScripts block taps and scrolling for 981 ms in total while the page loads. Good is under 200 ms.
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.
16 images without width and height
16 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+8%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 146 ms to 157 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-4%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.6 s to 2.5 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.2 s
1.2 sReal visitors wait 1.2 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.01
0.01For real visitors the layout shifts by 0.01 (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: 316 ms
316 msReal visitors wait 316 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.015
0.015The layout barely moves while loading (CLS 0.015, good is under 0.1).
Images and page weight
Page weight: 5.4 MB in 156 requests
5.4 MBYour homepage downloads 5.4 MB in 156 requests on a phone: scripts 3.1 MB (54), images 1.8 MB (30) and fonts 222 KiB (9). Under 2 MB keeps phones on slow connections fast.
4 images in older formats
4 images (844 KiB) 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 far larger than shown
317 KiB5 images are downloaded at several times the size a phone draws them, for example hero-background.avif at 1,320 px wide, shown at 390 px. Resized copies would save about 317 KiB.
3 images below the first screen load straight away
3 images further down the page (527 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.5 g of CO₂ per visit
1.52 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.52 g of CO₂e: 182.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
Links must have discernible text (10 elements)
Links must have discernible text: 10 elements on the page fail this check, rated serious by axe-core.
9 images without alt text
9 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (64 elements)
All page content should be contained by landmarks: 64 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.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
Headings skip levels
Headings skip levels (h1 → h3, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
1 checks passed
34 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 41 WCAG 2.2 A/AA and best-practice rules on the phone render: 34 passed and 7 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (79 characters)
Your title is 79 characters, so Google will cut it off around 60: “#1 Mortgage Broker in AU | Property Listings, Mortgage Brokers & Buyer's Agents”.
Meta description is long (188 characters)
Your meta description is 188 characters; Google truncates after about 160, so the end of your pitch is cut.
82 internal links, 16 external
The homepage links to 82 pages on aussie.com.au and 16 external pages.
6 checks passed
One H1 headline
Your main headline reads: “It starts withthe #1 mortgage broker*the #1 mortgage broker*the #1 mortgage broker*, not missing a better rate, a place…”.
Canonical URL set
The canonical URL is https://www.aussie.com.au/.
Structured data in place
Structured data found: Corporation.
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.aussie.com.au/sitemaps/properties.xml.
AI search readiness
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.
Organization data: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.
Other pages
1 page without a title
https://www.aussie.com.au/home-loans/basics has no <title>, so Google invents the link text in results.
5 linked pages hidden from search
https://www.aussie.com.au/home-loans/basics/borrowing-power, https://www.aussie.com.au/home-loans/basics, https://www.aussie.com.au/contract-analyser, https://www.aussie.com.au/book-appointment and https://www.aussie.com.au/home-loans/basics/new-home are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
2 pages share a title
https://www.aussie.com.au/property and https://www.aussie.com.au/home-loans/basics/new-home all use the title “Search for Properties, Real Estate & Location Insights | Aussie Homes”. Search engines can't tell which page to show for a search, so each competes with the others.
2 pages without a meta description
https://www.aussie.com.au/home-loans/basics and https://www.aussie.com.au/book-appointment have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://www.aussie.com.au/property and https://www.aussie.com.au/home-loans/basics/new-home use the same meta description. A description written for each page earns more clicks.
2 links to non-canonical URLs
Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.aussie.com.au/lp/conveyancing, whose canonical is https://www.aussie.com.au/home-loans/conveyancing. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
9 pages without an H1
https://www.aussie.com.au/home-loans/basics/borrowing-power, https://www.aussie.com.au/buyers-agent, https://www.aussie.com.au/home-loans/basics, https://www.aussie.com.au/contract-analyser, https://www.aussie.com.au/book-appointment and https://www.aussie.com.au/home-loans/basics/new-home and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 45 found) and read each the way a search engine does.
1 checks passed
Linked pages load
14 pages of 15 loaded without an error (the rest turned automated requests away).
Best practices
Browser-reported issues
Chrome logged issues while loading the page (“Content security policy”).
Missing source maps
Large scripts ship without source maps.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
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 analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
About 1,376 words of copy
The homepage carries about 1,376 words of visible text.
3 checks passed
17 calls to action
The homepage has 17 calls to action, for example “Talk to a broker”, “Start getting pre-approved” and “Buy now, sell later”.
Social proof on the page
Social proof on the homepage: 1 customer or partner logo and 1 trust badge.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Amplitude, Google Ads, Google Analytics, Google Tag Manager and Meta Pixel 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.
8 cookies set on arrival
8Opening the homepage sets 8 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.
22 other companies contacted
Loading the homepage contacts 22 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 aussie.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
- Framework
- Next.js
- Hosting
- AWS
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 42 issues on aussie.com.au, including 17 speed issues, 2 SEO issues and 5 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.