Website review, no card needed

lifeed.org.au logo

lifeed.org.au website review

Visit site (opens in a new tab)Reviewed 24 October 202636 issues · 86 checks

This review found 36 issues worth fixing on lifeed.org.au, 16 of them high impact, across 86 checks. The most urgent: use efficient cache lifetimes. 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.7 s2.2 sMay 2Oct 172.7 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20263.7 s
May 9, 20263.9 s
May 16, 20264.1 s
May 23, 20264.2 s
May 30, 20264.2 s
Jun 6, 20264.4 s
Jun 13, 20264.3 s
Jun 20, 20264.2 s
Jun 27, 20263.9 s
Jul 4, 20263.6 s
Jul 11, 20263.3 s
Jul 18, 20263.1 s
Jul 25, 20262.9 s
Aug 1, 20262.5 s
Aug 8, 20262.5 s
Aug 15, 20262.5 s
Aug 22, 20262.5 s
Aug 29, 20262.6 s
Sep 5, 20262.6 s
Sep 12, 20262.6 s
Sep 19, 20262.6 s
Sep 26, 20262.6 s
Oct 3, 20262.6 s
Oct 10, 20262.7 s
Oct 17, 20262.7 s
Real-visitor tap response (INP)75th percentile, phones
168 ms132 msMay 2Oct 17164 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026138 ms
May 9, 2026138 ms
May 16, 2026145 ms
May 23, 2026148 ms
May 30, 2026147 ms
Jun 6, 2026149 ms
Jun 13, 2026140 ms
Jun 20, 2026140 ms
Jun 27, 2026137 ms
Jul 4, 2026137 ms
Jul 11, 2026136 ms
Jul 18, 2026136 ms
Jul 25, 2026145 ms
Aug 1, 2026143 ms
Aug 8, 2026149 ms
Aug 15, 2026152 ms
Aug 22, 2026154 ms
Aug 29, 2026147 ms
Sep 5, 2026146 ms
Sep 12, 2026146 ms
Sep 19, 2026142 ms
Sep 26, 2026147 ms
Oct 3, 2026151 ms
Oct 10, 2026157 ms
Oct 17, 2026164 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 lifeed.org.au (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. lifeed.org.au at 1.2 s1.2 s
  2. lifeed.org.au at 2.4 s2.4 s
  3. lifeed.org.au at 3.6 s3.6 s
  4. lifeed.org.au at 4.8 s4.8 s
  5. lifeed.org.au at 6.0 s6.0 s
  6. lifeed.org.au at 7.2 s7.2 s
  7. lifeed.org.au at 8.4 s8.4 s
  8. lifeed.org.au at 9.6 s9.6 s

Speed

12 to fix43
  • Use efficient cache lifetimes

    6.8 s · 3.5 MB

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

  • Reduce unused JavaScript

    1.6 s · 1.4 MB

    About 1.4 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.6 s faster on a phone.

  • Render-blocking requests

    1.9 s

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

  • Mobile performance score: 43

    43/100

    Your mobile performance score is 43 (desktop: 33). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 4.4 s

    A phone's processor spends 4.4 s on main-thread work while loading, 2.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 8 third-party services on the page

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

  • Google Tag Manager adds 939 ms

    939 ms

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

  • Google CDN adds 665 ms

    665 ms

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

  • Improve image delivery

    715 KiB

    5 images could be 715 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Facebook adds 286 ms

    286 ms

    Facebook costs a phone 286 ms of main-thread work and 226 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.

  • 20 long tasks on the main thread

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

  • 1,574 HTML elements

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

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

  • Legacy JavaScript

    54 KiB

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

  • Minify JavaScript

    18 KiB

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

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

1 checks passed
  • Server response: 195 ms

    195 ms

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

Core Web Vitals

11 to fix33
  • 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 TTFB: 1.9 s

    1.9 s

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

  • Largest Contentful Paint: 11.8 s

    11.8 s

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

  • Speed Index: 17.6 s

    17.6 s

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

  • Time to Interactive: 28.8 s

    28.8 s

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

  • Total Blocking Time: 907 ms

    907 ms

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

  • Real-user LCP: 3.4 s

    3.4 s

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

  • Real-user INP: 216 ms

    216 ms

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

  • Real-user FCP: 2.7 s

    2.7 s

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

  • First Contentful Paint: 2.0 s

    2.0 s

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

  • 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) got 16% slower for real visitors

    +16%

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

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

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

    -28%

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

  • Cumulative Layout Shift: 0.004

    0.004

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

