Website review, no card needed

hia.com.au logo

hia.com.au website review

Visit site (opens in a new tab)Reviewed 30 October 202639 issues · 72 checks

This review found 39 issues worth fixing on hia.com.au, 15 of them high impact, across 72 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
4.9 s3.0 sMay 9Oct 243.6 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20264.0 s
May 16, 20264.1 s
May 23, 20264.2 s
May 30, 20264.2 s
Jun 6, 20264.3 s
Jun 13, 20264.4 s
Jun 20, 20264.3 s
Jun 27, 20264.4 s
Jul 4, 20264.5 s
Jul 11, 20264.4 s
Jul 18, 20264.5 s
Jul 25, 20264.6 s
Aug 1, 20264.4 s
Aug 8, 20264.2 s
Aug 15, 20263.9 s
Aug 22, 20263.3 s
Aug 29, 20263.2 s
Sep 5, 20263.2 s
Sep 12, 20263.3 s
Sep 19, 20263.4 s
Sep 26, 20263.4 s
Oct 3, 20263.6 s
Oct 10, 20263.6 s
Oct 17, 20263.6 s
Oct 24, 20263.6 s
Real-visitor tap response (INP)75th percentile, phones
176 ms113 msMay 9Oct 24162 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026120 ms
May 16, 2026121 ms
May 23, 2026122 ms
May 30, 2026126 ms
Jun 6, 2026130 ms
Jun 13, 2026137 ms
Jun 20, 2026139 ms
Jun 27, 2026137 ms
Jul 4, 2026143 ms
Jul 11, 2026145 ms
Jul 18, 2026141 ms
Jul 25, 2026140 ms
Aug 1, 2026134 ms
Aug 8, 2026136 ms
Aug 15, 2026138 ms
Aug 22, 2026146 ms
Aug 29, 2026155 ms
Sep 5, 2026154 ms
Sep 12, 2026161 ms
Sep 19, 2026162 ms
Sep 26, 2026162 ms
Oct 3, 2026165 ms
Oct 10, 2026168 ms
Oct 17, 2026169 ms
Oct 24, 2026162 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

Full-page screenshot of hia.com.au (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. hia.com.au at 1.2 s1.2 s
  2. hia.com.au at 2.3 s2.3 s
  3. hia.com.au at 3.5 s3.5 s
  4. hia.com.au at 4.7 s4.7 s
  5. hia.com.au at 5.8 s5.8 s
  6. hia.com.au at 7.0 s7.0 s
  7. hia.com.au at 8.1 s8.1 s
  8. hia.com.au at 9.3 s9.3 s

Speed

13 to fix20
  • Reduce unused JavaScript

    3.6 s · 796 KiB

    About 796 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.6 s faster on a phone.

  • Use efficient cache lifetimes

    2.8 s · 682 KiB

    12 files are served with short cache lifetimes, so returning visitors download them again (682 KiB).

  • Render-blocking requests

    2.3 s

    4 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.3 s.

  • Mobile performance score: 20

    20/100

    Your mobile performance score is 20. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and Google Maps and others), adding 1.1 MB and 1.2 s of main-thread time.

  • Improve image delivery

    1.2 MB

    6 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Reduce unused CSS

    600 ms · 105 KiB

    About 105 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.

  • 11 long tasks on the main thread

    11 long tasks block the main thread while loading, the longest for 655 ms. During a long task the page ignores taps.

  • Google Tag Manager adds 570 ms

    570 ms

    Google Tag Manager costs a phone 570 ms of main-thread work and 383 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

    450 ms · 49 KiB

    Polyfills for old browsers add 49 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 450 ms faster on a phone.

  • Main-thread work: 3.9 s

    A phone's processor spends 3.9 s on main-thread work while loading, 1.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Facebook adds 320 ms

    320 ms

    Facebook costs a phone 320 ms of main-thread work and 254 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 Maps adds 231 ms

    231 ms

    Google Maps costs a phone 231 ms of main-thread work and 393 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.

  • 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: 187 ms

    187 ms

    Your server sent the HTML in 187 ms, well inside Google's 600 ms guideline.

Core Web Vitals

