Website review, no card needed

cbhs.com.au logo

cbhs.com.au website review

Visit site (opens in a new tab)Reviewed 3 November 202639 issues · 86 checks

This review found 39 issues worth fixing on cbhs.com.au, 21 of them high impact, across 86 checks. The most urgent: improve image delivery. 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
3.2 s2.3 sMay 16Oct 312.9 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.6 s
May 23, 20262.7 s
May 30, 20262.8 s
Jun 6, 20262.7 s
Jun 13, 20262.8 s
Jun 20, 20262.6 s
Jun 27, 20262.6 s
Jul 4, 20262.6 s
Jul 11, 20262.6 s
Jul 18, 20262.5 s
Jul 25, 20262.4 s
Aug 1, 20262.7 s
Aug 8, 20262.9 s
Aug 15, 20263.0 s
Aug 22, 20263.0 s
Aug 29, 20262.9 s
Sep 5, 20262.7 s
Sep 12, 20262.7 s
Sep 19, 20262.7 s
Sep 26, 20262.8 s
Oct 3, 20263.0 s
Oct 10, 20263.0 s
Oct 17, 20263.1 s
Oct 24, 20263.1 s
Oct 31, 20262.9 s
Real-visitor tap response (INP)75th percentile, phones
243 ms182 msMay 16Oct 31229 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026204 ms
May 23, 2026203 ms
May 30, 2026202 ms
Jun 6, 2026203 ms
Jun 13, 2026207 ms
Jun 20, 2026209 ms
Jun 27, 2026202 ms
Jul 4, 2026200 ms
Jul 11, 2026193 ms
Jul 18, 2026189 ms
Jul 25, 2026195 ms
Aug 1, 2026194 ms
Aug 8, 2026203 ms
Aug 15, 2026207 ms
Aug 22, 2026207 ms
Aug 29, 2026211 ms
Sep 5, 2026212 ms
Sep 12, 2026213 ms
Sep 19, 2026225 ms
Sep 26, 2026236 ms
Oct 3, 2026233 ms
Oct 10, 2026229 ms
Oct 17, 2026229 ms
Oct 24, 2026232 ms
Oct 31, 2026229 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 cbhs.com.au (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. cbhs.com.au at 1.4 s1.4 s
  2. cbhs.com.au at 2.8 s2.8 s
  3. cbhs.com.au at 4.2 s4.2 s
  4. cbhs.com.au at 5.6 s5.6 s
  5. cbhs.com.au at 7.0 s7.0 s
  6. cbhs.com.au at 8.4 s8.4 s
  7. cbhs.com.au at 9.8 s9.8 s
  8. cbhs.com.au at 11.2 s11.2 s

Speed

12 to fix5
  • Improve image delivery

    6.8 s · 1.3 MB

    4 images could be 1.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 6.8 s faster on a phone.

  • Use efficient cache lifetimes

    6.0 s · 1.5 MB

    17 files are served with short cache lifetimes, so returning visitors download them again (1.5 MB).

  • Reduce unused JavaScript

    5.7 s · 1.6 MB

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

  • Render-blocking requests

    6.8 s

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

  • Google Tag Manager adds 2.1 s

    2.1 s

    Google Tag Manager costs a phone 2.1 s of main-thread work and 1.5 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.

  • Mobile performance score: 5

    5/100

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

  • Main-thread work: 7.0 s

    A phone's processor spends 7.0 s on main-thread work while loading, 4.2 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, botframework.com and Facebook and others), adding 3.1 MB and 3.6 s of main-thread time.

  • botframework.com adds 794 ms

    794 ms

    botframework.com costs a phone 794 ms of main-thread work and 936 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.

  • 19 long tasks on the main thread

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

  • Reduce unused CSS

    300 ms · 67 KiB

    About 67 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

  • Azure Web Services adds 145 ms

    145 ms

    Azure Web Services costs a phone 145 ms of main-thread work and 412 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

    150 ms · 23 KiB

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

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

    5 ms

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

Core Web Vitals

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

  • Real-user CLS: 0.54

    0.54

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

  • Largest Contentful Paint: 24.6 s

    24.6 s

    Your largest element takes 24.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “lady_doing_pilates”.

  • Time to Interactive: 32.5 s

    32.5 s

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

  • First Contentful Paint: 7.4 s

    7.4 s

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

  • Speed Index: 13.9 s

    13.9 s

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

  • Total Blocking Time: 2.9 s

    2.9 s

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

  • Cumulative Layout Shift: 0.497

    0.497

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

  • 8 images without width and height

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

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

    +13%

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

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

    +11%

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

4 checks passed
  • Real-user LCP: 2.1 s

    2.1 s

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

  • Real-user INP: 174 ms

    174 ms

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

  • Real-user FCP: 1.6 s

    1.6 s

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

  • Real-user TTFB: 534 ms

    534 ms

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

Images and page weight

4 to fix35
  • Page weight: 5.6 MB in 144 requests

    5.6 MB

    Your homepage downloads 5.6 MB in 144 requests on a phone: scripts 3.7 MB (63), images 1.5 MB (26) and other files 158 KiB (47). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    2602_cbhs_website_blogbanner_900x500px_1.tmb-ctabannerd.png weighs 1,021 KiB. On a phone connection a single image that size takes seconds.

  • 4 images in older formats

    4 images (1.4 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.

  • 3 images far larger than shown

    322 KiB

    3 images are downloaded at several times the size a phone draws them, for example best-for-gold-hospital-cover-winner-health-insurance-2026.pn at 800 px wide, shown at 118 px. Resized copies would save about 322 KiB.

  • About 1.6 g of CO₂ per visit

    1.58 g

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

1 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

1 to fixGoogle 9798
  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

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

  • 49 automated accessibility rules passed

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

SEO

5 to fixGoogle 8573
  • robots.txt blocks all crawlers

    Your robots.txt disallows the whole site for every crawler, so search engines are told to stay out.

  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • No structured data

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

  • No XML sitemap

    No XML sitemap at https://www.cbhs.com.au/sitemap.xml, so Google discovers your pages only by following links.

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

  • 148 internal links, 7 external

    The homepage links to 148 pages on cbhs.com.au and 7 external pages.

4 checks passed
  • Meta description: 120 characters

    Your meta description is 120 characters: “Belong to More. 70 years with a singular mission. Members for life. Everything we do centres around achieving that goal.”.

  • Title: 33 characters

    Your title is a healthy 33 characters: “CBHS Health Fund - Belong to More”.

  • Canonical URL set

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

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

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.

  • No llms.txt

    There is no https://www.cbhs.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,370 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 11 pages without an H1

    https://www.cbhs.com.au/health-insurance, https://www.cbhs.com.au/health-insurance/hospital-extras, https://www.cbhs.com.au/health-insurance/hospital-cover, https://www.cbhs.com.au/health-insurance/extras-cover, https://www.cbhs.com.au/health-insurance/ambulance-cover and https://www.cbhs.com.au/health-insurance/dependant-cover and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 6 pages slow to respond

    https://www.cbhs.com.au/health-insurance/hospital-cover, https://www.cbhs.com.au/health-insurance/ambulance-cover, https://www.cbhs.com.au/health-insurance/singles-and-couples, https://www.cbhs.com.au/health-insurance/families-and-sole-parents, https://www.cbhs.com.au/health-insurance/mature-families and https://www.cbhs.com.au/health-insurance/retirees took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

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

  • Every page has a meta description

    All 14 pages that loaded have a meta description.

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

Best practices

5 to fixGoogle 5073
  • 1 broken image

    1 image failed to load on a phone, for example https://event-va1.pubmatic.com?adv=28573&cb=59270125&ref=https%3A%2F%2Fwww.cbhs.com.au%2F.

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Loading the script 'https://ads-engagement.presage.io/script?site=www.cbhs.com.au&full_url=https%3A%2F%2Fwww.cbhs.com.a…”.

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

  • Browser-reported issues

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

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

100
  • About 1,224 words of copy

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

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

7 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “contact us” and “GET A QUOTE”.

  • 10 calls to action

    The homepage has 10 calls to action, for example “GET A QUOTE”, “Why join CBHS” and “Call”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 10 testimonial or review blocks and 6 customer or partner logos.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

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

  • 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

1 to fix
  • 8 trackers load before any consent

    8

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

  • 28 cookies set on arrival

    28

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

  • 30 other companies contacted

    Loading the homepage contacts 30 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 cbhs.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.2.8427.0 DX
Framework
Tailwind CSS
Analytics
Google Tag Manager
Hosting
AWS

Company

Founded
1951

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 cbhs.com.au, including 21 speed issues and 5 SEO issues. 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