Website review, no card needed

baptistcaresa.org.au logo

baptistcaresa.org.au website review

Visit site (opens in a new tab)Reviewed 29 October 202639 issues · 79 checks

This review found 39 issues worth fixing on baptistcaresa.org.au, 14 of them high impact, across 79 checks. The most urgent: render-blocking requests. 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.1 s2.5 sMay 9Oct 243.8 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.8 s
May 16, 20262.7 s
May 23, 20262.8 s
May 30, 20262.8 s
Jun 6, 20262.7 s
Jun 13, 20262.8 s
Jun 20, 20262.7 s
Jun 27, 20262.7 s
Jul 4, 20262.9 s
Jul 11, 20262.9 s
Jul 18, 20262.9 s
Jul 25, 20262.9 s
Aug 1, 20262.9 s
Aug 8, 20262.8 s
Aug 15, 20262.8 s
Aug 22, 20262.7 s
Aug 29, 20262.8 s
Sep 5, 20263.1 s
Sep 12, 20263.6 s
Sep 19, 20263.9 s
Sep 26, 20263.9 s
Oct 3, 20263.8 s
Oct 10, 20263.7 s
Oct 17, 20263.7 s
Oct 24, 20263.8 s
Real-visitor tap response (INP)75th percentile, phones
167 ms115 msMay 9Oct 24161 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026122 ms
May 16, 2026121 ms
May 23, 2026127 ms
May 30, 2026129 ms
Jun 6, 2026135 ms
Jun 13, 2026131 ms
Jun 20, 2026136 ms
Jun 27, 2026136 ms
Jul 4, 2026132 ms
Jul 11, 2026142 ms
Jul 18, 2026137 ms
Jul 25, 2026135 ms
Aug 1, 2026141 ms
Aug 8, 2026134 ms
Aug 15, 2026130 ms
Aug 22, 2026130 ms
Aug 29, 2026126 ms
Sep 5, 2026123 ms
Sep 12, 2026136 ms
Sep 19, 2026146 ms
Sep 26, 2026153 ms
Oct 3, 2026151 ms
Oct 10, 2026157 ms
Oct 17, 2026152 ms
Oct 24, 2026161 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 baptistcaresa.org.au (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. baptistcaresa.org.au at 0.8 s0.8 s
  2. baptistcaresa.org.au at 1.7 s1.7 s
  3. baptistcaresa.org.au at 2.5 s2.5 s
  4. baptistcaresa.org.au at 3.3 s3.3 s
  5. baptistcaresa.org.au at 4.1 s4.1 s
  6. baptistcaresa.org.au at 5.0 s5.0 s
  7. baptistcaresa.org.au at 5.8 s5.8 s
  8. baptistcaresa.org.au at 6.6 s6.6 s

Speed

9 to fix55
  • Render-blocking requests

    2.5 s

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

  • Improve image delivery

    650 ms · 703 KiB

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

  • Mobile performance score: 55

    55/100

    Your mobile performance score is 55. Pages that score under 90 lose visitors before the first paint.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and Google CDN and others), adding 1.7 MB and 812 ms of main-thread time.

  • Reduce unused JavaScript

    867 KiB

    About 867 KiB of JavaScript is downloaded but never used on this page.

  • Google Tag Manager adds 500 ms

    500 ms

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

  • Use efficient cache lifetimes

    150 ms · 399 KiB

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

  • 1,552 HTML elements

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

  • Google CDN adds 61 ms

    61 ms

    Google CDN costs a phone 61 ms of main-thread work and 348 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 · 57 KiB

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

  • 11 long tasks on the main thread

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

  • Reduce unused CSS

    64 KiB

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

  • Minify CSS

    12 KiB

    12 KiB could be saved by minifying CSS.

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

2 checks passed
  • Main-thread work: 1.7 s

    A phone's processor spends 1.7 s on main-thread work while loading, 993 ms of it running JavaScript. That is comfortably low.

  • Server response: 406 ms

    406 ms

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

Core Web Vitals

10 to fix63
  • 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.1 s

    3.1 s

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

  • Largest Contentful Paint: 19.8 s

    19.8 s

    Your largest element takes 19.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

  • Speed Index: 16.0 s

    16.0 s

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

  • Time to Interactive: 23.8 s

    23.8 s

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

  • First Contentful Paint: 3.7 s

    3.7 s

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

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

    +29%

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

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

    +36%

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

  • Total Blocking Time: 205 ms

    205 ms

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

  • 10 images without width and height

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

