Website review, no card needed
ruralaid.org.au website review
Visit site (opens in a new tab)Reviewed 20 October 202643 issues · 91 checks
This review found 43 issues worth fixing on ruralaid.org.au, 21 of them high impact, across 91 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
71CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 5.3 s |
| May 9, 2026 | 5.3 s |
| May 16, 2026 | 5.3 s |
| May 23, 2026 | 5.2 s |
| May 30, 2026 | 5.5 s |
| Jun 6, 2026 | 5.4 s |
| Jun 13, 2026 | 5.4 s |
| Jun 20, 2026 | 5.3 s |
| Jun 27, 2026 | 5.3 s |
| Jul 4, 2026 | 5.2 s |
| Jul 11, 2026 | 5.3 s |
| Jul 18, 2026 | 5.5 s |
| Jul 25, 2026 | 5.2 s |
| Aug 1, 2026 | 5.3 s |
| Aug 8, 2026 | 5.3 s |
| Aug 15, 2026 | 5.2 s |
| Aug 22, 2026 | 5.4 s |
| Aug 29, 2026 | 5.4 s |
| Sep 5, 2026 | 5.4 s |
| Sep 12, 2026 | 5.7 s |
| Sep 19, 2026 | 5.9 s |
| Sep 26, 2026 | 6.2 s |
| Oct 3, 2026 | 6.5 s |
| Oct 10, 2026 | 6.4 s |
| Oct 17, 2026 | 6.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 120 ms |
| May 9, 2026 | 115 ms |
| May 16, 2026 | 128 ms |
| May 23, 2026 | 135 ms |
| May 30, 2026 | 142 ms |
| Jun 6, 2026 | 136 ms |
| Jun 13, 2026 | 127 ms |
| Jun 20, 2026 | 125 ms |
| Jun 27, 2026 | 125 ms |
| Jul 4, 2026 | 128 ms |
| Jul 11, 2026 | 128 ms |
| Jul 18, 2026 | 131 ms |
| Jul 25, 2026 | 130 ms |
| Aug 1, 2026 | 127 ms |
| Aug 8, 2026 | 132 ms |
| Aug 15, 2026 | 132 ms |
| Aug 22, 2026 | 142 ms |
| Aug 29, 2026 | 144 ms |
| Sep 5, 2026 | 147 ms |
| Sep 12, 2026 | 153 ms |
| Sep 19, 2026 | 168 ms |
| Sep 26, 2026 | 159 ms |
| Oct 3, 2026 | 154 ms |
| Oct 10, 2026 | 148 ms |
| Oct 17, 2026 | 146 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
How it loaded on a phone
0.9 s
1.8 s
2.7 s
3.6 s
4.5 s
5.4 s
6.3 s
7.2 s
Speed
Use efficient cache lifetimes
3.8 s · 2.8 MB42 files are served with short cache lifetimes, so returning visitors download them again (2.8 MB).
Reduce unused JavaScript
3.5 s · 754 KiBAbout 754 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.5 s faster on a phone.
Render-blocking requests
3.3 s12 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.3 s.
Reduce unused CSS
2.1 s · 318 KiBAbout 318 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 2.1 s faster on a phone.
Mobile performance score: 40
40/100Your mobile performance score is 40 (desktop: 57). 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 (YouTube, Google Tag Manager and Facebook and others), adding 1.7 MB and 1.5 s of main-thread time.
YouTube adds 546 ms
546 msYouTube costs a phone 546 ms of main-thread work and 974 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 Tag Manager adds 542 ms
542 msGoogle Tag Manager costs a phone 542 ms of main-thread work and 344 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.
9 long tasks on the main thread
9 long tasks block the main thread while loading, the longest for 519 ms. During a long task the page ignores taps.
Minify CSS
300 ms · 43 KiB43 KiB could be saved by minifying CSS.
Facebook adds 264 ms
264 msFacebook costs a phone 264 ms of main-thread work and 280 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.
Main-thread work: 2.8 s
A phone's processor spends 2.8 s on main-thread work while loading, 1.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Improve image delivery
85 KiB3 images could be 85 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
24 KiBPolyfills for old browsers add 24 KiB JavaScript that modern phones do not need.
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.
Minify JavaScript
3 KiB3 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 2 ms
2 msYour server sent the HTML in 2 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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: 6.6 s
6.6 sReal visitors wait 6.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 6.2 s
6.2 sReal visitors see the first content after 6.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 5.7 s
5.7 sReal visitors wait 5.7 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 16.5 s
16.5 sYour largest element takes 16.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Our Story Rural Aid is Australia’s leading charity supporti…”.
Speed Index: 14.8 s
14.8 sVisually, the page fills in at 14.8 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 23.9 s
23.9 sThe page becomes fully interactive after 23.9 s. Good is under 3.8 s.
First Contentful Paint: 4.0 s
4.0 sThe first text or image appears after 4.0 s on a phone. Good is under 1.8 s.
Total Blocking Time: 624 ms
624 msScripts block taps and scrolling for 624 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) got 25% slower for real visitors
+25%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 120 ms to 146 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
13 images without width and height
13 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) got 18% slower for real visitors
+18%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 5.3 s to 6.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0.084
0.084The layout barely moves while loading (CLS 0.084, good is under 0.1).
Images and page weight
Page weight: 4.3 MB in 90 requests
4.3 MBYour homepage downloads 4.3 MB in 90 requests on a phone: images 2.2 MB (29), scripts 1.7 MB (22) and stylesheets 285 KiB (10). Under 2 MB keeps phones on slow connections fast.
9 images in older formats
9 images (1.9 MB) 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.
3 images below the first screen load straight away
3 images further down the page (103 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.2 g of CO₂ per visit
1.22 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.22 g of CO₂e: 146.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
6 text elements with low contrast
6 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.
13 images without alt text
13 images have no alt text, which hurts accessibility and image search.
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.
8 links without text
8 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h2 → h5), which makes the page harder to scan with a screen reader.
1 checks passed
38 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: 38 passed and 7 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Structured data has 1 problem
Structured data found (BreadcrumbList, LocalBusiness, Organization and WebPage) but with 1 problem, for example “Organization: logo is not an absolute URL ("https://www.ruralaid.org.au/wp-content/uploads/2026/01/RuralAid_logo_cmyk.jpg")”.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
44 internal links, 19 external
The homepage links to 44 pages on ruralaid.org.au and 19 external pages.
6 checks passed
Meta description: 141 characters
Your meta description is 141 characters: “Welcome to Rural Aid Australia. Rural Aid provides critical support including water, fodder (hay) and counselling assis…”.
Title: 47 characters
Your title is a healthy 47 characters: “Home - Rural Aid - Supporting Rural Communities”.
Canonical URL set
The canonical URL is https://www.ruralaid.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://www.ruralaid.org.au/sitemap_index.xml.
AI search readiness
4 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 (330 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.ruralaid.org.au/llms.txt (2 KiB, 21 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a meta description
https://www.ruralaid.org.au/farmer-stories has no meta description, so Google writes the search snippet from whatever text it finds.
13 pages share a meta description
https://www.ruralaid.org.au/services-provided, https://www.ruralaid.org.au/about, https://www.ruralaid.org.au/buyabale/about-buy-a-bale, https://www.ruralaid.org.au/annual-reports, https://www.ruralaid.org.au/board-of-directors and https://www.ruralaid.org.au/job-portal and 7 others use the same meta description. A description written for each page earns more clicks.
8 pages without an H1
https://www.ruralaid.org.au/annual-reports, https://www.ruralaid.org.au/board-of-directors, https://www.ruralaid.org.au/job-portal, https://www.ruralaid.org.au/faq, https://www.ruralaid.org.au/founders and https://www.ruralaid.org.au/leadership-team and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.
13 pages slow to respond
https://www.ruralaid.org.au/services-provided, https://www.ruralaid.org.au/about, https://www.ruralaid.org.au/buyabale/about-buy-a-bale, https://www.ruralaid.org.au/annual-reports, https://www.ruralaid.org.au/job-portal and https://www.ruralaid.org.au/corporate-partnerships and 7 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 29 found) and read each the way a search engine does.
5 checks passed
Linked pages load
14 pages of 15 loaded without an error (the rest turned automated requests away).
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
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 14 pages that loaded have a <title>.
Best practices
11 small tap targets
11 of 16 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
6 third-party cookies
6 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 “Cannot read properties of null (reading 'add')”.
9 distorted images
9 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
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
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
Only about 242 words
The homepage has only about 242 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “CONTACT US”.
8 calls to action
The homepage has 8 calls to action, for example “CONTACT US”, “About Buy a Bale” and “Shop to Donate”.
Analytics in place
Analytics detected: Google Tag Manager and Umami.
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
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Criteo, Google Ads, Google Analytics, Google Tag Manager and LinkedIn Insight and 2 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.
12 cookies set on arrival
12Opening the homepage sets 12 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.
26 other companies contacted
Loading the homepage contacts 26 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 ruralaid.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
- CMS
- WordPress
- Framework
- jQuery
- 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 43 issues on ruralaid.org.au, including 23 speed issues, 2 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.