Website review, no card needed

salvationarmy.org.au logo

salvationarmy.org.au website review

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

This review found 34 issues worth fixing on salvationarmy.org.au, 8 of them high impact, across 79 checks. The most urgent: google Tag Manager adds 1.4 s. 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.7 s765 msMay 9Oct 241.1 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.2 s
May 16, 20262.2 s
May 23, 20262.2 s
May 30, 20262.3 s
Jun 6, 20262.4 s
Jun 13, 20262.4 s
Jun 20, 20262.5 s
Jun 27, 20262.5 s
Jul 4, 20262.4 s
Jul 11, 20262.3 s
Jul 18, 20262.1 s
Jul 25, 20261.8 s
Aug 1, 20261.4 s
Aug 8, 20261.2 s
Aug 15, 20261.1 s
Aug 22, 20261.1 s
Aug 29, 20261.0 s
Sep 5, 2026988 ms
Sep 12, 2026996 ms
Sep 19, 20261.0 s
Sep 26, 20261.1 s
Oct 3, 20261.1 s
Oct 10, 20261.1 s
Oct 17, 20261.1 s
Oct 24, 20261.1 s
Real-visitor tap response (INP)75th percentile, phones
336 ms229 msMay 9Oct 24324 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026241 ms
May 16, 2026243 ms
May 23, 2026241 ms
May 30, 2026245 ms
Jun 6, 2026249 ms
Jun 13, 2026249 ms
Jun 20, 2026253 ms
Jun 27, 2026256 ms
Jul 4, 2026258 ms
Jul 11, 2026261 ms
Jul 18, 2026263 ms
Jul 25, 2026272 ms
Aug 1, 2026284 ms
Aug 8, 2026293 ms
Aug 15, 2026300 ms
Aug 22, 2026302 ms
Aug 29, 2026302 ms
Sep 5, 2026307 ms
Sep 12, 2026307 ms
Sep 19, 2026311 ms
Sep 26, 2026313 ms
Oct 3, 2026315 ms
Oct 10, 2026319 ms
Oct 17, 2026320 ms
Oct 24, 2026324 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 salvationarmy.org.au (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

11 to fix73
  • Google Tag Manager adds 1.4 s

    1.4 s

    Google Tag Manager costs a phone 1.4 s of main-thread work and 1.2 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.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and TikTok and others), adding 1.8 MB and 2.0 s of main-thread time.

  • Mobile performance score: 73

    73/100

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

  • Use efficient cache lifetimes

    300 ms · 595 KiB

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

  • Reduce unused JavaScript

    794 KiB

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

  • Render-blocking requests

    650 ms

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

  • Reduce initial server response time

    511 ms

    Reduce initial server response time. Google estimates savings of 511 ms on a phone.

  • Document request latency

    500 ms

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

  • Main-thread work: 3.8 s

    A phone's processor spends 3.8 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 308 ms. During a long task the page ignores taps.

  • Server response: 611 ms

    611 ms

    Your server takes 611 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.

  • Reduce unused CSS

    280 ms · 68 KiB

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

  • Legacy JavaScript

    91 KiB

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

  • Minify JavaScript

    8 KiB

    8 KiB could be saved by minifying JavaScript.

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

Core Web Vitals

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

  • Time to Interactive: 22.0 s

    22.0 s

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

  • Total Blocking Time: 1.4 s

    1.4 s

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

  • Real-user INP: 324 ms

    324 ms

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

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

    +33%

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

9 checks passed
  • Real-user LCP: 1.0 s

    1.0 s

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

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

    449 ms

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

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

    -51%

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

  • Largest Contentful Paint: 2.1 s

    2.1 s

    Your largest element renders in 2.1 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the image.

  • Speed Index: 2.3 s

    2.3 s

    Visually, the page fills in at 2.3 s (Speed Index), inside the 3.4 s “good” threshold.

  • First Contentful Paint: 1.2 s

    1.2 s

    The first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0.001

    0.001

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

Images and page weight

1 to fix85
  • Page weight: 3.1 MB in 176 requests

    3.1 MB

    Your homepage downloads 3.1 MB in 176 requests on a phone: scripts 2.5 MB (89), fonts 268 KiB (3) and images 170 KiB (23). Under 2 MB keeps phones on slow connections fast.

  • 1 image below the first screen load straight away

    1 image further down the page (22 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 0.9 g of CO₂ per visit

    0.87 g

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

3 to fixGoogle 9396
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

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

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

2 checks passed
  • Every image has alt text

    All 17 images in the HTML carry an alt attribute.

  • 42 automated accessibility rules passed

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

SEO

4 to fixGoogle 9284
  • Title is long (77 characters)

    Your title is 77 characters, so Google will cut it off around 60: “The Salvation Army Australia - Believe in good | The Salvation Army Australia”.

  • Structured data has 1 problem

    Structured data found (untyped) but with 1 problem, for example “ld+json block 1 is not valid JSON (Unexpected non-whitespace character after JSON at position 2)”.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 3 links with vague text

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

  • 37 internal links, 4 external

    The homepage links to 37 pages on salvationarmy.org.au and 4 external pages.

5 checks passed
  • Meta description: 160 characters

    Your meta description is 160 characters: “The Salvation Army Australia provides hope and support through social services, emergency relief, and community program…”.

  • One H1 headline

    Your main headline reads: “Be the hope families need this Christmas”.

  • Canonical URL set

    The canonical URL is https://www.salvationarmy.org.au/.

  • 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.salvationarmy.org.au/n/sitemap.xml.

AI search readiness

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

  • Parts of the site are closed to 1 AI crawler

    Your robots.txt lets Perplexity (PerplexityBot) read the homepage but closes other sections to them, so answers about those pages can't cite you.

  • No llms.txt

    There is no https://www.salvationarmy.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.

1 checks passed
  • Text is in the HTML

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

Other pages

3 to fix85
  • 1 page without a meta description

    https://www.salvationarmy.org.au/ways-to-give/cmas/26/w1/lf has 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://www.salvationarmy.org.au/link/df7730963dfb40699469819dcff0e971.aspx, whose canonical is https://www.salvationarmy.org.au/about-us/commitment-to-reconciliation. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 1 page without an H1

    https://www.salvationarmy.org.au/ways-to-give/cmas/26/w1/lf has no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page slow to respond

    https://www.salvationarmy.org.au/link/df7730963dfb40699469819dcff0e971.aspx took over 3 s to send its HTML from our server.

  • 15 internal pages checked

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

  • Titles are unique

    Every page we checked has its own title.

  • 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 10078
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=25084334&tm=gtm002&Ver=2&mid=922d98c5-f9ad-43de-999c-61a541b482ea&bo=1&sid=38c67500d59011f186061507020f7877&vid=38c6b680d59011f18fae255787d7ac20&vids=1&msclkid=N&pi=91.

  • 4 small tap targets

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

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 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 547 words of copy

    The homepage carries about 547 words of visible text.

3 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “Order now” and “Contact supporter services”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 1 email 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.

  • 36 cookies set on arrival

    36

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

  • 40 other companies contacted

    Loading the homepage contacts 40 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 salvationarmy.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

Framework
Tailwind CSS
Analytics
Google Tag Manager
Hosting
Episerver

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 salvationarmy.org.au, including 16 speed issues, 4 SEO 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