Website review, no card needed

nib.com.au logo

nib.com.au website review

Visit site (opens in a new tab)Reviewed 5 November 202633 issues · 87 checks

This review found 33 issues worth fixing on nib.com.au, 11 of them high impact, across 87 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
3.8 s2.1 sMay 16Oct 312.4 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.4 s
May 23, 20263.0 s
May 30, 20263.5 s
Jun 6, 20263.6 s
Jun 13, 20263.6 s
Jun 20, 20263.2 s
Jun 27, 20262.9 s
Jul 4, 20262.9 s
Jul 11, 20262.8 s
Jul 18, 20262.7 s
Jul 25, 20262.5 s
Aug 1, 20262.4 s
Aug 8, 20262.4 s
Aug 15, 20262.4 s
Aug 22, 20262.3 s
Aug 29, 20262.4 s
Sep 5, 20262.4 s
Sep 12, 20262.4 s
Sep 19, 20262.3 s
Sep 26, 20262.3 s
Oct 3, 20262.3 s
Oct 10, 20262.4 s
Oct 17, 20262.4 s
Oct 24, 20262.5 s
Oct 31, 20262.4 s
Real-visitor tap response (INP)75th percentile, phones
188 ms169 msMay 16Oct 31186 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026177 ms
May 23, 2026179 ms
May 30, 2026179 ms
Jun 6, 2026182 ms
Jun 13, 2026180 ms
Jun 20, 2026177 ms
Jun 27, 2026175 ms
Jul 4, 2026171 ms
Jul 11, 2026171 ms
Jul 18, 2026171 ms
Jul 25, 2026172 ms
Aug 1, 2026172 ms
Aug 8, 2026174 ms
Aug 15, 2026176 ms
Aug 22, 2026178 ms
Aug 29, 2026183 ms
Sep 5, 2026183 ms
Sep 12, 2026184 ms
Sep 19, 2026184 ms
Sep 26, 2026186 ms
Oct 3, 2026185 ms
Oct 10, 2026184 ms
Oct 17, 2026183 ms
Oct 24, 2026181 ms
Oct 31, 2026186 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 nib.com.au (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. nib.com.au at 0.4 s0.4 s
  2. nib.com.au at 0.8 s0.8 s
  3. nib.com.au at 1.1 s1.1 s
  4. nib.com.au at 1.5 s1.5 s
  5. nib.com.au at 1.9 s1.9 s
  6. nib.com.au at 2.3 s2.3 s
  7. nib.com.au at 2.6 s2.6 s
  8. nib.com.au at 3.0 s3.0 s

Speed

9 to fix41
  • Reduce unused JavaScript

    2.7 s · 632 KiB

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

  • Use efficient cache lifetimes

    2.1 s · 592 KiB

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

  • Mobile performance score: 41

    41/100

    Your mobile performance score is 41. 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, ContentSquare and Tealium and others), adding 1.5 MB and 1.4 s of main-thread time.

  • Google Tag Manager adds 773 ms

    773 ms

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

  • Render-blocking requests

    800 ms

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

  • Main-thread work: 3.5 s

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

  • 17 long tasks on the main thread

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

  • 1,642 HTML elements

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

  • Improve image delivery

    150 ms · 46 KiB

    2 images could be 46 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

  • Legacy JavaScript

    150 ms · 45 KiB

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

  • Reduce unused CSS

    19 KiB

    About 19 KiB of CSS is downloaded but never applied on this page.

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

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

    5 ms

    Your server sent the HTML in 5 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.

  • Real-user FCP: 3.7 s

    3.7 s

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

  • Real-user TTFB: 3.0 s

    3.0 s

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

  • Largest Contentful Paint: 15.4 s

    15.4 s

    Your largest element takes 15.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Mary Fowler and Paul Harragon celebrating”.

  • Time to Interactive: 18.7 s

    18.7 s

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

  • Total Blocking Time: 838 ms

    838 ms

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

  • Speed Index: 6.1 s

    6.1 s

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

  • Real-user LCP: 3.8 s

    3.8 s

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

  • First Contentful Paint: 2.7 s

    2.7 s

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

  • Cumulative Layout Shift: 0.136

    0.136

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

  • 2 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +3%

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

3 checks passed
  • Real-user INP: 171 ms

    171 ms

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

  • Real-user CLS: 0.00

    0.00

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

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

    -10%

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

Images and page weight

1 to fix85
  • Page weight: 2.1 MB in 106 requests

    2.1 MB

    Your homepage downloads 2.1 MB in 106 requests on a phone: scripts 1.8 MB (52), images 112 KiB (12) and fonts 77 KiB (3). Under 2 MB keeps phones on slow connections fast.

  • About 0.6 g of CO₂ per visit

    0.59 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

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

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

4 to fixGoogle 10096
  • Banner landmark should not be contained in another landmark (1 element)

    Banner landmark should not be contained in another landmark: 1 element on the page fails 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.

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

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

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 9 images in the HTML carry an alt attribute.

  • 43 automated accessibility rules passed

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

SEO

1 to fixGoogle 10097
  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No X (Twitter) card tag

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

  • 167 internal links, 11 external

    The homepage links to 167 pages on nib.com.au and 11 external pages.

7 checks passed
  • Meta description: 156 characters

    Your meta description is 156 characters: “Find health insurance that suits your needs with nib. Explore hospital and extras cover, overseas health cover, travel …”.

  • One H1 headline

    Your main headline reads: “Win at Health Insurance”.

  • Title: 53 characters

    Your title is a healthy 53 characters: “Health Insurance, Travel Cover & Healthy Living | nib”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: Organization and WebSite.

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

AI search readiness

100
  • No llms.txt

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

Other pages

1 to fix95
  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.nib.com.au/going-to-hospital, whose canonical is https://www.nib.com.au/health-information/going-to-hospital. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 5 pages slow to respond

    https://www.nib.com.au/health-insurance/couples, https://www.nib.com.au/health-insurance/extras, https://www.nib.com.au/health-insurance/ambulance, https://www.nib.com.au/member-benefits and https://www.nib.com.au/first-choice-network took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

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

Best practices

3 to fixGoogle 7776
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=13016349&Ver=2&mid=34b2483e-d275-4055-9a57-ce24b02cecb8&bo=1&sid=4b667b80d96811f19f38777dadd62f51&vid=4b669780d96811f1957e5b4b9c444b91&vids=1&msclkid=N&pi=918639831&lg.

  • 4 small tap targets

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

  • 1 third-party cookie

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

  • Browser-reported issues

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

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix86
  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No analytics detected

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

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

    The homepage carries about 454 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Get a quote”.

  • 17 calls to action

    The homepage has 17 calls to action, for example “Get a quote”, “Call us” and “Join nib for free”.

  • Social proof on the page

    Social proof on the homepage: a star rating and 3 trust badges.

  • Direct contact links

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

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 10 trackers load before any consent

    10

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

  • 30 cookies set on arrival

    30

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

  • 37 other companies contacted

    Loading the homepage contacts 37 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 nib.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
Cloudflare

Company

Founded
1952
Headquarters
Newcastle

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on nib.com.au, including 20 speed issues, 1 SEO issue 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