Website review, no card needed
alp.org.au website review
Visit site (opens in a new tab)Reviewed 19 October 202639 issues · 82 checks
This review found 39 issues worth fixing on alp.org.au, 10 of them high impact, across 82 checks. The most urgent: render-blocking requests. 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
79CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 1.8 s |
| May 9, 2026 | 1.8 s |
| May 16, 2026 | 1.9 s |
| May 23, 2026 | 2.0 s |
| May 30, 2026 | 1.8 s |
| Jun 6, 2026 | 1.9 s |
| Jun 13, 2026 | 1.9 s |
| Jun 20, 2026 | 1.8 s |
| Jun 27, 2026 | 1.7 s |
| Jul 4, 2026 | 1.6 s |
| Jul 11, 2026 | 1.4 s |
| Jul 18, 2026 | 1.4 s |
| Jul 25, 2026 | 1.5 s |
| Aug 1, 2026 | 1.7 s |
| Aug 8, 2026 | 1.7 s |
| Aug 15, 2026 | 1.7 s |
| Aug 22, 2026 | 1.5 s |
| Aug 29, 2026 | 1.4 s |
| Sep 5, 2026 | 1.8 s |
| Sep 12, 2026 | 1.9 s |
| Sep 19, 2026 | 2.0 s |
| Sep 26, 2026 | 2.0 s |
| Oct 3, 2026 | 1.8 s |
| Oct 10, 2026 | 1.6 s |
| Oct 17, 2026 | 1.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 147 ms |
| May 9, 2026 | 154 ms |
| May 16, 2026 | 162 ms |
| May 23, 2026 | 172 ms |
| May 30, 2026 | 148 ms |
| Jun 6, 2026 | 145 ms |
| Jun 13, 2026 | 129 ms |
| Jun 20, 2026 | 112 ms |
| Jun 27, 2026 | 120 ms |
| Jul 4, 2026 | 121 ms |
| Jul 11, 2026 | 120 ms |
| Jul 18, 2026 | 125 ms |
| Jul 25, 2026 | 113 ms |
| Aug 1, 2026 | 118 ms |
| Aug 8, 2026 | 136 ms |
| Aug 15, 2026 | 130 ms |
| Aug 22, 2026 | 122 ms |
| Aug 29, 2026 | 120 ms |
| Sep 5, 2026 | 121 ms |
| Sep 12, 2026 | 127 ms |
| Sep 19, 2026 | 135 ms |
| Sep 26, 2026 | 137 ms |
| Oct 3, 2026 | 137 ms |
| Oct 10, 2026 | 130 ms |
| Oct 17, 2026 | 121 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
Speed
Render-blocking requests
1.8 s7 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.8 s.
Main-thread work: 4.7 s
A phone's processor spends 4.7 s on main-thread work while loading, 2.9 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 CDN, Google Tag Manager and Stripe and others), adding 2.8 MB and 2.4 s of main-thread time.
Reduce unused JavaScript
1.7 MBAbout 1.7 MB of JavaScript is downloaded but never used on this page.
Use efficient cache lifetimes
1.6 MB34 files are served with short cache lifetimes, so returning visitors download them again (1.6 MB).
Improve image delivery
1.0 MB6 images could be 1.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Mobile performance score: 63
63/100Your mobile performance score is 63 (desktop: 56). Pages that score under 90 lose visitors before the first paint.
Google CDN adds 799 ms
799 msGoogle CDN costs a phone 799 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.
Font display
800 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 800 ms).
Google Tag Manager adds 641 ms
641 msGoogle Tag Manager costs a phone 641 ms of main-thread work and 856 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.
Facebook adds 277 ms
277 msFacebook costs a phone 277 ms of main-thread work and 303 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.
Stripe adds 280 ms
280 msStripe costs a phone 280 ms of main-thread work and 274 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 191 ms. During a long task the page ignores taps.
Reduce unused CSS
110 ms · 64 KiBAbout 64 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 110 ms faster on a phone.
Legacy JavaScript
26 KiBPolyfills for old browsers add 26 KiB JavaScript that modern phones do not need.
Document request latency
22 KiBThe HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.
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 CSS
3 KiB3 KiB could be saved by minifying CSS.
1 checks passed
Server response: 27 ms
27 msYour server sent the HTML in 27 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 34.3 s
34.3 sThe page becomes fully interactive after 34.3 s. Good is under 3.8 s.
Speed Index: 10.2 s
10.2 sVisually, the page fills in at 10.2 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 1.2 s
1.2 sScripts block taps and scrolling for 1.2 s in total while the page loads. Good is under 200 ms.
First Contentful Paint: 2.1 s
2.1 sThe first text or image appears after 2.1 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.
Largest content (LCP) held steady for real visitors
-6%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
9 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.8 s
1.8 sReal visitors wait 1.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 121 ms
121 msReal visitors wait 121 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 527 ms
527 msReal visitors wait 527 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 17% faster for real visitors
-17%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 147 ms to 121 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest Contentful Paint: 2.3 s
2.3 sYour largest element renders in 2.3 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Building Australia's Future”.
Cumulative Layout Shift: 0.006
0.006The layout barely moves while loading (CLS 0.006, good is under 0.1).
Images and page weight
Page weight: 6.3 MB in 111 requests
6.3 MBYour homepage downloads 6.3 MB in 111 requests on a phone: scripts 3.5 MB (43), images 1.4 MB (16) and other files 727 KiB (30). Under 2 MB keeps phones on slow connections fast.
1 image below the first screen load straight away
1 image further down the page (20 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 1.8 g of CO₂ per visit
1.79 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.79 g of CO₂e: 214.4 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
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (13 elements)
All page content should be contained by landmarks: 13 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.
6 form fields without a label
6 form fields have no label, so screen readers announce an empty box and autofill guesses.
3 links without text
3 visible links have no text or label, so screen readers cannot say where they go.
1 checks passed
31 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 35 WCAG 2.2 A/AA and best-practice rules on the phone render: 31 passed and 4 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
2 H1 headlines
There are 2 <h1> headlines (“Building Australia's Future” and “Building Australia's Future”). One clear main headline is easier for people and search engines.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
No XML sitemap
No XML sitemap at https://alp.org.au/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at alp.org.au/robots.txt, the first file search crawlers ask for.
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.
62 internal links, 6 external
The homepage links to 62 pages on alp.org.au and 6 external pages.
3 checks passed
Meta description: 77 characters
Your meta description is 77 characters: “Find out about Anthony Albanese and Labor's plan to build Australia's Future.”.
Title: 52 characters
Your title is a healthy 52 characters: “Australian Labor Party – Building Australia's Future”.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
AI search readiness
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://alp.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.
Other pages
3 linked pages are broken
Your homepage links to https://alp.org.au/our-plan, https://alp.org.au/our-people and https://alp.org.au/get-involved, which answer with an error. Visitors hit a dead end and search engines drop them.
4 pages share a title
https://alp.org.au/our-people/our-people, https://alp.org.au/our-people/members-of-parliament, https://alp.org.au/our-people/ministry and https://alp.org.au/our-people/senators all use the title “Our People”. Search engines can't tell which page to show for a search, so each competes with the others.
5 pages without a meta description
https://alp.org.au/our-plan/what-were-working-on, https://alp.org.au/our-plan/albanese-labor-government-achievements, https://alp.org.au/our-people/organisation, https://alp.org.au/media and https://alp.org.au/get-involved/work-with-us have no meta description, so Google writes the search snippet from whatever text it finds.
4 pages share a meta description
https://alp.org.au/our-people/our-people, https://alp.org.au/our-people/members-of-parliament, https://alp.org.au/our-people/ministry and https://alp.org.au/our-people/senators use the same meta description. A description written for each page earns more clicks.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 31 found) and read each the way a search engine does.
4 checks passed
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 12 pages that loaded have a <title>.
Best practices
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
7 of 7 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 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 62 words
The homepage has only about 62 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.
2 checks passed
5 calls to action
The homepage has 5 calls to action, for example “Join Labor”, “Join us on Substack” and “Shop”.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Meta Pixel 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.
16 cookies set on arrival
16Opening the homepage sets 16 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.
38 other companies contacted
Loading the homepage contacts 38 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 alp.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
- jQuery
- Analytics
- Google Analytics | Google Tag Manager
Company
- Founded
- 1901
- Headquarters
- Barton
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 alp.org.au, including 17 speed issues, 6 SEO issues and 4 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.