Website review, no card needed

hamlin.org.au logo

hamlin.org.au website review

Visit site (opens in a new tab)Reviewed 5 November 202639 issues · 65 checks

This review found 39 issues worth fixing on hamlin.org.au, 16 of them high impact, across 65 checks. The most urgent: reduce unused JavaScript. 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
6.7 s2.6 sMay 16Oct 316.2 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20264.8 s
May 23, 20265.4 s
May 30, 20265.4 s
Jun 6, 20265.4 s
Jun 13, 20266.1 s
Jun 20, 20265.6 s
Jun 27, 20265.8 s
Jul 4, 20265.8 s
Jul 11, 20265.1 s
Jul 18, 20264.2 s
Jul 25, 20263.7 s
Aug 1, 20263.1 s
Aug 8, 20263.8 s
Aug 15, 20265.2 s
Aug 22, 20265.4 s
Aug 29, 20265.1 s
Sep 5, 20264.9 s
Sep 12, 20264.5 s
Sep 19, 20264.0 s
Sep 26, 20263.4 s
Oct 3, 20263.6 s
Oct 10, 20264.0 s
Oct 17, 20265.0 s
Oct 24, 20266.1 s
Oct 31, 20266.2 s
Real-visitor tap response (INP)75th percentile, phones
215 ms100 msMay 30Oct 31114 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026146 ms
Jun 6, 2026133 ms
Jun 13, 2026124 ms
Jun 20, 2026139 ms
Jun 27, 2026167 ms
Jul 4, 2026169 ms
Jul 11, 2026175 ms
Jul 18, 2026146 ms
Jul 25, 2026131 ms
Aug 29, 2026193 ms
Sep 5, 2026202 ms
Sep 12, 2026184 ms
Sep 19, 2026177 ms
Oct 3, 2026134 ms
Oct 10, 2026125 ms
Oct 17, 2026129 ms
Oct 24, 2026113 ms
Oct 31, 2026114 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 hamlin.org.au (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. hamlin.org.au at 0.9 s0.9 s
  2. hamlin.org.au at 1.8 s1.8 s
  3. hamlin.org.au at 2.8 s2.8 s
  4. hamlin.org.au at 3.7 s3.7 s
  5. hamlin.org.au at 4.6 s4.6 s
  6. hamlin.org.au at 5.5 s5.5 s
  7. hamlin.org.au at 6.5 s6.5 s
  8. hamlin.org.au at 7.4 s7.4 s

Speed

12 to fix52
  • Reduce unused JavaScript

    3.6 s · 728 KiB

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

  • Font display

    2.3 s

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

  • Reduce unused CSS

    1.6 s · 325 KiB

    About 325 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.6 s faster on a phone.

  • Render-blocking requests

    1.8 s

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

  • Use efficient cache lifetimes

    6.0 MB

    20 files are served with short cache lifetimes, so returning visitors download them again (6.0 MB).

  • Improve image delivery

    2.9 MB

    7 images could be 2.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 6 third-party services on the page

    6 third-party services load with your homepage (YouTube, Google CDN and Other Google APIs/SDKs and others), adding 7.5 MB and 639 ms of main-thread time.

  • Mobile performance score: 52

    52/100

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

  • Azure Web Services adds 0 ms

    0 ms

    Azure Web Services costs a phone 0 ms of main-thread work and 6.0 MB 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.

  • YouTube adds 477 ms

    477 ms

    YouTube costs a phone 477 ms of main-thread work and 987 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.

  • 1,612 HTML elements

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

  • Google CDN adds 117 ms

    117 ms

    Google CDN costs a phone 117 ms of main-thread work and 390 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.

  • 6 long tasks on the main thread

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

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

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

  • Server response: 398 ms

    398 ms

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

Core Web Vitals

9 to fix50
  • 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 LCP: 7.8 s

    7.8 s

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

  • Real-user FCP: 7.3 s

    7.3 s

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

  • First Contentful Paint: 10.4 s

    10.4 s

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

  • Largest Contentful Paint: 16.4 s

    16.4 s

    Your largest element takes 16.4 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: 17.2 s

    17.2 s

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

  • Time to Interactive: 33.0 s

    33.0 s

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

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

    +21%

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

  • Real-user TTFB: 1.5 s

    1.5 s

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

4 checks passed
  • Real-user CLS: 0.02

    0.02

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

  • Tap response (INP) got 19% faster for real visitors

    -19%

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

  • Total Blocking Time: 182 ms

    182 ms

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

  • Cumulative Layout Shift: 0.016

    0.016

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

Images and page weight

1 to fix33
  • Page weight: 8.4 MB in 50 requests

    8.4 MB

    Your homepage downloads 8.4 MB in 50 requests on a phone: images 5.9 MB (17), scripts 1.2 MB (7) and fonts 480 KiB (7). Under 2 MB keeps phones on slow connections fast.

  • About 2.4 g of CO₂ per visit

    2.39 g

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

Accessibility

2 to fixGoogle 8794
  • 3 text elements with low contrast

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

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • No main landmark

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

1 checks passed
  • 14 automated accessibility rules passed

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

SEO

6 to fixGoogle 9175
  • 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 canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • No robots.txt

    There is no robots.txt at hamlin.org.au/robots.txt, the first file search crawlers ask for.

  • 12 links with vague text

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

  • Only 0 internal links

    The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

4 checks passed
  • Meta description: 116 characters

    Your meta description is 116 characters: “Catherine Hamlin Fistula Foundation is an Australian nonprofit working towards ending obstetric fistula in Ethiopia.”.

  • Title: 50 characters

    Your title is a healthy 50 characters: “Australian Charity Eradicating Fistula in Ethiopia”.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.hamlin.org.au/sitemap.xml.

AI search readiness

1 to fix83
  • 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://www.hamlin.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
  • AI answer engines may read the site

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

Best practices

2 to fixGoogle 7389
  • 5 third-party cookies

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

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “The Content Security Policy directive 'upgrade-insecure-requests' is ignored when delivered in a report-only policy.”.

  • Browser-reported issues

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix33
  • 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 calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • 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 direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • Only about 1 words

    The homepage has only about 1 words of visible text; thin pages give Google and first-time buyers little to go on.

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

1 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager and Meta Pixel.

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, Hotjar 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.

  • 8 cookies set on arrival

    8

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

  • 15 other companies contacted

    Loading the homepage contacts 15 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 hamlin.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

Analytics
Google Tag Manager
Hosting
Azure

Company

Headquarters
Sydney

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 hamlin.org.au, including 21 speed issues, 6 SEO issues and 5 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