Website review, no card needed
thegrayl.com.au website review
Visit site (opens in a new tab)Reviewed 9 November 202637 issues · 87 checks
This review found 37 issues worth fixing on thegrayl.com.au, 13 of them high impact, across 87 checks. The most urgent: page weight: 13.2 MB in 302 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
82B- #29,450 of 103,826 reviewed websitesbeats 66%
- #19,358 of 57,943 online storesbeats 60%
- #18,709 of 52,750 Shopify storesbeats 58%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 1.6 s |
| May 30, 2026 | 1.4 s |
| Jun 6, 2026 | 1.2 s |
| Jun 13, 2026 | 1.2 s |
| Jun 20, 2026 | 1.3 s |
| Jun 27, 2026 | 1.3 s |
| Jul 4, 2026 | 1.4 s |
| Jul 11, 2026 | 1.4 s |
| Jul 18, 2026 | 1.4 s |
| Jul 25, 2026 | 1.4 s |
| Aug 1, 2026 | 1.4 s |
| Aug 8, 2026 | 1.3 s |
| Aug 15, 2026 | 1.4 s |
| Aug 29, 2026 | 1.5 s |
| Sep 5, 2026 | 1.5 s |
| Sep 12, 2026 | 1.5 s |
| Sep 19, 2026 | 1.5 s |
| Sep 26, 2026 | 1.4 s |
| Oct 10, 2026 | 1.6 s |
| Oct 17, 2026 | 1.6 s |
| Oct 24, 2026 | 1.7 s |
| Oct 31, 2026 | 1.6 s |
| Nov 7, 2026 | 1.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 96 ms |
| Jun 6, 2026 | 95 ms |
| Jun 13, 2026 | 91 ms |
| Jun 20, 2026 | 96 ms |
| Jun 27, 2026 | 99 ms |
| Jul 4, 2026 | 103 ms |
| Jul 11, 2026 | 102 ms |
| Jul 18, 2026 | 96 ms |
| Jul 25, 2026 | 93 ms |
| Aug 1, 2026 | 96 ms |
| Aug 8, 2026 | 96 ms |
| Aug 15, 2026 | 99 ms |
| Sep 19, 2026 | 97 ms |
| Oct 24, 2026 | 112 ms |
| Oct 31, 2026 | 104 ms |
| Nov 7, 2026 | 104 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.7 s
1.5 s
2.2 s
2.9 s
3.6 s
4.4 s
5.1 s
5.8 s
Speed
Reduce unused JavaScript
850 ms · 958 KiBAbout 958 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 850 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (groovehq.com, Yotpo and Shopify and others), adding 11.4 MB and 348 ms of main-thread time.
Shopify adds 56 ms
56 msShopify costs a phone 56 ms of main-thread work and 10.2 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.
Mobile performance score: 71
71/100Your mobile performance score is 71. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
900 ms5 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.
Use efficient cache lifetimes
700 ms · 163 KiB21 files are served with short cache lifetimes, so returning visitors download them again (163 KiB).
Improve image delivery
450 ms · 353 KiB9 images could be 353 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.
groovehq.com adds 202 ms
202 msgroovehq.com costs a phone 202 ms of main-thread work and 942 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.
Main-thread work: 2.8 s
A phone's processor spends 2.8 s on main-thread work while loading, 776 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Reduce unused CSS
250 ms · 58 KiBAbout 58 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 250 ms faster on a phone.
1 long task on the main thread
1 long task block the main thread while loading, the longest for 85 ms. During a long task the page ignores taps.
Minify JavaScript
19 KiB19 KiB could be saved by minifying JavaScript.
Legacy JavaScript
17 KiBPolyfills for old browsers add 17 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.
1 checks passed
Server response: 5 ms
5 msYour server sent the HTML in 5 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 7.1 s
7.1 sYour largest element takes 7.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “World’s Fastest Portable Water Purifier - Travel, Adventure…”.
Time to Interactive: 9.6 s
9.6 sThe page becomes fully interactive after 9.6 s. Good is under 3.8 s.
Speed Index: 6.0 s
6.0 sVisually, the page fills in at 6.0 s (Speed Index). Good is under 3.4 s.
21 images without width and height
21 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+9%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 96 ms to 104 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+7%Over the last 25 four-week periods to 2026-11-07, 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).
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: 104 ms
104 msReal visitors wait 104 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.02
0.02For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.
Real-user FCP: 1.0 s
1.0 sReal visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 414 ms
414 msReal visitors wait 414 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.014
0.014The layout barely moves while loading (CLS 0.014, good is under 0.1).
First Contentful Paint: 0.9 s
0.9 sThe first text or image appears after 0.9 s, inside the 1.8 s “good” threshold.
Total Blocking Time: 18 ms
18 msScripts block the page for only 18 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 13.2 MB in 302 requests
13.2 MBYour homepage downloads 13.2 MB in 302 requests on a phone: media 10.0 MB (1), scripts 1.2 MB (94) and other files 1.1 MB (134). Under 2 MB keeps phones on slow connections fast.
2 images far larger than shown
123 KiB2 images are downloaded at several times the size a phone draws them, for example 500-COV_COVERT_BLACK_ULTRAPRESS_ALEX_WANDER__PRIMITIVEWANDER at 1,400 px wide, shown at 390 px. Resized copies would save about 123 KiB.
2 images in older formats
2 images (269 KiB) 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.
1 image below the first screen load straight away
1 image further down the page (30 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 3.7 g of CO₂ per visit
3.75 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.75 g of CO₂e: 449.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Invalid ARIA attributes
1 element use ARIA attributes their role does not allow, which confuses screen readers.
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.
ARIA attributes must conform to valid values (1 element)
ARIA attributes must conform to valid values: 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”.
Hidden but focusable
2 elements hidden from screen readers can still receive keyboard focus.
ARIA input fields must have an accessible name (2 elements)
ARIA input fields must have an accessible name: 2 elements on the page fail this check, rated serious by axe-core.
2 text elements with low contrast
2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Interactive controls must not be nested (2 elements)
Interactive controls must not be nested: 2 elements on the page fail this check, rated serious by axe-core.
34 links without text
34 visible links have no text or label, so screen readers cannot say where they go.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
Elements marked as presentational should be consistently ignored (1 element)
Elements marked as presentational should be consistently ignored: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 27 images in the HTML carry an alt attribute.
49 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 60 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 11 failed. 6 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.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
5 links crawlers can't follow
5 links have no real href, so search engines can't follow them.
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.
117 internal links, 15 external
The homepage links to 117 pages on thegrayl.com.au and 15 external pages.
6 checks passed
Meta description: 155 characters
Your meta description is 155 characters: “Welcome to GRAYL® Australia, home of the world's fastest portable purifier. With advanced filtration,, allowing anyone …”.
One H1 headline
Your main headline reads: “GRAYL® Australia”.
Title: 58 characters
Your title is a healthy 58 characters: “GRAYL® Australia Official Store | Purify Water. Anywhere.™”.
Canonical URL set
The canonical URL is https://thegrayl.com.au/.
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://thegrayl.com.au/sitemap.xml.
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.
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 (375 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://thegrayl.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://thegrayl.com.au/collections/camp-drinkware, https://thegrayl.com.au/collections/replacement-parts and https://thegrayl.com.au/collections/carry-project have no meta description, so Google writes the search snippet from whatever text it finds.
8 pages without an H1
https://thegrayl.com.au/pages/our-story, https://thegrayl.com.au/pages/a-closer-look, https://thegrayl.com.au/pages/giving-back, https://thegrayl.com.au/pages/ambassadors, https://thegrayl.com.au/pages/guides-manuals and https://thegrayl.com.au/pages/geopress-quickstart-guide and 2 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 43 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: net::ERR_FAILED”.
2 checks passed
Tap targets are thumb-sized
50 of 60 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
About 254 words of copy
The homepage carries about 254 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 NOW”.
6 calls to action
The homepage has 6 calls to action, for example “Shop”, “SHOP NOW” and “LEARN MORE”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: PostHog.
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
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (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.
13 cookies set on arrival
13Opening the homepage sets 13 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.
19 other companies contacted
Loading the homepage contacts 19 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 thegrayl.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 5 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Avada Seo Suite · Selleasy · In Cart Upsell · Mailchimp · chimpstatic.com
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
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 37 issues on thegrayl.com.au, including 13 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.