Images and page weight

3 to fix35
  • Page weight: 6.2 MB in 116 requests

    6.2 MB

    Your homepage downloads 6.2 MB in 116 requests on a phone: scripts 2.7 MB (63), images 2.6 MB (16) and other files 364 KiB (17). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    Harolds-Big-School-HERO-header-2880X920px.svg weighs 1.2 MB. On a phone connection a single image that size takes seconds.

  • 2 images far larger than shown

    1.1 MB

    2 images are downloaded at several times the size a phone draws them, for example Harolds-Big-School-HERO-header-2880X920px.svg at 2,880 px wide, shown at 390 px. Resized copies would save about 1.1 MB.

  • 4 images in older formats

    4 images (260 KiB) 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.

  • About 1.8 g of CO₂ per visit

    1.77 g

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

1 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

5 to fixGoogle 9293
  • 2 buttons without a name

    2 buttons have no accessible name, so screen readers announce just “button”.

  • Form elements should have a visible label (4 elements)

    Form elements should have a visible label: 4 elements on the page fail this check, rated serious by axe-core.

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

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

  • 3 form fields without a label

    3 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • 2 links without text

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

  • 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 46 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 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 4 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 9294
  • Structured data has 1 problem

    Structured data found (BreadcrumbList, ImageObject, Organization and WebPage) but with 1 problem, for example “Organization: logo is not an absolute URL ("https://lifeed.org.au/wp-content/uploads/2022/01/CMYK-Life-Ed-logo-colour-pr…”.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • 167 internal links, 20 external

    The homepage links to 167 pages on lifeed.org.au and 20 external pages.

7 checks passed
  • Meta description: 131 characters

    Your meta description is 131 characters: “Trusted by schools and families for over 45 years. Life Ed delivers educational services to thousands of children acros…”.

  • One H1 headline

    Your main headline reads: “Exploring new beginnings and belonging”.

  • Title: 60 characters

    Your title is a healthy 60 characters: “Life Ed Australia - Helping to ensure every child can thrive”.

  • Canonical URL set

    The canonical URL is https://lifeed.org.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://lifeed.org.au/sitemap_index.xml.

AI search readiness

100
  • No llms.txt

    There is no https://lifeed.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 (1,672 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 1 page without an H1

    https://lifeed.org.au/forms/enquiry-form has no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://lifeed.org.au/forms/enquiry-form 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.

  • 8 pages slow to respond

    https://lifeed.org.au/what-we-do/how-we-deliver-preventative-health-education, https://lifeed.org.au/what-we-do/where-we-provide-education, https://lifeed.org.au/what-we-do/evidence-based-reports, https://lifeed.org.au/resources/parents/how-to-have-the-vape-talk-with-your-kids, https://lifeed.org.au/teachers-and-schools/guide-to-thrive-6-7-transition and https://lifeed.org.au/teachers-and-schools/the-life-ed-program/early-years-learning-program and 2 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

6 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 a meta description

    All 15 pages that loaded have a meta description.

  • 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

Google 96100
3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix92
  • 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.

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

    The homepage carries about 814 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop” and “Learn More”.

  • 11 calls to action

    The homepage has 11 calls to action, for example “Shop”, “Life Ed Shop” and “Learn More”.

  • 1 short form

    A short form (4 fields at most) is right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 29 testimonial or review blocks, 1 customer or partner logo and “600K Students”.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Meta Pixel.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager 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.

  • 15 cookies set on arrival

    15

    Opening the homepage sets 15 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 lifeed.org.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 © 2021.

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Analytics | Google Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 36 issues on lifeed.org.au, including 23 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