Website review, no card needed
amcham.com.au website review
Visit site (opens in a new tab)Reviewed 24 October 202644 issues · 80 checks
This review found 44 issues worth fixing on amcham.com.au, 21 of them high impact, across 80 checks. The most urgent: improve image delivery. 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
61DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.7 s |
| May 9, 2026 | 2.7 s |
| May 16, 2026 | 2.4 s |
| May 23, 2026 | 2.7 s |
| May 30, 2026 | 2.8 s |
| Jun 6, 2026 | 2.9 s |
| Jun 13, 2026 | 3.0 s |
| Jun 20, 2026 | 3.2 s |
| Jun 27, 2026 | 3.4 s |
| Jul 4, 2026 | 3.0 s |
| Jul 11, 2026 | 3.0 s |
| Jul 18, 2026 | 3.0 s |
| Jul 25, 2026 | 2.6 s |
| Aug 1, 2026 | 2.8 s |
| Aug 8, 2026 | 2.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 70 ms |
| May 16, 2026 | 70 ms |
| May 23, 2026 | 72 ms |
| May 30, 2026 | 74 ms |
| Jun 6, 2026 | 72 ms |
| Jun 13, 2026 | 71 ms |
| Jun 20, 2026 | 71 ms |
| Jul 4, 2026 | 73 ms |
| Jul 11, 2026 | 75 ms |
| Jul 18, 2026 | 76 ms |
| Jul 25, 2026 | 74 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
1.9 s
3.9 s
5.8 s
7.7 s
9.6 s
11.6 s
13.5 s
15.4 s
Speed
Improve image delivery
10.8 s · 3.5 MB5 images could be 3.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 10.8 s faster on a phone.
Use efficient cache lifetimes
7.0 s · 2.5 MB68 files are served with short cache lifetimes, so returning visitors download them again (2.5 MB).
Render-blocking requests
8.9 s16 files block the first paint until they finish downloading. Deferring or inlining them could save about 8.9 s.
Reduce unused JavaScript
4.5 s · 1.9 MBAbout 1.9 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.5 s faster on a phone.
Font display
3.0 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 3.0 s).
Reduce unused CSS
1.1 s · 280 KiBAbout 280 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.
Mobile performance score: 16
16/100Your mobile performance score is 16 (desktop: 32). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
4,185 HTML elements
The page has 4,185 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
7 third-party services on the page
7 third-party services load with your homepage (sfox.au, Stripe and Google Maps and others), adding 2.8 MB and 1.4 s of main-thread time.
Document request latency
900 ms · 532 KiBThe HTML itself could arrive about 900 ms sooner: redirects, a slow server response or missing compression delay everything after it.
sfox.au adds 920 ms
920 mssfox.au costs a phone 920 ms of main-thread work and 2.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.
Reduce initial server response time
907 msReduce initial server response time. Google estimates savings of 907 ms on a phone.
Duplicated JavaScript
350 ms · 428 KiB428 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 350 ms faster on a phone.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 647 ms. During a long task the page ignores taps.
Main-thread work: 3.8 s
A phone's processor spends 3.8 s on main-thread work while loading, 1.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Google Maps adds 170 ms
170 msGoogle Maps costs a phone 170 ms of main-thread work and 392 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.
Server response: 1.0 s
1.0 sYour server takes 1.0 s to send the HTML. Google recommends under 600 ms; everything else waits for it.
Minify CSS
13 KiB13 KiB could be saved by minifying CSS.
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.
Minify JavaScript
3 KiB3 KiB could be saved by minifying JavaScript.
Core Web Vitals
First Contentful Paint: 13.4 s
13.4 sThe first text or image appears after 13.4 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 39.7 s
39.7 sYour largest element takes 39.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 20.0 s
20.0 sVisually, the page fills in at 20.0 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 45.4 s
45.4 sThe page becomes fully interactive after 45.4 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.372
0.372The layout shifts by 0.372 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Total Blocking Time: 955 ms
955 msScripts block taps and scrolling for 955 ms in total while the page loads. Good is under 200 ms.
43 images without width and height
43 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+7%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 70 ms to 74 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-1%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.7 s to 2.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
Images and page weight
Page weight: 10.4 MB in 118 requests
10.4 MBYour homepage downloads 10.4 MB in 118 requests on a phone: images 5.9 MB (72), scripts 2.6 MB (16) and HTML 798 KiB (3). Under 2 MB keeps phones on slow connections fast.
3 images over 500 KB
3 images weigh 4.7 MB together. On a phone connection a single image that size takes seconds.
2 images far larger than shown
1.3 MB2 images are downloaded at several times the size a phone draws them, for example img-mh-1.jpg at 2,048 px wide, shown at 390 px. Resized copies would save about 1.3 MB.
8 images in older formats
8 images (5.6 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.
12 images below the first screen load straight away
12 images further down the page (2.1 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 2.9 g of CO₂ per visit
2.94 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.94 g of CO₂e: 353.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
2 images without alt text
2 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (326 elements)
All page content should be contained by landmarks: 326 elements on the page fail this check, rated moderate by axe-core.
3 links without text
3 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h4 → h6, h3 → h5 and h3 → h6), which makes the page harder to scan with a screen reader.
1 checks passed
34 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 38 WCAG 2.2 A/AA and best-practice rules on the phone render: 34 passed and 4 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
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 XML sitemap
No XML sitemap at https://amcham.com.au/sitemap.xml, so Google discovers your pages only by following links.
Open Graph partly set
Open Graph is missing og:title and og:description, so shared links fall back to guesses.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
43 internal links, 6 external
The homepage links to 43 pages on amcham.com.au and 6 external pages.
3 checks passed
Title: 41 characters
Your title is a healthy 41 characters: “American Chamber of Commerce in Australia”.
Canonical URL set
The canonical URL is https://www.amcham.com.au/.
robots.txt in place
robots.txt is in place.
AI search readiness
Most text only appears after JavaScript runs
20%A phone browser shows 3,033 words, but the HTML your server sends has only 602. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.
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://amcham.com.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
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Other pages
15 pages without a meta description
https://amcham.com.au/membership/become-a-member, https://amcham.com.au/2026-membership, https://amcham.com.au/events-experiences/upcoming-events, https://amcham.com.au/membership, https://amcham.com.au/events-experiences and https://amcham.com.au/insight-advocacy/policy-advocacy-overview and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
15 pages without an H1
https://amcham.com.au/membership/become-a-member, https://amcham.com.au/2026-membership, https://amcham.com.au/events-experiences/upcoming-events, https://amcham.com.au/membership, https://amcham.com.au/events-experiences and https://amcham.com.au/insight-advocacy/policy-advocacy-overview and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.
2 pages with very little text
https://amcham.com.au/membership/become-a-member and https://amcham.com.au/2026-membership have 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.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 28 found) and read each the way a search engine does.
5 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.
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
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
2 checks passed
Tap targets are thumb-sized
255 of 257 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 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.
About 3,033 words of copy
The homepage carries about 3,033 words of visible text.
2 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Join Now” and “Why Join / Membership Outcome”.
7 calls to action
The homepage has 7 calls to action, for example “Join Now”, “Subscribe” and “Login for member pricing”.
Privacy and tracking
3 cookies set on arrival
3Opening the homepage sets 3 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.
12 other companies contacted
Loading the homepage contacts 12 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 amcham.com.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
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 44 issues on amcham.com.au, including 24 speed issues, 4 SEO issues and 3 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.