Website review, no card needed
burbank.com.au website review
Visit site (opens in a new tab)Reviewed 2 November 202667 issues · 109 checks
This review found 67 issues worth fixing on burbank.com.au, 33 of them high impact, across 109 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
59FClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 3.2 s |
| May 23, 2026 | 3.3 s |
| May 30, 2026 | 3.3 s |
| Jun 6, 2026 | 3.2 s |
| Jun 13, 2026 | 3.2 s |
| Jun 20, 2026 | 3.2 s |
| Jun 27, 2026 | 3.2 s |
| Jul 4, 2026 | 3.4 s |
| Jul 11, 2026 | 3.5 s |
| Jul 18, 2026 | 3.5 s |
| Jul 25, 2026 | 3.4 s |
| Aug 1, 2026 | 3.4 s |
| Aug 8, 2026 | 3.3 s |
| Aug 15, 2026 | 3.3 s |
| Aug 22, 2026 | 3.4 s |
| Aug 29, 2026 | 3.4 s |
| Sep 5, 2026 | 3.6 s |
| Sep 12, 2026 | 3.6 s |
| Sep 19, 2026 | 3.6 s |
| Sep 26, 2026 | 3.7 s |
| Oct 3, 2026 | 3.7 s |
| Oct 10, 2026 | 3.8 s |
| Oct 17, 2026 | 3.8 s |
| Oct 24, 2026 | 3.8 s |
| Oct 31, 2026 | 3.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 179 ms |
| May 23, 2026 | 181 ms |
| May 30, 2026 | 187 ms |
| Jun 6, 2026 | 183 ms |
| Jun 13, 2026 | 181 ms |
| Jun 20, 2026 | 179 ms |
| Jun 27, 2026 | 180 ms |
| Jul 4, 2026 | 182 ms |
| Jul 11, 2026 | 190 ms |
| Jul 18, 2026 | 201 ms |
| Jul 25, 2026 | 202 ms |
| Aug 1, 2026 | 204 ms |
| Aug 8, 2026 | 212 ms |
| Aug 15, 2026 | 213 ms |
| Aug 22, 2026 | 220 ms |
| Aug 29, 2026 | 223 ms |
| Sep 5, 2026 | 228 ms |
| Sep 12, 2026 | 228 ms |
| Sep 19, 2026 | 233 ms |
| Sep 26, 2026 | 242 ms |
| Oct 3, 2026 | 246 ms |
| Oct 10, 2026 | 267 ms |
| Oct 17, 2026 | 277 ms |
| Oct 24, 2026 | 280 ms |
| Oct 31, 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
1.5 s
3.1 s
4.6 s
6.2 s
7.7 s
9.3 s
10.8 s
12.4 s
Speed
Reduce unused JavaScript
1.9 s · 1.7 MBAbout 1.7 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.9 s faster on a phone.
Use efficient cache lifetimes
1.2 s · 1.0 MB67 files are served with short cache lifetimes, so returning visitors download them again (1.0 MB).
Google Tag Manager adds 1.6 s
1.6 sGoogle Tag Manager costs a phone 1.6 s of main-thread work and 1.4 MB 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.
Font display
1.6 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.6 s).
Render-blocking requests
1.3 s4 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.3 s.
Mobile performance score: 33
33/100Your mobile performance score is 33. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 7.7 s
A phone's processor spends 7.7 s on main-thread work while loading, 4.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, hsappstatic.net and Google CDN and others), adding 3.7 MB and 3.7 s of main-thread time.
Improve image delivery
600 ms · 2.5 MB18 images could be 2.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 600 ms faster on a phone.
hsappstatic.net adds 656 ms
656 mshsappstatic.net costs a phone 656 ms of main-thread work and 711 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.
Google CDN adds 408 ms
408 msGoogle CDN costs a phone 408 ms of main-thread work and 760 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.
realestate.com.au adds 401 ms
401 msrealestate.com.au costs a phone 401 ms of main-thread work and 142 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 336 ms. During a long task the page ignores taps.
Facebook adds 295 ms
295 msFacebook costs a phone 295 ms of main-thread work and 308 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,010 HTML elements
The page has 2,010 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Reduce unused CSS
150 ms · 172 KiBAbout 172 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Duplicated JavaScript
119 KiB119 KiB JavaScript is shipped twice across bundles.
Legacy JavaScript
71 KiBPolyfills for old browsers add 71 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: 218 ms
218 msYour server sent the HTML in 218 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.
Real-user LCP: 4.6 s
4.6 sReal visitors wait 4.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 3.8 s
3.8 sReal visitors see the first content after 3.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 3.2 s
3.2 sReal visitors wait 3.2 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 15.9 s
15.9 sYour largest element takes 15.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 25.6 s
25.6 sVisually, the page fills in at 25.6 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 40.4 s
40.4 sThe page becomes fully interactive after 40.4 s. Good is under 3.8 s.
Total Blocking Time: 2.6 s
2.6 sScripts block taps and scrolling for 2.6 s in total while the page loads. Good is under 200 ms.
Real-user INP: 215 ms
215 msReal visitors wait 215 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.20
0.20For real visitors the layout shifts by 0.20 (75th percentile). Good is under 0.1.
Tap response (INP) got 55% slower for real visitors
+55%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 179 ms to 279 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 2.6 s
2.6 sThe first text or image appears after 2.6 s on a phone. Good is under 1.8 s.
26 images without width and height
26 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) got 18% slower for real visitors
+18%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 3.2 s to 3.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
1 checks passed
Cumulative Layout Shift: 0.032
0.032The layout barely moves while loading (CLS 0.032, good is under 0.1).
Images and page weight
Page weight: 17.6 MB in 249 requests
17.6 MBYour homepage downloads 17.6 MB in 249 requests on a phone: images 11.8 MB (81), scripts 4.7 MB (71) and other files 394 KiB (68). Under 2 MB keeps phones on slow connections fast.
7 images over 500 KB
7 images weigh 5.3 MB together. On a phone connection a single image that size takes seconds.
37 images in older formats
37 images (11.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.
8 images below the first screen load straight away
8 images further down the page (1.4 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
1 image far larger than shown
300 KiB1 image is downloaded at several times the size a phone draws it, for example Full-Width-Image-with-Top-Anchor-Mobile2.jpg at 1,920 px wide, shown at 390 px. Resized copies would save about 300 KiB.
About 5.0 g of CO₂ per visit
4.98 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.98 g of CO₂e: 597.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Invalid ARIA attributes
1 element use ARIA attributes their role does not allow, which confuses screen readers.
Certain ARIA roles must contain particular children (1 element)
Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.
ARIA attributes must conform to valid values (1 element)
ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
Unlabelled dropdowns
1 dropdown has no label.
6 text elements with low contrast
6 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
3 tap targets too small
3 tap targets are too small or too close together to hit reliably with a finger.
Interactive controls must not be nested (2 elements)
Interactive controls must not be nested: 2 elements on the page fail this check, rated serious by axe-core.
ARIA dialog and alertdialog nodes should have an accessible name (1 element)
ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
ARIA input fields must have an accessible name (1 element)
ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
ARIA toggle fields must have an accessible name (1 element)
ARIA toggle fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
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.
51 images without alt text
51 images have no alt text, which hurts accessibility and image search.
105 form fields without a label
105 form fields have no label, so screen readers announce an empty box and autofill guesses.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
20 links without text
20 visible links have no text or label, so screen readers cannot say where they go.
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.
Elements marked as presentational should be consistently ignored (1 element)
Elements marked as presentational should be consistently ignored: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h5, h3 → h5 and h3 → h5), which makes the page harder to scan with a screen reader.
1 checks passed
51 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 70 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 19 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Structured data has 1 problem
Structured data found (Organization and WebSite) but with 1 problem, for example “WebSite: missing name”.
12 links crawlers can't follow
12 links have no real href, so search engines can't follow them.
3 links with vague text
3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
One H1 headline
Your <h1> is empty.
208 internal links, 11 external
The homepage links to 208 pages on burbank.com.au and 11 external pages.
6 checks passed
Meta description: 140 characters
Your meta description is 140 characters: “Burbank Homes is a trusted Melbourne home builder, creating quality new homes across Victoria with flexible designs to …”.
Title: 48 characters
Your title is a healthy 48 characters: “Burbank Homes | Melbourne Home Builder, Victoria”.
Canonical URL set
The canonical URL is https://www.burbank.com.au/.
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.burbank.com.au/sitemap.xml.
AI search readiness
Organization data is thin (2 of 6 facts)
Your Organization JSON-LD is missing logo, 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.
No llms.txt
There is no https://www.burbank.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,847 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page without a title
https://www.burbank.com.au/victoria/promotions has no <title>, so Google invents the link text in results.
1 page points its canonical at the homepage
https://www.burbank.com.au/victoria declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.
2 pages share a title
/ and https://www.burbank.com.au/victoria all use the title “Burbank Homes | Melbourne Home Builder, Victoria”. Search engines can't tell which page to show for a search, so each competes with the others.
6 pages without a meta description
https://www.burbank.com.au/victoria/contact-burbank, https://www.burbank.com.au/victoria/promotions, https://www.burbank.com.au/victoria/new-homes/storey.single, https://www.burbank.com.au/victoria/new-homes/storey.double, https://www.burbank.com.au/victoria/display-homes-for-sale and https://www.burbank.com.au/victoria/h&l have no meta description, so Google writes the search snippet from whatever text it finds.
6 pages slow to respond
https://www.burbank.com.au/victoria/new-homes, https://www.burbank.com.au/victoria/house-and-land, https://www.burbank.com.au/victoria/promotions, https://www.burbank.com.au/victoria/new-homes/storey.single, https://www.burbank.com.au/victoria/new-homes/storey.double and https://www.burbank.com.au/victoria/display-homes-for-sale 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.
3 checks passed
Linked pages load
14 pages of 15 loaded without an error (the rest turned automated requests away).
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.
Best practices
1 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=11005952&tm=gtm002&Ver=2&mid=2de93589-234e-49b7-9b3b-0b0c4a51d39d&bo=1&sid=3a0a3d10d68711f1b9e02bbf856e0ebf&vid=3a0a3a60d68711f1bd0289822175f8ab&vids=1&msclkid=N&pi=91.
15 small tap targets
15 of 38 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.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
Missing source maps
Large scripts ship without source maps.
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
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.
Thin social proof
Social proof on the homepage: 10 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
A 20-field form
Your longest form asks for 20 fields (0 required). Every extra field lowers completion.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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 546 words of copy
The homepage carries about 546 words of visible text.
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “ENQUIRE”.
12 calls to action
The homepage has 12 calls to action, for example “Enquire”, “Enquire Now” and “CONTACT US”.
Analytics in place
Analytics detected: Google Tag Manager and HubSpot.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
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
14 trackers load before any consent
14Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and HubSpot and 9 mores (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.
28 cookies set on arrival
28Opening the homepage sets 28 cookies, 1 of them by other companies (measured from a US location before any click).
59 other companies contacted
Loading the homepage contacts 59 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: HubSpot cookie banner
A consent management tool (HubSpot cookie banner) 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 burbank.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
- Hosting
- Radware Ltd
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 67 issues on burbank.com.au, including 28 speed issues, 4 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.