13 to fix33
  • 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 CLS: 0.47

    0.47

    For real visitors the layout shifts by 0.47 (75th percentile). Good is under 0.1.

  • Largest Contentful Paint: 11.5 s

    11.5 s

    Your largest element takes 11.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “div.v-image__image”. Most of its time is element render delay (6.6 s).

  • Speed Index: 16.4 s

    16.4 s

    Visually, the page fills in at 16.4 s (Speed Index). Good is under 3.4 s.

  • Time to Interactive: 20.7 s

    20.7 s

    The page becomes fully interactive after 20.7 s. Good is under 3.8 s.

  • Total Blocking Time: 1.2 s

    1.2 s

    Scripts block taps and scrolling for 1.2 s in total while the page loads. Good is under 200 ms.

  • Cumulative Layout Shift: 0.435

    0.435

    The layout shifts by 0.435 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Real-user LCP: 3.0 s

    3.0 s

    Real visitors wait 3.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Tap response (INP) got 37% slower for real visitors

    +37%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 120 ms to 162 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Real-user FCP: 2.7 s

    2.7 s

    Real visitors see the first content after 2.7 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 916 ms

    916 ms

    Real visitors wait 916 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • First Contentful Paint: 1.9 s

    1.9 s

    The first text or image appears after 1.9 s on a phone. Good is under 1.8 s.

  • 3 images without width and height

    3 images have no width and height attributes, so the layout jumps as each one loads.

2 checks passed
  • Real-user INP: 160 ms

    160 ms

    Real visitors wait 160 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Largest content (LCP) got 11% faster for real visitors

    -11%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 4.0 s to 3.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Images and page weight

1 to fix50
  • Page weight: 3.7 MB in 51 requests

    3.7 MB

    Your homepage downloads 3.7 MB in 51 requests on a phone: images 1.8 MB (12), scripts 1.7 MB (13) and stylesheets 114 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • About 1.0 g of CO₂ per visit

    1.04 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.04 g of CO₂e: 124.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Accessibility

5 to fix75
  • 4 buttons without a name

    4 buttons have no accessible name, so screen readers announce just “button”.

  • Invalid ARIA attributes

    1 element use ARIA attributes their role does not allow, which confuses screen readers.

  • Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

    Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children. (1 element).

  • Unlabelled dropdowns

    1 dropdown has no label.

  • Links do not have a discernible name

    Links do not have a discernible name (1 element).

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Headings skip levels

    Headings skip levels (h3 → h6, h4 → h6 and h4 → h6), which makes the page harder to scan with a screen reader.

1 checks passed
  • Every image has alt text

    All 9 images in the HTML carry an alt attribute.

SEO

3 to fixGoogle 9289
  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 8 H1 headlines

    There are 8 <h1> headlines (“Step inside Australia's 2026 Home of the Year”, “Step inside Australia's 2026 Home of the Year” and “Up to $290 in bonus value for HIA Safescan Subscr…”). One clear main headline is easier for people and search engines.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 129 internal links, 6 external

    The homepage links to 129 pages on hia.com.au and 6 external pages.

6 checks passed
  • Meta description: 155 characters

    Your meta description is 155 characters: “HIA is the peak national industry association for residential building in Australia. HIA members strive for full compli…”.

  • Title: 57 characters

    Your title is a healthy 57 characters: “Housing Industry Association | HIA | You're in good hands”.

  • Canonical URL set

    The canonical URL is https://hia.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://hia.com.au/sitemap.xml.

AI search readiness

1 to fix83
  • 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://hia.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.

1 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.

Other pages

1 to fix95
  • 1 page without a meta description

    https://hia.com.au/our-industry/economics/economic-insights has no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages slow to respond

    https://hia.com.au/our-industry/economics, https://hia.com.au/our-industry/economics/economic-insights and https://hia.com.au/our-industry/housing took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 96 found) and read each the way a search engine does.

6 checks passed
  • Linked pages load

    8 pages of 15 loaded without an error (the rest turned automated requests away).

  • 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.

  • 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 8 pages that loaded have a <title>.

Best practices

Google 100100
  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • Thin social proof

    Social proof on the homepage: 4 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • 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 1,742 words of copy

    The homepage carries about 1,742 words of visible text.

2 checks passed
  • 4 calls to action

    The homepage has 4 calls to action, for example “Browse the shop”, “How do I apply?” and “Get your builder's licence”.

  • Direct contact links

    Visitors can reach you directly: 4 phone links and 0 email links.

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 hia.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

Hosting
Azure

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 39 issues on hia.com.au, including 26 speed issues, 3 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25