Website review, no card needed
airbagman.com.au website review
Visit site (opens in a new tab)Reviewed 20 October 202636 issues · 82 checks
This review found 36 issues worth fixing on airbagman.com.au, 12 of them high impact, across 82 checks. The most urgent: page weight: 56.6 MB in 328 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
73C- #93,171 of 126,357 reviewed websitesbeats 23%
- #57,575 of 70,445 online storesbeats 15%
- #53,782 of 63,948 Shopify storesbeats 13%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 1.6 s |
| May 9, 2026 | 1.6 s |
| May 16, 2026 | 1.6 s |
| May 23, 2026 | 1.6 s |
| May 30, 2026 | 1.5 s |
| Jun 6, 2026 | 1.5 s |
| Jun 13, 2026 | 1.6 s |
| Jun 20, 2026 | 1.6 s |
| Jun 27, 2026 | 1.6 s |
| Jul 4, 2026 | 1.6 s |
| Jul 11, 2026 | 1.6 s |
| Jul 18, 2026 | 1.5 s |
| Jul 25, 2026 | 1.5 s |
| Aug 1, 2026 | 1.5 s |
| Aug 8, 2026 | 1.4 s |
| Aug 15, 2026 | 1.4 s |
| Aug 22, 2026 | 1.4 s |
| Aug 29, 2026 | 1.4 s |
| Sep 5, 2026 | 1.5 s |
| Sep 12, 2026 | 1.5 s |
| Sep 19, 2026 | 1.6 s |
| Sep 26, 2026 | 1.6 s |
| Oct 3, 2026 | 1.6 s |
| Oct 10, 2026 | 1.6 s |
| Oct 17, 2026 | 1.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 95 ms |
| May 9, 2026 | 95 ms |
| May 16, 2026 | 95 ms |
| May 23, 2026 | 96 ms |
| May 30, 2026 | 96 ms |
| Jun 6, 2026 | 97 ms |
| Jun 13, 2026 | 98 ms |
| Jun 20, 2026 | 98 ms |
| Jun 27, 2026 | 99 ms |
| Jul 4, 2026 | 97 ms |
| Jul 11, 2026 | 96 ms |
| Jul 18, 2026 | 96 ms |
| Jul 25, 2026 | 96 ms |
| Aug 1, 2026 | 96 ms |
| Aug 8, 2026 | 98 ms |
| Aug 15, 2026 | 99 ms |
| Aug 22, 2026 | 102 ms |
| Aug 29, 2026 | 99 ms |
| Sep 5, 2026 | 97 ms |
| Sep 12, 2026 | 97 ms |
| Sep 19, 2026 | 97 ms |
| Sep 26, 2026 | 98 ms |
| Oct 3, 2026 | 99 ms |
| Oct 10, 2026 | 97 ms |
| Oct 17, 2026 | 96 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.0 s
1.9 s
2.9 s
3.9 s
4.9 s
5.8 s
6.8 s
7.8 s
Speed
Render-blocking requests
1.2 s7 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.2 s.
Mobile performance score: 27
27/100Your mobile performance score is 27. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 5.7 s
A phone's processor spends 5.7 s on main-thread work while loading, 1.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Use efficient cache lifetimes
1.7 MB62 files are served with short cache lifetimes, so returning visitors download them again (1.7 MB).
Improve image delivery
900 ms · 696 KiB31 images could be 696 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 900 ms faster on a phone.
18 long tasks on the main thread
18 long tasks block the main thread while loading, the longest for 1.4 s. During a long task the page ignores taps.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, JSDelivr CDN and Other Google APIs/SDKs and others), adding 777 KiB and 1.1 s of main-thread time.
Reduce unused JavaScript
600 ms · 281 KiBAbout 281 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.
Google Tag Manager adds 591 ms
591 msGoogle Tag Manager costs a phone 591 ms of main-thread work and 316 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.
Reduce unused CSS
150 ms · 18 KiBAbout 18 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.
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.
1 checks passed
Server response: 4 ms
4 msYour server sent the HTML in 4 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.
Largest Contentful Paint: 140.3 s
140.3 sYour largest element takes 140.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Time to Interactive: 155.3 s
155.3 sThe page becomes fully interactive after 155.3 s. Good is under 3.8 s.
Total Blocking Time: 1.5 s
1.5 sScripts block taps and scrolling for 1.5 s in total while the page loads. Good is under 200 ms.
Speed Index: 6.2 s
6.2 sVisually, the page fills in at 6.2 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 2.7 s
2.7 sReal visitors wait 2.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
First Contentful Paint: 2.9 s
2.9 sThe first text or image appears after 2.9 s on a phone. Good is under 1.8 s.
Cumulative Layout Shift: 0.227
0.227The layout shifts by 0.227 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Tap response (INP) held steady for real visitors
+2%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 95 ms to 96 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
0%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.6 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user INP: 112 ms
112 msReal visitors wait 112 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.2 s
1.2 sReal visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 596 ms
596 msReal visitors wait 596 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
Page weight: 56.6 MB in 328 requests
56.6 MBYour homepage downloads 56.6 MB in 328 requests on a phone: images 54.6 MB (98), scripts 939 KiB (71) and other files 874 KiB (127). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
140 KiB1 image is downloaded at several times the size a phone draws it, for example header-logo.png at 4,163 px wide, shown at 89 px. Resized copies would save about 140 KiB.
1 image in older formats
1 image (140 KiB) is 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 16.0 g of CO₂ per visit
16.04 gBy the Sustainable Web Design model, a visit to your homepage emits about 16.04 g of CO₂e: 1924.8 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
38 text elements with low contrast
38 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
27 tap targets too small
27 tap targets are too small or too close together to hit reliably with a finger.
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.
9 links without text
9 visible links have no text or label, so screen readers cannot say where they go.
4 form fields without a label
4 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h2 → h5, h2 → h5 and h2 → h5), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 10 images in the HTML carry an alt attribute.
42 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 5 failed. 1 more 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.
Meta description is long (271 characters)
Your meta description is 271 characters; Google truncates after about 160, so the end of your pitch is cut.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
3 links with vague text
3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
134 internal links, 10 external
The homepage links to 134 pages on airbagman.com.au and 10 external pages.
5 checks passed
Title: 34 characters
Your title is a healthy 34 characters: “Airbag Man – Airbag Man Suspension”.
Canonical URL set
The canonical URL is https://airbagman.com.au/.
Structured data in place
Structured data found: Organization and WebSite.
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://airbagman.com.au/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing logo, description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
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.
Text is in the HTML
Your server sends the page's text in the HTML (805 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://airbagman.com.au/llms.txt (5 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
3 pages share a title
https://airbagman.com.au/pages/air-control-kit-search, https://airbagman.com.au/pages/on-board-air-control and https://airbagman.com.au/pages/air-tanks all use the title “Air Control – Airbag Man Suspension”. 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://airbagman.com.au/pages/air-control-kit-search, https://airbagman.com.au/collections/all, https://airbagman.com.au/pages/on-board-air-control, https://airbagman.com.au/pages/air-tanks and https://airbagman.com.au/pages/industries have no meta description, so Google writes the search snippet from whatever text it finds.
4 links to non-canonical URLs
Your homepage links to 4 pages by a URL that isn't their canonical one, for example https://airbagman.com.au/pages/air-control-kit-search, whose canonical is https://airbagman.com.au/pages/air-control. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
12 pages without an H1
https://airbagman.com.au/pages/air-control-kit-search, https://airbagman.com.au/pages/on-board-air-control, https://airbagman.com.au/pages/air-tanks, https://airbagman.com.au/pages/industries, https://airbagman.com.au/pages/industry/recreational-commercial and https://airbagman.com.au/pages/industry/oem-replacements and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 35 found) and read each the way a search engine does.
3 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
39 of 39 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
Thin social proof
Social proof on the homepage: 3 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
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.
About 785 words of copy
The homepage carries about 785 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: “Learn more” and “Order now”.
10 calls to action
The homepage has 10 calls to action, for example “0 Request a Quote (0)”, “Contact” and “Request a Quote”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Phone number on the homepage
Your phone number is on the homepage.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and The Trade Desk (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.
14 cookies set on arrival
14Opening the homepage sets 14 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.
29 other companies contacted
Loading the homepage contacts 29 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 airbagman.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
- E-commerce
- Shopify
- 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 airbagman.com.au, including 17 speed issues, 4 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.