Website review, no card needed
chifley.com.au website review
Visit site (opens in a new tab)Reviewed 21 October 202653 issues · 85 checks
This review found 53 issues worth fixing on chifley.com.au, 20 of them high impact, across 85 checks. The most urgent: render-blocking requests. 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
66DClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
0.5 s
1.0 s
1.6 s
2.1 s
2.6 s
3.1 s
3.6 s
4.2 s
Speed
Render-blocking requests
3.9 s13 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.9 s.
Font display
1.2 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.2 s).
Mobile performance score: 37
37/100Your mobile performance score is 37 (desktop: 20). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Improve image delivery
19.9 MB9 images could be 19.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Reduce unused JavaScript
560 ms · 956 KiBAbout 956 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 560 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (YouTube, Google Tag Manager and Clarity and others), adding 1.7 MB and 1.1 s of main-thread time.
Reduce unused CSS
600 ms · 242 KiBAbout 242 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.
Use efficient cache lifetimes
550 ms · 217 KiB5 files are served with short cache lifetimes, so returning visitors download them again (217 KiB).
YouTube adds 478 ms
478 msYouTube costs a phone 478 ms of main-thread work and 984 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.
Main-thread work: 3.3 s
A phone's processor spends 3.3 s on main-thread work while loading, 1.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Google Tag Manager adds 254 ms
254 msGoogle Tag Manager costs a phone 254 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.
Minify CSS
260 ms · 35 KiB35 KiB could be saved by minifying CSS.
13 long tasks on the main thread
13 long tasks block the main thread while loading, the longest for 208 ms. During a long task the page ignores taps.
Minify JavaScript
110 ms · 7 KiB7 KiB could be saved by minifying JavaScript.
Legacy JavaScript
21 KiBPolyfills for old browsers add 21 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.
1 checks passed
Server response: 173 ms
173 msYour server sent the HTML in 173 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 23.1 s
23.1 sThe page becomes fully interactive after 23.1 s. Good is under 3.8 s.
Speed Index: 12.6 s
12.6 sVisually, the page fills in at 12.6 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 4.3 s
4.3 sThe first text or image appears after 4.3 s on a phone. Good is under 1.8 s.
Cumulative Layout Shift: 0.367
0.367The layout shifts by 0.367 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Largest Contentful Paint: 4.5 s
4.5 sYour largest element takes 4.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “AN ICONIC SYDNEY ADDRESS DEFINING THE CITY'S SKYLINE. CHIFL…”. Most of its time is element render delay (2.6 s).
Total Blocking Time: 449 ms
449 msScripts block taps and scrolling for 449 ms in total while the page loads. Good is under 200 ms.
7 images without width and height
7 images have no width and height attributes, so the layout jumps as each one loads.
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.
Images and page weight
Page weight: 27.5 MB in 71 requests
27.5 MBYour homepage downloads 27.5 MB in 71 requests on a phone: images 25.1 MB (18), scripts 1.8 MB (24) and stylesheets 235 KiB (7). Under 2 MB keeps phones on slow connections fast.
8 images over 500 KB
8 images weigh 18.7 MB together. On a phone connection a single image that size takes seconds.
8 images far larger than shown
12.0 MB8 images are downloaded at several times the size a phone draws them, for example 1.png at 2,000 px wide, shown at 325 px. Resized copies would save about 12.0 MB.
8 images in older formats
8 images (18.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 (18.7 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 7.8 g of CO₂ per visit
7.78 gBy the Sustainable Web Design model, a visit to your homepage emits about 7.78 g of CO₂e: 933.7 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”.
Input buttons must have discernible text (1 element)
Input buttons must have discernible text: 1 element on the page fails this check, rated critical by axe-core.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
<svg> elements with an img or image role must have alternative text (1 element)
<svg> elements with an img or image role must have alternative text: 1 element on the page fails this check, rated serious by axe-core.
19 images without alt text
19 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (14 elements)
All page content should be contained by landmarks: 14 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.
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.
9 links without text
9 visible links have no text or label, so screen readers cannot say where they go.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
Headings should not be empty (2 elements)
Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h4, h2 → h6 and h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
41 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: 41 passed and 11 failed. 2 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.
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (4 characters)
Your title is only 4 characters: “Home”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No social preview image
No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No XML sitemap
No XML sitemap at https://www.chifley.com.au/sitemap.xml, so Google discovers your pages only by following links.
10 links crawlers can't follow
10 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.
14 internal links, 3 external
The homepage links to 14 pages on chifley.com.au and 3 external pages.
2 checks passed
Canonical URL set
The canonical URL is https://www.chifley.com.au/.
robots.txt in place
robots.txt is in place.
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.
No llms.txt
There is no https://www.chifley.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 (832 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page points its canonical at the homepage
https://www.chifley.com.au/home 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.chifley.com.au/home all use the title “Home”. Search engines can't tell which page to show for a search, so each competes with the others.
9 pages without a meta description
https://www.chifley.com.au/home, https://www.chifley.com.au/contact, https://www.chifley.com.au/precinct-overview, https://www.chifley.com.au/retail, https://www.chifley.com.au/leasing and https://www.chifley.com.au/sustainability and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.
7 pages without an H1
https://www.chifley.com.au/home, https://www.chifley.com.au/contact, https://www.chifley.com.au/precinct-overview, https://www.chifley.com.au/retail, https://www.chifley.com.au/leasing and https://www.chifley.com.au/sustainability and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.
9 internal pages checked
We fetched 9 pages linked from your homepage and read each the way a search engine does.
3 checks passed
Linked pages load
All 9 pages we checked loaded without an error.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 9 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.
3 small tap targets
3 of 14 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 “Failed to load resource: the server responded with a status of 404 ()”.
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
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 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 876 words of copy
The homepage carries about 876 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: “CONTACT”.
3 calls to action
The homepage has 3 calls to action, for example “CONTACT” and “Contact”.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel and Microsoft Clarity.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity (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.
9 cookies set on arrival
9Opening the homepage sets 9 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.
17 other companies contacted
Loading the homepage contacts 17 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 chifley.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
- Sitefinity 15.4.8636.0 DX
- Framework
- Bootstrap
- Analytics
- Google Analytics | Google Tag Manager | Microsoft Clarity
- Hosting
- Azure
Company
- Founded
- 1992
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 chifley.com.au, including 18 speed issues, 7 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.