Website review, no card needed
watertiger.com.au website review
Visit site (opens in a new tab)Reviewed 10 November 202625 issues · 81 checks
This review found 25 issues worth fixing on watertiger.com.au, 4 of them high impact, across 81 checks. The most urgent: 19 text elements with low contrast. 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
86B- #12,254 of 125,829 reviewed websitesbeats 87%
- #7,333 of 70,272 online storesbeats 85%
- #7,101 of 63,832 Shopify storesbeats 84%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 719 ms |
| May 30, 2026 | 600 ms |
| Jun 6, 2026 | 602 ms |
| Jun 13, 2026 | 581 ms |
| Jun 20, 2026 | 598 ms |
| Jun 27, 2026 | 725 ms |
| Jul 4, 2026 | 688 ms |
| Jul 11, 2026 | 844 ms |
| Jul 18, 2026 | 835 ms |
| Jul 25, 2026 | 757 ms |
| Aug 1, 2026 | 728 ms |
| Aug 8, 2026 | 722 ms |
| Aug 15, 2026 | 706 ms |
| Aug 22, 2026 | 709 ms |
| Aug 29, 2026 | 828 ms |
| Sep 5, 2026 | 879 ms |
| Sep 12, 2026 | 1.0 s |
| Sep 19, 2026 | 1.1 s |
| Sep 26, 2026 | 1.2 s |
| Oct 3, 2026 | 1.2 s |
| Oct 10, 2026 | 1.1 s |
| Oct 17, 2026 | 1.1 s |
| Oct 24, 2026 | 1.0 s |
| Oct 31, 2026 | 969 ms |
| Nov 7, 2026 | 927 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 79 ms |
| May 30, 2026 | 76 ms |
| Jun 6, 2026 | 78 ms |
| Jun 13, 2026 | 70 ms |
| Jun 20, 2026 | 70 ms |
| Jun 27, 2026 | 77 ms |
| Jul 4, 2026 | 74 ms |
| Jul 11, 2026 | 79 ms |
| Jul 25, 2026 | 71 ms |
| Aug 1, 2026 | 72 ms |
| Aug 8, 2026 | 78 ms |
| Aug 15, 2026 | 79 ms |
| Aug 22, 2026 | 83 ms |
| Aug 29, 2026 | 88 ms |
| Sep 5, 2026 | 94 ms |
| Sep 12, 2026 | 103 ms |
| Sep 19, 2026 | 106 ms |
| Sep 26, 2026 | 105 ms |
| Oct 3, 2026 | 105 ms |
| Oct 10, 2026 | 105 ms |
| Oct 17, 2026 | 105 ms |
| Oct 24, 2026 | 106 ms |
| Oct 31, 2026 | 108 ms |
| Nov 7, 2026 | 103 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.6 s
2.4 s
3.3 s
4.1 s
4.9 s
5.7 s
6.5 s
Speed
Mobile performance score: 73
73/100Your mobile performance score is 73. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
850 ms4 files block the first paint until they finish downloading. Deferring or inlining them could save about 850 ms.
Improve image delivery
150 ms · 415 KiB7 images could be 415 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
1,854 HTML elements
The page has 1,854 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Shopify adds 67 ms
67 msShopify costs a phone 67 ms of main-thread work and 443 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 JavaScript
150 ms · 99 KiBAbout 99 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
Reduce unused CSS
150 ms · 54 KiBAbout 54 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.
5 third-party services on the page
5 third-party services load with your homepage (Shopify, Hexton and nfcube.com and others), adding 566 KiB and 102 ms of main-thread time.
1 long task on the main thread
1 long task block the main thread while loading, the longest for 51 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
31 KiB5 files are served with short cache lifetimes, so returning visitors download them again (31 KiB).
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.
2 checks passed
Main-thread work: 2.0 s
A phone's processor spends 2.0 s on main-thread work while loading, 596 ms of it running JavaScript. That is comfortably low.
Server response: 8 ms
8 msYour server sent the HTML in 8 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 10.8 s
10.8 sYour largest element takes 10.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Water Tiger Furniture Vintage Indian Timber Carved Mirror”.
Time to Interactive: 11.1 s
11.1 sThe page becomes fully interactive after 11.1 s. Good is under 3.8 s.
Tap response (INP) got 36% slower for real visitors
+36%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 79 ms to 103 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 44% slower for real visitors
+44%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 0.7 s to 0.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Speed Index: 4.2 s
4.2 sVisually, the page fills in at 4.2 s (Speed Index). Good is under 3.4 s.
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: 0.9 s
0.9 sReal visitors wait 0.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 103 ms
103 msReal visitors wait 103 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: 0.8 s
0.8 sReal visitors see the first content after 0.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 446 ms
446 msReal visitors wait 446 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.001
0.001The layout barely moves while loading (CLS 0.001, good is under 0.1).
First Contentful Paint: 1.1 s
1.1 sThe first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.
Total Blocking Time: 1 ms
1 msScripts block the page for only 1 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 3.5 MB in 277 requests
3.5 MBYour homepage downloads 3.5 MB in 277 requests on a phone: images 1.7 MB (23), other files 1.1 MB (156) and scripts 499 KiB (70). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
IMG_07772.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
1 image in older formats
1 image (118 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 1.0 g of CO₂ per visit
1.00 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.00 g of CO₂e: 119.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
19 text elements with low contrast
19 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Hidden but focusable
9 elements hidden from screen readers can still receive keyboard focus.
All page content should be contained by landmarks (6 elements)
All page content should be contained by landmarks: 6 elements on the page fail this check, rated moderate by axe-core.
8 links without text
8 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
2 checks passed
Every image has alt text
All 40 images in the HTML carry an alt attribute.
50 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 3 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (68 characters)
Your title is 68 characters, so Google will cut it off around 60: “Watertiger | Vintage Furniture, Home Decor & Treasures – Water Tiger”.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Meta description is long (229 characters)
Your meta description is 229 characters; Google truncates after about 160, so the end of your pitch is cut.
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.
119 internal links, 14 external
The homepage links to 119 pages on watertiger.com.au and 14 external pages.
5 checks passed
One H1 headline
Your main headline reads: “Water Tiger”.
Canonical URL set
The canonical URL is https://watertiger.com.au/.
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://watertiger.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.
Some text only appears after JavaScript runs
44%The HTML your server sends has 633 of the 1,445 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.
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.
llms.txt published
The site publishes https://watertiger.com.au/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 44 found) and read each the way a search engine does.
7 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.
Every page has an H1
Each page we checked has a main headline.
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
19 of 21 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.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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,445 words of copy
The homepage carries about 1,445 words of visible text.
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP NOW” and “CONTACT US”.
26 calls to action
The homepage has 26 calls to action, for example “SHOP”, “SHOP BY COUNTRY” and “SHOP ALL”.
4 short forms
4 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 1 testimonial or review block and a star rating.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Pinterest Tag 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.
15 cookies set on arrival
15Opening the homepage sets 15 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 watertiger.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 3 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Instafeed · Judge Me Reviews · hextom.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 25 issues on watertiger.com.au, including 10 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.