Website review, no card needed
goodriddance.com.au website review
Visit site (opens in a new tab)Reviewed 10 November 202629 issues · 81 checks
This review found 29 issues worth fixing on goodriddance.com.au, 9 of them high impact, across 81 checks. The most urgent: 5,706 HTML elements. 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
88B- #5,228 of 108,869 reviewed websitesbeats 93%
- #2,908 of 61,767 online storesbeats 93%
- #2,825 of 56,365 Shopify storesbeats 92%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 1.8 s |
| May 30, 2026 | 1.7 s |
| Jun 6, 2026 | 1.7 s |
| Jun 13, 2026 | 1.7 s |
| Jun 20, 2026 | 1.6 s |
| Jun 27, 2026 | 1.6 s |
| Jul 4, 2026 | 1.7 s |
| Jul 11, 2026 | 1.7 s |
| Jul 18, 2026 | 1.7 s |
| Jul 25, 2026 | 1.7 s |
| Aug 1, 2026 | 1.7 s |
| Aug 8, 2026 | 1.6 s |
| Aug 15, 2026 | 1.6 s |
| Aug 22, 2026 | 1.7 s |
| Aug 29, 2026 | 1.7 s |
| Sep 5, 2026 | 1.7 s |
| Sep 12, 2026 | 1.6 s |
| Sep 19, 2026 | 1.5 s |
| Sep 26, 2026 | 1.5 s |
| Oct 3, 2026 | 1.5 s |
| Oct 10, 2026 | 1.5 s |
| Oct 17, 2026 | 1.6 s |
| Oct 24, 2026 | 1.6 s |
| Oct 31, 2026 | 1.7 s |
| Nov 7, 2026 | 1.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 138 ms |
| May 30, 2026 | 137 ms |
| Jun 6, 2026 | 133 ms |
| Jun 13, 2026 | 133 ms |
| Jun 20, 2026 | 135 ms |
| Jun 27, 2026 | 138 ms |
| Jul 4, 2026 | 142 ms |
| Jul 11, 2026 | 142 ms |
| Jul 18, 2026 | 144 ms |
| Jul 25, 2026 | 135 ms |
| Aug 1, 2026 | 128 ms |
| Aug 8, 2026 | 128 ms |
| Aug 15, 2026 | 128 ms |
| Aug 22, 2026 | 129 ms |
| Aug 29, 2026 | 133 ms |
| Sep 5, 2026 | 130 ms |
| Sep 12, 2026 | 129 ms |
| Sep 19, 2026 | 127 ms |
| Sep 26, 2026 | 126 ms |
| Oct 3, 2026 | 126 ms |
| Oct 10, 2026 | 127 ms |
| Oct 17, 2026 | 129 ms |
| Oct 24, 2026 | 133 ms |
| Oct 31, 2026 | 136 ms |
| Nov 7, 2026 | 137 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.8 s
1.5 s
2.3 s
3.0 s
3.8 s
4.5 s
5.3 s
6.0 s
Speed
5,706 HTML elements
The page has 5,706 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
1.0 MB11 images could be 1.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Mobile performance score: 73
73/100Your mobile performance score is 73. Pages that score under 90 lose visitors before the first paint.
8 third-party services on the page
8 third-party services load with your homepage (alia-prod.com, Shopify and Clarity and others), adding 1.8 MB and 641 ms of main-thread time.
Render-blocking requests
750 ms15 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.
Reduce unused JavaScript
595 KiBAbout 595 KiB of JavaScript is downloaded but never used on this page.
Main-thread work: 4.0 s
A phone's processor spends 4.0 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
315 KiB15 files are served with short cache lifetimes, so returning visitors download them again (315 KiB).
alia-prod.com adds 231 ms
231 msalia-prod.com costs a phone 231 ms of main-thread work and 740 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.
Shopify adds 171 ms
171 msShopify costs a phone 171 ms of main-thread work and 650 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 · 21 KiBAbout 21 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.
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 98 ms. During a long task the page ignores taps.
Legacy JavaScript
35 KiBPolyfills for old browsers add 35 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.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 12 ms
12 msYour server sent the HTML in 12 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 14.9 s
14.9 sThe page becomes fully interactive after 14.9 s. Good is under 3.8 s.
Speed Index: 9.8 s
9.8 sVisually, the page fills in at 9.8 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 4.8 s
4.8 sYour largest element takes 4.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Tap response (INP) held steady for real visitors
-1%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 138 ms to 137 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-8%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.6 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.6 s
1.6 sReal visitors wait 1.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 129 ms
129 msReal visitors wait 129 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.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 436 ms
436 msReal visitors wait 436 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.2 s
1.2 sThe first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.
Total Blocking Time: 83 ms
83 msScripts block the page for only 83 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.012
0.012The layout barely moves while loading (CLS 0.012, good is under 0.1).
Images and page weight
Page weight: 3.9 MB in 319 requests
3.9 MBYour homepage downloads 3.9 MB in 319 requests on a phone: scripts 1.5 MB (108), images 1.3 MB (26) and other files 872 KiB (129). Under 2 MB keeps phones on slow connections fast.
About 1.1 g of CO₂ per visit
1.10 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.10 g of CO₂e: 132.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Certain ARIA roles must contain particular children (1 element)
Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
8 text elements with low contrast
8 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
4 tap targets too small
4 tap targets are too small or too close together to hit reliably with a finger.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (4 elements)
All page content should be contained by landmarks: 4 elements on the page fail this check, rated moderate by axe-core.
Heading levels should only increase by one (1 element)
Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.
2 checks passed
Every image has alt text
All 29 images in the HTML carry an alt attribute.
55 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 62 WCAG 2.2 A/AA and best-practice rules on the phone render: 55 passed and 7 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
2 H1 headlines
There are 2 <h1> headlines (“” and “Leading Aussies Back Outside”). One clear main headline is easier for people and search engines.
2 links with vague text
2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
77 internal links, 9 external
The homepage links to 77 pages on goodriddance.com.au and 9 external pages.
7 checks passed
Meta description: 136 characters
Your meta description is 136 characters: “Good Riddance is a clinically proven, natural insect and mosquito repellent guaranteed to protect against mozzies, midg…”.
Title: 58 characters
Your title is a healthy 58 characters: “Mosquito repellent and insect repellent from Good Riddance”.
Canonical URL set
The canonical URL is https://goodriddance.com.au/.
Structured data in place
Structured data found: Organization and WebSite.
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://goodriddance.com.au/sitemap.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 (2,040 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://goodriddance.com.au/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
3 pages without a meta description
https://goodriddance.com.au/policies/shipping-policy, https://goodriddance.com.au/blogs/uncategorized and https://goodriddance.com.au/pages/apply-for-a-wholesale-account have no meta description, so Google writes the search snippet from whatever text it finds.
14 pages without an H1
https://goodriddance.com.au/collections, https://goodriddance.com.au/policies/shipping-policy, https://goodriddance.com.au/products/good-riddance-tropical-insect-repellent-100ml, https://goodriddance.com.au/products/good-riddance-sensitive-insect-repellent-100ml, https://goodriddance.com.au/products/good-riddance-rescue-balm-10g and https://goodriddance.com.au/products/good-riddance-family-pack and 8 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 26 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
6 JavaScript errors while loading
6 errors were 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
23 of 23 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: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.
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.
About 1,075 words of copy
The homepage carries about 1,075 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: “Shop All”.
12 calls to action
The homepage has 12 calls to action, for example “Shop”, “Shop All” and “Contact Us”.
12 short forms
12 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Microsoft Clarity.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo 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.
19 cookies set on arrival
19Opening the homepage sets 19 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.
50 other companies contacted
Loading the homepage contacts 50 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 goodriddance.com.au, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
Your storefront loads 12 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Triplewhale · Microsoft Clarity · Gorgias Live Chat Helpdesk · Klaviyo Email Marketing Sms · Okendo · Section Factory · Countdown Timer · Forms · Freegifts · Upcart · cloudfront.net · bogos.io
Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info
Upkeep, stack and company
Stack
- E-commerce
- Shopify
- Analytics
- Microsoft Clarity
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 29 issues on goodriddance.com.au, including 13 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.