help.org.au website review

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

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

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

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

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

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

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

Google Tag Manager costs a phone 523 ms of main-thread work and 549 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 costs a phone 417 ms of main-thread work and 736 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.

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

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

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

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

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

23 KiB could be saved by minifying JavaScript.

7 KiB could be saved by minifying CSS.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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.

Your largest element takes 95.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “One door to open many. Connecting quality commercial soluti…”.

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

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

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

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

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

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

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

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

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

Your homepage downloads 36.5 MB in 218 requests on a phone: images 34.0 MB (138), scripts 1.8 MB (38) and other files 369 KiB (22). Under 2 MB keeps phones on slow connections fast.

27 images weigh 23.0 MB together. On a phone connection a single image that size takes seconds.

40 images (26.3 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.

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

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

2 dropdowns have no label.

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

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

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

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

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

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

Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.

Your title is only 18 characters: “Home - Help.org.au”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your meta description is 203 characters; Google truncates after about 160, so the end of your pitch is cut.

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

The homepage links to 253 pages on help.org.au and 26 external pages.

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

robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

https://www.help.org.au/social-enterprises/contract-packaging-solutions and https://www.help.org.au/contract-packaging-solutions all use the title “Contract Packaging Solutions - Help.org.au”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.help.org.au/social-enterprises/contract-packaging-solutions and https://www.help.org.au/contract-packaging-solutions use the same meta description. A description written for each page earns more clicks.

Your homepage links to 7 pages by a URL that isn't their canonical one, for example https://www.help.org.au/advanced-metal-fabrication, whose canonical is https://www.help.org.au/social-enterprises/advanced-metal-fabrication. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.help.org.au/our-locations, https://www.help.org.au/advanced-metal-fabrication, https://www.help.org.au/social-enterprises/contract-design-and-manufacture, https://www.help.org.au/social-enterprises/commercial-laser-cutting, https://www.help.org.au/social-enterprises/contract-packaging-solutions and https://www.help.org.au/contract-packaging-solutions and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

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

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://use.fontawesome.com/releases/v5.7.2/css/all.css?ver=7.1.3' from origin 'https://ww…”.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 559 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel and 1 more (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.

Opening the homepage sets 17 cookies (measured from a US location before any click).

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.

Loading the homepage contacts 31 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.