Website review, no card needed

aia.com.au logo

aia.com.au website review

Visit site (opens in a new tab)Reviewed 1 November 202644 issues · 81 checks

This review found 44 issues worth fixing on aia.com.au, 16 of them high impact, across 81 checks. The most urgent: avoid multiple page redirects. 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.0 s2.9 sMay 9Oct 243.8 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.7 s
May 16, 20263.8 s
May 23, 20263.6 s
May 30, 20263.6 s
Jun 6, 20263.4 s
Jun 13, 20263.4 s
Jun 20, 20263.3 s
Jun 27, 20263.3 s
Jul 4, 20263.1 s
Jul 11, 20263.0 s
Jul 18, 20263.0 s
Jul 25, 20263.0 s
Aug 1, 20263.1 s
Aug 8, 20263.2 s
Aug 15, 20263.3 s
Aug 22, 20263.3 s
Aug 29, 20263.5 s
Sep 5, 20263.6 s
Sep 12, 20263.7 s
Sep 19, 20263.8 s
Sep 26, 20263.8 s
Oct 3, 20263.8 s
Oct 10, 20263.8 s
Oct 17, 20263.8 s
Oct 24, 20263.8 s
Real-visitor tap response (INP)75th percentile, phones
149 ms106 msMay 9Oct 24144 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026112 ms
May 16, 2026116 ms
May 23, 2026115 ms
May 30, 2026120 ms
Jun 6, 2026124 ms
Jun 13, 2026122 ms
Jun 20, 2026126 ms
Jun 27, 2026120 ms
Jul 4, 2026114 ms
Jul 11, 2026113 ms
Jul 18, 2026111 ms
Jul 25, 2026112 ms
Aug 1, 2026112 ms
Aug 8, 2026113 ms
Aug 15, 2026113 ms
Aug 22, 2026112 ms
Aug 29, 2026112 ms
Sep 5, 2026113 ms
Sep 12, 2026116 ms
Sep 19, 2026124 ms
Sep 26, 2026133 ms
Oct 3, 2026142 ms
Oct 10, 2026144 ms
Oct 17, 2026144 ms
Oct 24, 2026144 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 aia.com.au (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. aia.com.au at 0.8 s0.8 s
  2. aia.com.au at 1.6 s1.6 s
  3. aia.com.au at 2.4 s2.4 s
  4. aia.com.au at 3.1 s3.1 s
  5. aia.com.au at 3.9 s3.9 s
  6. aia.com.au at 4.7 s4.7 s
  7. aia.com.au at 5.5 s5.5 s
  8. aia.com.au at 6.3 s6.3 s

Speed

8 to fix27
  • Avoid multiple page redirects

    24.8 s

    The page goes through 1 redirect before it starts loading, costing about 24.8 s. Link and advertise the final URL directly.

  • Reduce unused JavaScript

    13.3 s · 1.7 MB

    About 1.7 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 13.3 s faster on a phone.

  • Minify JavaScript

    1.6 s · 173 KiB

    173 KiB could be saved by minifying JavaScript.

  • Mobile performance score: 27

    27/100

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

  • Main-thread work: 8.5 s

    A phone's processor spends 8.5 s on main-thread work while loading, 6.0 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, Dynatrace and Facebook and others), adding 758 KiB and 705 ms of main-thread time.

  • 20 long tasks on the main thread

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

  • 2,347 HTML elements

    The page has 2,347 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

1 checks passed
  • Server response: 8 ms

    8 ms

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

Core Web Vitals

11 to fix67
  • 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.

  • First Contentful Paint: 13.4 s

    13.4 s

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

  • Largest Contentful Paint: 39.7 s

    39.7 s

    Your largest element takes 39.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “A man and woman embrace each other affectionately in a lush…”.

  • Speed Index: 17.0 s

    17.0 s

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

  • Time to Interactive: 40.1 s

    40.1 s

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

  • Total Blocking Time: 1.9 s

    1.9 s

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

  • Real-user LCP: 3.9 s

    3.9 s

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

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

    +26%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 112 ms to 144 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: 1.3 s

    1.3 s

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

  • 1 image without width and height

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

  • Largest content (LCP) held steady for real visitors

    +3%

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

3 checks passed
  • Real-user INP: 141 ms

    141 ms

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

  • Real-user CLS: 0.08

    0.08

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

  • Cumulative Layout Shift: 0.001

    0.001

    The layout barely moves while loading (CLS 0.001, good is under 0.1).

Images and page weight

2 to fix60
  • Page weight: 7.1 MB in 237 requests

    7.1 MB

    Your homepage downloads 7.1 MB in 237 requests on a phone: scripts 3.6 MB (52), images 2.2 MB (94) and fonts 639 KiB (11). Under 2 MB keeps phones on slow connections fast.

  • 3 images far larger than shown

    181 KiB

    3 images are downloaded at several times the size a phone draws them, for example Row [email protected] at 900 px wide, shown at 120 px. Resized copies would save about 181 KiB.

  • 1 image in older formats

    1 image (105 KiB) is 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.

  • 1 image below the first screen load straight away

    1 image further down the page (105 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 2.0 g of CO₂ per visit

    2.01 g

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

Accessibility

5 to fixGoogle 9592
  • 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.

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • 25 images without alt text

    25 images have no alt text, which hurts accessibility and image search.

  • Heading levels should only increase by one (1 element)

    Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

  • 7 form fields without a label

    7 form fields have no label, so screen readers announce an empty box and autofill guesses.

1 checks passed
  • 46 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 3 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

6 to fixGoogle 4268
  • Blocked from indexing

    Google's crawler is blocked from indexing this page.

  • Title is short (13 characters)

    Your title is only 13 characters: “AIA Australia”. 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 canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

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

  • Open Graph partly set

    Open Graph is missing og:title and og:description, so shared links fall back to guesses.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 197 internal links, 22 external

    The homepage links to 197 pages on aia.com.au and 22 external pages.

4 checks passed
  • Meta description: 145 characters

    Your meta description is 145 characters: “Discover AIA Australia’s health and life insurance solutions, featuring award-winning cover and AIA Vitality rewards fo…”.

  • One H1 headline

    Your main headline reads: “Get up to 8 weeks free* on your health insurance”.

  • 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.aia.com.au/en/sitemap.xml.

AI search readiness

1 to fix88
  • 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.

3 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,826 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.aia.com.au/llms.txt (13 KiB, 29 links), a plain-text guide to the site for AI tools.

Other pages

3 to fix80
  • 1 linked page hidden from search

    https://www.aia.com.au/en/products/corporate-health-insurance is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 2 pages share a title

    / and https://www.aia.com.au/en all use the title “AIA Australia”. 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.aia.com.au/en/products/for-superannuation-partners/aia-embrace, https://www.aia.com.au/en/products/for-superannuation-partners/vitality-in-super, https://www.aia.com.au/en/products/for-superannuation-partners/claims, https://www.aia.com.au/en/products/for-superannuation-partners/group-insights, https://www.aia.com.au/en/products/for-superannuation-partners/our-partners and https://www.aia.com.au/en/products/partner-with-us have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages slow to respond

    https://www.aia.com.au/en and https://www.aia.com.au/en/products/for-superannuation-partners/group-insights took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has an H1

    Each page we checked has a main headline.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

5 to fixGoogle 5081
  • 4 small tap targets

    4 of 20 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 4 third-party cookies

    4 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • Deprecated browser APIs

    The page uses 2 deprecated browser APIs that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'ContentFrame')”.

  • 2 distorted images

    2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

  • 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 fix80
  • 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 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 972 words of copy

    The homepage carries about 972 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 Us”.

  • 14 calls to action

    The homepage has 14 calls to action, for example “Contact Us”, “Get a quote” and “Learn more”.

  • Social proof on the page

    Social proof on the homepage: 2 testimonial or review blocks, 1 customer or partner logo and 1 trust badge.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, 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.

  • 20 cookies set on arrival

    20

    Opening the homepage sets 20 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.

  • 25 other companies contacted

    Loading the homepage contacts 25 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 aia.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
Tailwind CSS
Hosting
Akamai

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 44 issues on aia.com.au, including 19 speed issues, 6 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