Website review, no card needed

independenceaustralia.com.au logo

independenceaustralia.com.au website review

Visit site (opens in a new tab)Reviewed 28 October 202634 issues · 82 checks

This review found 34 issues worth fixing on independenceaustralia.com.au, 16 of them high impact, across 82 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
2.0 s900 msMay 9Oct 241.8 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.3 s
May 16, 20261.3 s
May 23, 20261.3 s
May 30, 20261.4 s
Jun 6, 20261.3 s
Jun 13, 20261.2 s
Jun 20, 20261.1 s
Jun 27, 20261.1 s
Jul 4, 20261.0 s
Jul 11, 20261.1 s
Jul 18, 20261.1 s
Jul 25, 20261.2 s
Aug 1, 20261.3 s
Aug 8, 20261.3 s
Aug 15, 20261.4 s
Aug 22, 20261.6 s
Aug 29, 20261.7 s
Sep 5, 20261.8 s
Sep 12, 20261.8 s
Sep 19, 20261.7 s
Sep 26, 20261.8 s
Oct 3, 20261.8 s
Oct 10, 20261.8 s
Oct 17, 20261.8 s
Oct 24, 20261.8 s
Real-visitor tap response (INP)75th percentile, phones
151 ms114 msMay 9Oct 24147 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026130 ms
May 16, 2026131 ms
May 23, 2026130 ms
May 30, 2026132 ms
Jun 6, 2026129 ms
Jun 13, 2026130 ms
Jun 20, 2026128 ms
Jun 27, 2026123 ms
Jul 4, 2026122 ms
Jul 11, 2026120 ms
Jul 18, 2026118 ms
Jul 25, 2026121 ms
Aug 1, 2026122 ms
Aug 8, 2026127 ms
Aug 15, 2026129 ms
Aug 22, 2026129 ms
Aug 29, 2026128 ms
Sep 5, 2026128 ms
Sep 12, 2026130 ms
Sep 19, 2026130 ms
Sep 26, 2026130 ms
Oct 3, 2026130 ms
Oct 10, 2026137 ms
Oct 17, 2026137 ms
Oct 24, 2026147 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 independenceaustralia.com.au (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. independenceaustralia.com.au at 0.6 s0.6 s
  2. independenceaustralia.com.au at 1.2 s1.2 s
  3. independenceaustralia.com.au at 1.9 s1.9 s
  4. independenceaustralia.com.au at 2.5 s2.5 s
  5. independenceaustralia.com.au at 3.1 s3.1 s
  6. independenceaustralia.com.au at 3.7 s3.7 s
  7. independenceaustralia.com.au at 4.3 s4.3 s
  8. independenceaustralia.com.au at 5.0 s5.0 s

Speed

13 to fix26
  • Improve image delivery

    17.3 s · 6.4 MB

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

  • YouTube adds 1.1 s

    1.1 s

    YouTube costs a phone 1.1 s of main-thread work and 2.4 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.

  • Google Tag Manager adds 1.1 s

    1.1 s

    Google Tag Manager costs a phone 1.1 s of main-thread work and 536 KiB 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: 26

    26/100

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

  • Main-thread work: 6.6 s

    A phone's processor spends 6.6 s on main-thread work while loading, 3.5 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 (YouTube, Google Tag Manager and Facebook and others), adding 3.8 MB and 2.7 s of main-thread time.

  • Reduce unused JavaScript

    2.0 MB

    About 2.0 MB of JavaScript is downloaded but never used on this page.

  • Render-blocking requests

    900 ms

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

  • 20 long tasks on the main thread

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

  • Reduce unused CSS

    460 ms · 120 KiB

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

  • Use efficient cache lifetimes

    284 KiB

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

  • Facebook adds 251 ms

    251 ms

    Facebook costs a phone 251 ms of main-thread work and 235 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.

  • userway.org adds 80 ms

    80 ms

    userway.org costs a phone 80 ms of main-thread work and 448 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

    84 KiB

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

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

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

1 checks passed
  • Server response: 45 ms

    45 ms

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

Core Web Vitals

8 to fix100
  • Largest Contentful Paint: 29.7 s

    29.7 s

    Your largest element takes 29.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Man in blue shirt smiling riding a bike”.

  • Time to Interactive: 43.4 s

    43.4 s

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

  • Total Blocking Time: 1.7 s

    1.7 s

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

  • Speed Index: 8.6 s

    8.6 s

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

  • First Contentful Paint: 3.0 s

    3.0 s

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

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

    +38%

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

  • Cumulative Layout Shift: 0.184

    0.184

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

  • 6 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +9%

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

6 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • 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 INP: 143 ms

    143 ms

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

  • Real-user CLS: 0.04

    0.04

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

  • Real-user FCP: 1.3 s

    1.3 s

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

  • Real-user TTFB: 498 ms

    498 ms

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

Images and page weight

5 to fix18
  • Page weight: 16.4 MB in 166 requests

    16.4 MB

    Your homepage downloads 16.4 MB in 166 requests on a phone: images 11.6 MB (43), scripts 3.5 MB (50) and fonts 508 KiB (12). Under 2 MB keeps phones on slow connections fast.

  • 2 images over 500 KB

    2 images weigh 4.1 MB together. On a phone connection a single image that size takes seconds.

  • 2 images far larger than shown

    2.5 MB

    2 images are downloaded at several times the size a phone draws them, for example Homepage-Banner.png at 1,920 px wide, shown at 351 px. Resized copies would save about 2.5 MB.

  • 6 images in older formats

    6 images (4.6 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.

  • 2 images below the first screen load straight away

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

  • About 4.6 g of CO₂ per visit

    4.64 g

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

Accessibility

2 to fixGoogle 9797
  • Hidden but focusable

    6 elements hidden from screen readers can still receive keyboard focus.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 27 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 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 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

Google 100100
  • Open Graph partly set

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

  • 113 internal links, 30 external

    The homepage links to 113 pages on independenceaustralia.com.au and 30 external pages.

7 checks passed
  • Meta description: 120 characters

    Your meta description is 120 characters: “Independence Australia is a social enterprise that provides choices for people with a disability or other personal need.”.

  • One H1 headline

    Your main headline reads: “Australia’s Trusted NDIS Service Provider for Independent Living.”.

  • Title: 57 characters

    Your title is a healthy 57 characters: “Independence Australia | Registered NDIS Service Provider”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, Organization, WebPage 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.independenceaustralia.com.au/sitemap_index.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

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

Other pages

100
  • 15 internal pages checked

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

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

2 to fixGoogle 7391
  • 5 third-party cookies

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

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Invalid or unexpected token”.

  • Browser-reported issues

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

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust 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 424 words of copy

    The homepage carries about 424 words of visible text.

3 checks passed
  • 10 calls to action

    The homepage has 10 calls to action, for example “Contact Us”, “Get in Touch” and “Product and Order Enquiries”.

  • Analytics in place

    Analytics detected: Google Tag Manager, Meta Pixel and LinkedIn Insight.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

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

  • 12 cookies set on arrival

    12

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

  • 28 other companies contacted

    Loading the homepage contacts 28 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 independenceaustralia.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
WordPress
Framework
jQuery
Analytics
Google Tag Manager
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 34 issues on independenceaustralia.com.au, including 21 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