Website review, no card needed

hbf.com.au logo

hbf.com.au website review

Visit site (opens in a new tab)Reviewed 2 November 202637 issues · 88 checks

This review found 37 issues worth fixing on hbf.com.au, 14 of them high impact, across 88 checks. The most urgent: mobile performance score: 34. 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.5 s1.7 sMay 16Oct 312.0 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20263.3 s
May 23, 20263.3 s
May 30, 20263.4 s
Jun 6, 20263.5 s
Jun 13, 20263.1 s
Jun 20, 20263.2 s
Jun 27, 20263.7 s
Jul 4, 20264.1 s
Jul 11, 20264.1 s
Jul 18, 20264.1 s
Jul 25, 20263.6 s
Aug 1, 20262.5 s
Aug 8, 20262.1 s
Aug 15, 20262.1 s
Aug 22, 20262.1 s
Aug 29, 20262.1 s
Sep 5, 20262.1 s
Sep 12, 20262.1 s
Sep 19, 20262.1 s
Sep 26, 20262.1 s
Oct 3, 20262.0 s
Oct 10, 20262.1 s
Oct 17, 20262.1 s
Oct 24, 20262.1 s
Oct 31, 20262.0 s
Real-visitor tap response (INP)75th percentile, phones
461 ms261 msMay 16Oct 31329 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026412 ms
May 23, 2026338 ms
May 30, 2026321 ms
Jun 6, 2026311 ms
Jun 13, 2026295 ms
Jun 20, 2026366 ms
Jun 27, 2026428 ms
Jul 4, 2026438 ms
Jul 11, 2026430 ms
Jul 18, 2026421 ms
Jul 25, 2026401 ms
Aug 1, 2026382 ms
Aug 8, 2026401 ms
Aug 15, 2026421 ms
Aug 22, 2026419 ms
Aug 29, 2026401 ms
Sep 5, 2026360 ms
Sep 12, 2026321 ms
Sep 19, 2026300 ms
Sep 26, 2026286 ms
Oct 3, 2026284 ms
Oct 10, 2026285 ms
Oct 17, 2026296 ms
Oct 24, 2026315 ms
Oct 31, 2026329 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 hbf.com.au (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

9 to fix34
  • Mobile performance score: 34

    34/100

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

  • Main-thread work: 8.7 s

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

  • Reduce unused JavaScript

    750 ms · 689 KiB

    About 689 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.

  • 20 long tasks on the main thread

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Facebook, AB Tasty and feroot.com and others), adding 1.1 MB and 358 ms of main-thread time.

  • Render-blocking requests

    450 ms

    2 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.

  • Use efficient cache lifetimes

    395 KiB

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

  • 1,879 HTML elements

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

  • site.com adds 19 ms

    19 ms

    site.com costs a phone 19 ms of main-thread work and 753 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.

  • Improve image delivery

    222 KiB

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

  • Reduce unused CSS

    150 ms · 60 KiB

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

  • Legacy JavaScript

    25 KiB

    Polyfills for old browsers add 25 KiB JavaScript that modern phones do not need.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

  • Minify CSS

    2 KiB

    2 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 577 ms

    577 ms

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

Core Web Vitals

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

  • Time to Interactive: 27.7 s

    27.7 s

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

  • Largest Contentful Paint: 7.7 s

    7.7 s

    Your largest element takes 7.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Quokka mascot sitting with a laptop and suitcase, holding a…”.

  • Total Blocking Time: 2.4 s

    2.4 s

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

  • Speed Index: 10.2 s

    10.2 s

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

  • Real-user INP: 296 ms

    296 ms

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

  • Real-user CLS: 0.15

    0.15

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

  • Real-user TTFB: 1.1 s

    1.1 s

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

  • Cumulative Layout Shift: 0.119

    0.119

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

5 checks passed
  • Real-user LCP: 2.0 s

    2.0 s

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

  • Real-user FCP: 1.7 s

    1.7 s

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

  • Tap response (INP) got 14% faster for real visitors

    -14%

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

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

    -39%

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

  • First Contentful Paint: 1.6 s

    1.6 s

    The first text or image appears after 1.6 s, inside the 1.8 s “good” threshold.

