Website review, no card needed
thirstycamel.com.au website review
Visit site (opens in a new tab)Reviewed 19 October 202651 issues · 91 checks
This review found 51 issues worth fixing on thirstycamel.com.au, 26 of them high impact, across 91 checks. The most urgent: use efficient cache lifetimes. 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
63DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 25, 2026 | 3.3 s |
| May 2, 2026 | 3.4 s |
| May 9, 2026 | 3.4 s |
| May 16, 2026 | 3.5 s |
| May 23, 2026 | 3.5 s |
| May 30, 2026 | 3.6 s |
| Jun 6, 2026 | 3.6 s |
| Jun 13, 2026 | 3.6 s |
| Jun 20, 2026 | 3.6 s |
| Jun 27, 2026 | 3.6 s |
| Jul 4, 2026 | 3.7 s |
| Jul 11, 2026 | 3.7 s |
| Jul 18, 2026 | 3.7 s |
| Jul 25, 2026 | 3.5 s |
| Aug 1, 2026 | 3.5 s |
| Aug 8, 2026 | 3.5 s |
| Aug 15, 2026 | 3.4 s |
| Aug 22, 2026 | 3.4 s |
| Aug 29, 2026 | 3.5 s |
| Sep 5, 2026 | 3.5 s |
| Sep 12, 2026 | 3.8 s |
| Sep 19, 2026 | 3.9 s |
| Sep 26, 2026 | 4.0 s |
| Oct 3, 2026 | 4.1 s |
| Oct 10, 2026 | 4.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 25, 2026 | 211 ms |
| May 2, 2026 | 211 ms |
| May 9, 2026 | 210 ms |
| May 16, 2026 | 213 ms |
| May 23, 2026 | 212 ms |
| May 30, 2026 | 211 ms |
| Jun 6, 2026 | 213 ms |
| Jun 13, 2026 | 213 ms |
| Jun 20, 2026 | 218 ms |
| Jun 27, 2026 | 222 ms |
| Jul 4, 2026 | 222 ms |
| Jul 11, 2026 | 220 ms |
| Jul 18, 2026 | 218 ms |
| Jul 25, 2026 | 212 ms |
| Aug 1, 2026 | 211 ms |
| Aug 8, 2026 | 214 ms |
| Aug 15, 2026 | 214 ms |
| Aug 22, 2026 | 217 ms |
| Aug 29, 2026 | 216 ms |
| Sep 5, 2026 | 213 ms |
| Sep 12, 2026 | 213 ms |
| Sep 19, 2026 | 214 ms |
| Sep 26, 2026 | 219 ms |
| Oct 3, 2026 | 221 ms |
| Oct 10, 2026 | 223 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
2.0 s
3.0 s
4.0 s
5.0 s
6.0 s
7.0 s
8.0 s
Speed
Use efficient cache lifetimes
2.8 s · 1.3 MB76 files are served with short cache lifetimes, so returning visitors download them again (1.3 MB).
Reduce unused JavaScript
3.3 s · 667 KiBAbout 667 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.3 s faster on a phone.
Render-blocking requests
2.5 s4 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.5 s.
Mobile performance score: 29
29/100Your mobile performance score is 29 (desktop: 44). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 6.7 s
A phone's processor spends 6.7 s on main-thread work while loading, 3.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3,223 HTML elements
The page has 3,223 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and Google Maps and others), adding 1.3 MB and 1.3 s of main-thread time.
Google Tag Manager adds 435 ms
435 msGoogle Tag Manager costs a phone 435 ms of main-thread work and 479 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 431 ms. During a long task the page ignores taps.
Facebook adds 402 ms
402 msFacebook costs a phone 402 ms of main-thread work and 223 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.
Improve image delivery
388 KiB10 images could be 388 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Font display
350 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 350 ms).
Google Maps adds 267 ms
267 msGoogle Maps costs a phone 267 ms of main-thread work and 383 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.
Legacy JavaScript
150 ms · 30 KiBPolyfills for old browsers add 30 KiB JavaScript that modern phones do not need. 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.
Duplicated JavaScript
4 KiB4 KiB JavaScript is shipped twice across bundles.
1 checks passed
Server response: 371 ms
371 msYour server sent the HTML in 371 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.
Real-user LCP: 5.2 s
5.2 sReal visitors wait 5.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 3.1 s
3.1 sReal visitors see the first content after 3.1 s (75th percentile). Good is under 1.8 s.
Largest Contentful Paint: 19.4 s
19.4 sYour largest element takes 19.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 19.6 s
19.6 sThe page becomes fully interactive after 19.6 s. Good is under 3.8 s.
Total Blocking Time: 2.6 s
2.6 sScripts block taps and scrolling for 2.6 s in total while the page loads. Good is under 200 ms.
Speed Index: 9.4 s
9.4 sVisually, the page fills in at 9.4 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 4.6 s
4.6 sThe first text or image appears after 4.6 s on a phone. Good is under 1.8 s.
Real-user INP: 274 ms
274 msReal visitors wait 274 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Largest content (LCP) got 21% slower for real visitors
+21%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' largest content (lcp) went from 3.3 s to 4.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user TTFB: 1.2 s
1.2 sReal visitors wait 1.2 s for your server to start answering (75th percentile). Good is under 800 ms.
9 images without width and height
9 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+5%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' tap response (inp) went from 211 ms to 223 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user CLS: 0.10
0.10For real visitors the layout shifts by 0.10 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 3.5 MB in 183 requests
3.5 MBYour homepage downloads 3.5 MB in 183 requests on a phone: scripts 1.9 MB (49), images 1.1 MB (70) and other files 286 KiB (54). Under 2 MB keeps phones on slow connections fast.
3 images far larger than shown
392 KiB3 images are downloaded at several times the size a phone draws them, for example 6806e07a-125b-44ea-25a6-115d17abeafa at 2,001 px wide, shown at 388 px. Resized copies would save about 392 KiB.
1 image in older formats
1 image (188 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.
1 image below the first screen load straight away
1 image further down the page (24 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 1.0 g of CO₂ per visit
0.99 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.99 g of CO₂e: 119.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Certain ARIA roles must be contained by particular parents (60 elements)
Certain ARIA roles must be contained by particular parents: 60 elements on the page fail this check, rated critical by axe-core.
Certain ARIA roles must contain particular children (5 elements)
Certain ARIA roles must contain particular children: 5 elements on the page fail this check, rated critical by axe-core.
3 buttons without a name
3 buttons have no accessible name, so screen readers announce just “button”.
Interactive controls must not be nested (60 elements)
Interactive controls must not be nested: 60 elements on the page fail this check, rated serious by axe-core.
14 text elements with low contrast
14 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
ARIA input fields must have an accessible name (5 elements)
ARIA input fields must have an accessible name: 5 elements on the page fail this check, rated serious by axe-core.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
Positive tabindex
3 elements have a tabindex above 0, which scrambles the keyboard order.
<html> element must have a lang attribute (1 element)
<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
112 links without text
112 visible links have no text or label, so screen readers cannot say where they go.
All page content should be contained by landmarks (17 elements)
All page content should be contained by landmarks: 17 elements on the page fail this check, rated moderate by axe-core.
3 form fields without a label
3 form fields have no label, so screen readers announce an empty box and autofill guesses.
No page language
The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
1 checks passed
38 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 38 passed and 13 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (67 characters)
Your title is 67 characters, so Google will cut it off around 60: “Thirsty Camel - Local Bottle Shop in Australia | Buy Alcohol Online”.
6 H1 headlines
There are 6 <h1> headlines (“Beer”, “Join Hump Club” and “Premix”). One clear main headline is easier for people and search engines.
49 internal links, 0 external
The homepage links to 49 pages on thirstycamel.com.au and 0 external pages.
6 checks passed
Meta description: 127 characters
Your meta description is 127 characters: “Thirsty Camel bottle shop offers the best prices for beer, wine & spirits. Join the Hump Club for member-only weekly di…”.
Canonical URL set
The canonical URL is https://www.thirstycamel.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://www.thirstycamel.com.au/sitemap.xml.
AI search readiness
Some text only appears after JavaScript runs
55%The HTML your server sends has 764 of the 1,380 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.
No llms.txt
There is no https://www.thirstycamel.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.
2 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: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.
Other pages
15 pages share a meta description
https://www.thirstycamel.com.au/specials, https://www.thirstycamel.com.au/hump-club, https://www.thirstycamel.com.au/everyday-value, https://www.thirstycamel.com.au/TOP-DROPS, https://www.thirstycamel.com.au/JD-Billsons and https://www.thirstycamel.com.au/bundles and 9 others use the same meta description. A description written for each page earns more clicks.
2 pages without an H1
https://www.thirstycamel.com.au/hump-club and https://www.thirstycamel.com.au/humpdaydeals 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 25 found) and read each the way a search engine does.
6 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
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
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Manifest: Line: 1, column: 1, Syntax error.”.
2 checks passed
Tap targets are thumb-sized
201 of 201 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.
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 1,380 words of copy
The homepage carries about 1,380 words of visible text.
3 checks passed
3 calls to action
The homepage has 3 calls to action, for example “Join For Free”, “Join for free” and “Contact Us”.
1 short form
A short form (2 fields at most) is right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Meta Pixel.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo 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.
9 cookies set on arrival
9Opening the homepage sets 9 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.
22 other companies contacted
Loading the homepage contacts 22 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 thirstycamel.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
- Next.js
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- Google Cloud
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 51 issues on thirstycamel.com.au, including 25 speed issues, 2 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.