Website review, no card needed

safeplaces.com.au logo

safeplaces.com.au website review

Visit site (opens in a new tab)Reviewed 1 November 202634 issues · 81 checks

This review found 34 issues worth fixing on safeplaces.com.au, 11 of them high impact, across 81 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
2.1 s1.7 sMay 9Oct 102.1 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.8 s
May 16, 20261.8 s
May 23, 20261.9 s
May 30, 20261.9 s
Jun 6, 20262.0 s
Jun 13, 20262.0 s
Jun 20, 20262.0 s
Jun 27, 20261.9 s
Jul 4, 20261.8 s
Jul 11, 20261.8 s
Jul 18, 20261.8 s
Jul 25, 20261.8 s
Aug 1, 20261.8 s
Aug 8, 20261.8 s
Aug 15, 20261.9 s
Aug 22, 20261.9 s
Aug 29, 20261.9 s
Sep 5, 20261.9 s
Sep 12, 20261.9 s
Sep 19, 20261.9 s
Sep 26, 20262.1 s
Oct 3, 20262.1 s
Oct 10, 20262.1 s
Real-visitor tap response (INP)75th percentile, phones
97 ms84 msMay 9Oct 1095 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202692 ms
May 16, 202692 ms
May 23, 202690 ms
May 30, 202692 ms
Jun 6, 202691 ms
Jun 13, 202690 ms
Jun 20, 202691 ms
Jun 27, 202690 ms
Jul 4, 202690 ms
Jul 11, 202689 ms
Jul 18, 202686 ms
Jul 25, 202685 ms
Aug 1, 202685 ms
Aug 8, 202685 ms
Aug 15, 202687 ms
Aug 22, 202687 ms
Aug 29, 202688 ms
Sep 5, 202690 ms
Sep 12, 202691 ms
Sep 19, 202692 ms
Sep 26, 202692 ms
Oct 3, 202692 ms
Oct 10, 202695 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 safeplaces.com.au (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

7 to fix47
  • Render-blocking requests

    6.2 s

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

  • Reduce unused JavaScript

    3.2 s · 602 KiB

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

  • Use efficient cache lifetimes

    2.5 s · 556 KiB

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

  • Mobile performance score: 47

    47/100

    Your mobile performance score is 47. 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 (Squarespace, Facebook and Google Tag Manager and others), adding 1.5 MB and 877 ms of main-thread time.

  • Improve image delivery

    600 ms · 251 KiB

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

  • Squarespace adds 406 ms

    406 ms

    Squarespace costs a phone 406 ms of main-thread work and 855 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.

  • 8 long tasks on the main thread

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

  • Reduce unused CSS

    150 ms · 56 KiB

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

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

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

2 checks passed
  • Main-thread work: 1.5 s

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

  • Server response: 27 ms

    27 ms

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

Core Web Vitals

6 to fix55
  • Largest Contentful Paint: 14.5 s

    14.5 s

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

  • First Contentful Paint: 6.4 s

    6.4 s

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

  • Time to Interactive: 14.5 s

    14.5 s

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

  • Speed Index: 7.1 s

    7.1 s

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

  • Total Blocking Time: 441 ms

    441 ms

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

  • 1 image without width and height

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

  • Tap response (INP) held steady for real visitors

    +2%

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

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

    +15%

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

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

2 to fix81
  • Page weight: 2.1 MB in 60 requests

    2.1 MB

    Your homepage downloads 2.1 MB in 60 requests on a phone: scripts 1.4 MB (33), images 318 KiB (7) and fonts 170 KiB (6). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    Website+Image+1.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • About 0.6 g of CO₂ per visit

    0.58 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

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

Accessibility

8 to fixGoogle 7486
  • 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.

  • 2 tap targets too small

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

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

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

    All page content should be contained by landmarks: 3 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.

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

  • 4 links without text

    4 visible links have no text or label, so screen readers cannot say where they go.

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

1 checks passed
  • 31 automated accessibility rules passed

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

SEO

4 to fixGoogle 8582
  • Title is short (24 characters)

    Your title is only 24 characters: “Safe Places For Children”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is short (61 characters)

    Your meta description is only 61 characters: “Supporting young people through therapeutic residential care.”. 70 to 160 characters is enough to sell the click.

  • Structured data has 2 problems

    Structured data found (LocalBusiness, Organization and WebSite) but with 2 problems, for example “WebSite: image is not an absolute URL ("//images.squarespace-cdn.com/content/v1/538e813be4b0f23b0d7…”.

  • 6 links crawlers can't follow

    6 links have no real href, so search engines can't follow them.

  • 42 internal links, 10 external

    The homepage links to 42 pages on safeplaces.com.au and 10 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “Safe Places For Children”.

  • Canonical URL set

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

  • 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://www.safeplaces.com.au/sitemap.xml.

AI search readiness

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

    Your Organization JSON-LD is missing name, url, logo and description. 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.safeplaces.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 (257 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix80
  • 1 linked page hidden from search

    https://www.safeplaces.com.au/work-with-us is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 2 pages share a title

    https://www.safeplaces.com.au/working-at-safe-places-copy-1 and https://www.safeplaces.com.au/work-with-us all use the title “Working at Safe Places — Safe Places For Children”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 9 pages without a meta description

    https://www.safeplaces.com.au/about-us, https://www.safeplaces.com.au/governance, https://www.safeplaces.com.au/corporate-structure, https://www.safeplaces.com.au/young-peoples-stories, https://www.safeplaces.com.au/youth-workers and https://www.safeplaces.com.au/working-at-safe-places-copy-1 and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page with very little text

    https://www.safeplaces.com.au/contact-it has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 15 internal pages checked

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

4 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 an H1

    Each page we checked has a main headline.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://static1.squarespace.com/static/sitecss/538e813be4b0f23b0d796dd9/151/4f73704924acb4…”.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix93
  • Thin social proof

    Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

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

    The homepage carries about 250 words of visible text.

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “CONTACT US”.

  • 3 calls to action

    The homepage has 3 calls to action, for example “Contact Us” and “Contact our IT team”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 1 email link.

  • Phone number on the homepage

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

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads 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.

  • 6 cookies set on arrival

    6

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

  • 13 other companies contacted

    Loading the homepage contacts 13 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 safeplaces.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
Squarespace
Framework
jQuery
Analytics
Google Tag Manager
Hosting
Squarespace

Company

Employees
81
Founded
2021
Headquarters
Brisbane

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 safeplaces.com.au, including 13 speed issues, 4 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