Website review, no card needed

csbb.catholic.edu.au logo

csbb.catholic.edu.au website review

Visit site (opens in a new tab)Reviewed 28 October 202626 issues · 79 checks

This review found 26 issues worth fixing on csbb.catholic.edu.au, 10 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
1.2 s817 msMay 9Oct 241.1 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.1 s
May 16, 20261.1 s
May 23, 2026936 ms
May 30, 2026903 ms
Jun 6, 2026912 ms
Jun 13, 2026859 ms
Jun 20, 2026903 ms
Jun 27, 2026944 ms
Jul 4, 2026953 ms
Jul 11, 20261.0 s
Jul 18, 20261.0 s
Jul 25, 2026970 ms
Aug 1, 2026945 ms
Aug 8, 2026943 ms
Aug 15, 2026904 ms
Aug 22, 2026963 ms
Aug 29, 2026992 ms
Sep 5, 2026918 ms
Sep 12, 2026974 ms
Sep 19, 2026938 ms
Sep 26, 2026928 ms
Oct 3, 20261.0 s
Oct 10, 2026994 ms
Oct 17, 20261.1 s
Oct 24, 20261.1 s
Real-visitor tap response (INP)75th percentile, phones
72 ms52 msMay 9Oct 2470 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202655 ms
May 16, 202657 ms
May 23, 202654 ms
May 30, 202656 ms
Jun 6, 202662 ms
Jun 13, 202662 ms
Jun 20, 202664 ms
Jun 27, 202663 ms
Jul 4, 202662 ms
Jul 11, 202662 ms
Jul 18, 202662 ms
Jul 25, 202662 ms
Aug 1, 202662 ms
Aug 8, 202670 ms
Aug 15, 202666 ms
Aug 22, 202665 ms
Aug 29, 202668 ms
Sep 5, 202662 ms
Sep 12, 202661 ms
Sep 19, 202663 ms
Sep 26, 202662 ms
Oct 3, 202662 ms
Oct 10, 202670 ms
Oct 17, 202665 ms
Oct 24, 202670 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 csbb.catholic.edu.au (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. csbb.catholic.edu.au at 0.5 s0.5 s
  2. csbb.catholic.edu.au at 0.9 s0.9 s
  3. csbb.catholic.edu.au at 1.4 s1.4 s
  4. csbb.catholic.edu.au at 1.8 s1.8 s
  5. csbb.catholic.edu.au at 2.3 s2.3 s
  6. csbb.catholic.edu.au at 2.8 s2.8 s
  7. csbb.catholic.edu.au at 3.2 s3.2 s
  8. csbb.catholic.edu.au at 3.7 s3.7 s

Speed

5 to fix72
  • Render-blocking requests

    3.5 s

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

  • Reduce unused JavaScript

    1.1 s · 211 KiB

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

  • Improve image delivery

    1.0 s · 184 KiB

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

  • Mobile performance score: 72

    72/100

    Your mobile performance score is 72 (desktop: 97). Pages that score under 90 lose visitors before the first paint.

  • Minify JavaScript

    330 ms · 86 KiB

    86 KiB could be saved by minifying JavaScript.

  • Reduce unused CSS

    150 ms · 43 KiB

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

  • Document request latency

    33 KiB

    The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

  • Phones get a much slower page than desktops

    Desktop scores 97 but mobile only 72. A gap that wide usually means heavy scripts and images that hit phones hardest.

  • 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 third-party service on the page

    1 third-party service load with your homepage (Google Fonts), adding 37 KiB and 0 ms of main-thread time.

2 checks passed
  • Main-thread work: 0.4 s

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

  • Server response: 186 ms

    186 ms

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

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 5.3 s

    5.3 s

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

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

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

    +21%

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

  • Speed Index: 4.8 s

    4.8 s

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

  • Time to Interactive: 5.3 s

    5.3 s

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

  • 9 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    +1%

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

8 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: 1.1 s

    1.1 s

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

  • Real-user INP: 67 ms

    67 ms

    Real visitors wait 67 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.

  • Real-user FCP: 1.0 s

    1.0 s

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

  • Real-user TTFB: 581 ms

    581 ms

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

  • Cumulative Layout Shift: 0.002

    0.002

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

  • Total Blocking Time: 0 ms

    0 ms

    Scripts block the page for only 0 ms while loading. Good is under 200 ms.

Images and page weight

1 to fix70
  • Page weight: 6.8 MB in 36 requests

    6.8 MB

    Your homepage downloads 6.8 MB in 36 requests on a phone: media 5.7 MB (1), images 684 KiB (21) and scripts 316 KiB (9). Under 2 MB keeps phones on slow connections fast.

  • About 1.9 g of CO₂ per visit

    1.94 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.94 g of CO₂e: 232.9 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

3 to fixGoogle 9395
  • 19 text elements with low contrast

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

  • Links must have discernible text (1 element)

    Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

  • 44 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: 44 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

4 to fixGoogle 9281
  • 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 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.

  • 13 links with vague text

    13 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • No X (Twitter) card tag

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

  • 85 internal links, 4 external

    The homepage links to 85 pages on csbb.catholic.edu.au and 4 external pages.

5 checks passed
  • Meta description: 151 characters

    Your meta description is 151 characters: “Catholic Schools Broken Bay is the fastest-growing Catholic school system in NSW. Empower your child to thrive and grow…”.

  • Title: 53 characters

    Your title is a healthy 53 characters: “Catholic Schools in NSW | Catholic Schools Broken Bay”.

  • Canonical URL set

    The canonical URL is https://csbb.catholic.edu.au/.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://csbb.catholic.edu.au/sitemap.xml.

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://csbb.catholic.edu.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 (847 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 2 pages without a meta description

    https://csbb.catholic.edu.au/schools and https://csbb.catholic.edu.au/enrol/enrolment-journey 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://csbb.catholic.edu.au/enrol/enrolment-journey, whose canonical is https://csbb.catholic.edu.au/enrol/enrolling-with-us. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 57 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.

  • 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

1 to fixGoogle 10093
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix71
  • 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.

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

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

    The homepage carries about 690 words of visible text.

4 checks passed
  • 13 calls to action

    The homepage has 13 calls to action, for example “Contact Us”, “Contact for Suppliers and Contractors” and “Learn more”.

  • 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: 12 testimonial or review blocks and “over 18,000 students”.

  • Phone number on the homepage

    Your phone number is on the homepage.

Privacy and tracking

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

  • 2 other companies contacted

    Loading the homepage contacts 2 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 csbb.catholic.edu.au, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

  • The footer still says © 2025.

Stack

CMS
Drupal
Framework
jQuery
Hosting
Mammoth Media Pty Ltd

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 26 issues on csbb.catholic.edu.au, including 11 speed issues, 4 SEO issues and 3 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