Images and page weight

3 to fix60
  • Page weight: 4.3 MB in 272 requests

    4.3 MB

    Your homepage downloads 4.3 MB in 272 requests on a phone: scripts 3.1 MB (185), images 603 KiB (19) and other files 162 KiB (52). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    6-weeks-free-overseas-working-visa-hospital-cover-offer-tier is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 1 image far larger than shown

    43 KiB

    1 image is downloaded at several times the size a phone draws it, for example tax-time-quokka.png at 1,040 px wide, shown at 298 px. Resized copies would save about 43 KiB.

  • 1 image in older formats

    1 image (163 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.

  • 7 images below the first screen load straight away

    7 images further down the page (211 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.2 g of CO₂ per visit

    1.22 g

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

Accessibility

10 to fixGoogle 8388
  • 18 text elements with low contrast

    18 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 9 tap targets too small

    9 tap targets are too small or too close together to hit reliably with a finger.

  • ARIA input fields must have an accessible name (8 elements)

    ARIA input fields must have an accessible name: 8 elements on the page fail this check, rated serious by axe-core.

  • Elements must only use permitted ARIA attributes (5 elements)

    Elements must only use permitted ARIA attributes: 5 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.

  • Banner landmark should not be contained in another landmark (5 elements)

    Banner landmark should not be contained in another landmark: 5 elements on the page fail this check, rated moderate by axe-core.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

  • Document should not have more than one banner landmark (1 element)

    Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • 8 form fields without a label

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

  • 4 links without text

    4 visible links have no text or label, so screen readers cannot say where they go.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

2 checks passed
  • Every image has alt text

    All 30 images in the HTML carry an alt attribute.

  • 50 automated accessibility rules passed

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

SEO

Google 100100
  • No X (Twitter) card tag

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

  • 169 internal links, 11 external

    The homepage links to 169 pages on hbf.com.au and 11 external pages.

8 checks passed
  • Meta description: 144 characters

    Your meta description is 144 characters: “Looking for private health insurance that puts members first? Compare affordable hospital and extras cover with HBF. Jo…”.

  • One H1 headline

    Your main headline reads: “Health insurance to suit your needs”.

  • Title: 51 characters

    Your title is a healthy 51 characters: “HBF Health Insurance | Compare Private Health Cover”.

  • Canonical URL set

    The canonical URL is https://www.hbf.com.au/.

  • Structured data in place

    Structured data found: Organization.

  • 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.hbf.com.au/sitemaps.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.hbf.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.

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.

  • Organization data: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,789 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 3 pages without a meta description

    https://www.hbf.com.au/payhbf, https://www.hbf.com.au/offers and https://www.hbf.com.au/health-insurance/cover-to-suit-your-needs have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    https://www.hbf.com.au/payhbf and https://www.hbf.com.au/health-insurance/cover-to-suit-your-needs have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://www.hbf.com.au/health-insurance/cover-to-suit-your-needs has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 3 pages slow to respond

    https://www.hbf.com.au/payhbf, https://www.hbf.com.au/health-insurance/new-to-health-insurance and https://www.hbf.com.au/health-insurance/overseas/what-is-ovhc took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

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

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://hbf.my.site.com/ESWMessagingChatUnAuth1753693401669/assets/styles/bootstrap.min.cs…”.

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

    19 of 23 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • 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.

  • Thin social proof

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

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

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

4 checks passed
  • 13 calls to action

    The homepage has 13 calls to action, for example “Call +61 8 9265 6111”, “Smart Start Extras” and “Get a quote”.

  • 1 short form

    A short form (2 fields at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 18 cookies set on arrival

    18

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

  • 13 other companies contacted

    Loading the homepage contacts 13 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 hbf.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
CloudFront

Company

Founded
1941
Headquarters
Perth

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 37 issues on hbf.com.au, including 18 speed 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