1 checks passed
  • Cumulative Layout Shift: 0

    0

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

Images and page weight

4 to fix43
  • Page weight: 7.0 MB in 135 requests

    7.0 MB

    Your homepage downloads 7.0 MB in 135 requests on a phone: images 4.5 MB (32), scripts 2.0 MB (46) and fonts 312 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • 13 images in older formats

    13 images (2.0 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.

  • 12 images below the first screen load straight away

    12 images further down the page (1.5 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 7 images far larger than shown

    229 KiB

    7 images are downloaded at several times the size a phone draws them, for example baptistcare-cta-get-in-touch-v1.jpg at 1,200 px wide, shown at 286 px. Resized copies would save about 229 KiB.

  • About 2.0 g of CO₂ per visit

    1.97 g

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

Accessibility

7 to fixGoogle 8591
  • 7 tap targets too small

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

  • 5 text elements with low contrast

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

  • Links look like plain text

    1 link inside paragraphs relies on colour alone to stand out.

  • All page content should be contained by landmarks (14 elements)

    All page content should be contained by landmarks: 14 elements on the page fail this check, rated moderate by axe-core.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • 1 link without text

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

  • ARIA role should be appropriate for the element (1 element)

    ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

  • 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 28 images in the HTML carry an alt attribute.

  • 47 automated accessibility rules passed

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

SEO

2 to fixGoogle 9283
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • Title is short (21 characters)

    Your title is only 21 characters: “Home - BaptistCare SA”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 123 internal links, 36 external

    The homepage links to 123 pages on baptistcaresa.org.au and 36 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “Kitchen closed?”.

  • Canonical URL set

    The canonical URL is https://baptistcaresa.org.au/.

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, Organization, WebPage and WebSite.

  • 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://baptistcaresa.org.au/sitemap_index.xml.

AI search readiness

100
  • No llms.txt

    There is no https://baptistcaresa.org.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: 4 of 6 facts

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

  • Text is in the HTML

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

Other pages

5 to fix50
  • 6 linked pages are broken

    Your homepage links to https://baptistcaresa.org.au/aged-care-homes, https://baptistcaresa.org.au/home-care, https://baptistcaresa.org.au/retirement-living, https://baptistcaresa.org.au/community-housing, https://baptistcaresa.org.au/hopestreet and https://baptistcaresa.org.au/bridging-the-gap, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 2 linked pages hidden from search

    https://baptistcaresa.org.au/donate and https://baptistcaresa.org.au/donate/spring-appeal are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 2 pages share a title

    https://baptistcaresa.org.au/donate and https://baptistcaresa.org.au/donate/spring-appeal all use the title “Spring Appeal - BaptistCare SA”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 7 pages without a meta description

    https://baptistcaresa.org.au/news, https://baptistcaresa.org.au/about-us, https://baptistcaresa.org.au/donate, https://baptistcaresa.org.au/contact-us, https://baptistcaresa.org.au/donate/spring-appeal and https://baptistcaresa.org.au/adventure/free-camp-giveaway and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://baptistcaresa.org.au/provide-your-feedback, whose canonical is https://baptistcaresa.org.au/feedback. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 5 pages slow to respond

    https://baptistcaresa.org.au/news, https://baptistcaresa.org.au/provide-your-feedback, https://baptistcaresa.org.au/donate, https://baptistcaresa.org.au/donate/spring-appeal and https://baptistcaresa.org.au/adventure/free-camp-giveaway took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

2 checks passed
  • Every page has an H1

    Each page we checked has a main headline.

  • Every page has a title

    All 9 pages that loaded have a <title>.

Best practices

Google 100100
3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

    15 of 17 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix83
  • 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 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,090 words of copy

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

5 checks passed
  • 6 calls to action

    The homepage has 6 calls to action, for example “Contact”, “Register now” and “contact us”.

  • 4 short forms

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

  • Social proof on the page

    Social proof on the homepage: 61 testimonial or review blocks and 1 customer or partner logo.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Cloudflare Web Analytics.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

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

  • 10 cookies set on arrival

    10

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

  • 19 other companies contacted

    Loading the homepage contacts 19 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 baptistcaresa.org.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 Analytics | Google Tag Manager
Hosting
Cloudflare

Company

Employees
486
Founded
2008

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 baptistcaresa.org.au, including 19 speed issues, 2 SEO issues and 1 conversion gap. 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