Website review, no card needed
wagwear.com.au website review
Visit site (opens in a new tab)Reviewed 8 November 202636 issues · 86 checks
This review found 36 issues worth fixing on wagwear.com.au, 8 of them high impact, across 86 checks. The most urgent: avoid multiple page redirects. 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
80B- #49,134 of 126,508 reviewed websitesbeats 55%
- #32,199 of 70,497 online storesbeats 48%
- #30,913 of 63,990 Shopify storesbeats 45%
Closest competitors among Shopify stores
Compare side by sideOne score from every part of this review. How it works
Speed
Avoid multiple page redirects
7.7 sThe page goes through 2 redirects before it starts loading, costing about 7.7 s. Link and advertise the final URL directly.
Reduce unused JavaScript
1.1 s · 846 KiBAbout 846 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.1 s faster on a phone.
Render-blocking requests
1.8 s5 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.8 s.
Main-thread work: 7.0 s
A phone's processor spends 7.0 s on main-thread work while loading, 2.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (wagwear.com, rebuyengine.com and loox.io and others), adding 20.3 MB and 1.4 s of main-thread time.
wagwear.com adds 279 ms
279 mswagwear.com costs a phone 279 ms of main-thread work and 18.8 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: 56
56/100Your mobile performance score is 56. Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
300 ms · 97 KiBAbout 97 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
Improve image delivery
50 ms · 284 KiB8 images could be 284 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 50 ms faster on a phone.
rebuyengine.com adds 228 ms
228 msrebuyengine.com costs a phone 228 ms of main-thread work and 686 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 168 ms
168 msShopify costs a phone 168 ms of main-thread work and 354 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.
1,551 HTML elements
The page has 1,551 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
12 long tasks on the main thread
12 long tasks block the main thread while loading, the longest for 190 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
188 KiB21 files are served with short cache lifetimes, so returning visitors download them again (188 KiB).
Document request latency
100 msThe HTML itself could arrive about 100 ms sooner: redirects, a slow server response or missing compression delay everything after it.
Legacy JavaScript
82 KiBPolyfills for old browsers add 82 KiB JavaScript that modern phones do not need.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Minify JavaScript
14 KiB14 KiB could be saved by minifying JavaScript.
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: 7 ms
7 msYour server sent the HTML in 7 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 27.0 s
27.0 sThe page becomes fully interactive after 27.0 s. Good is under 3.8 s.
Largest Contentful Paint: 9.2 s
9.2 sYour largest element takes 9.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Two mulberry dog boots with ankle straps, shown on a solid …”.
Speed Index: 9.1 s
9.1 sVisually, the page fills in at 9.1 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 340 ms
340 msScripts block taps and scrolling for 340 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 2.3 s
2.3 sThe first text or image appears after 2.3 s on a phone. Good is under 1.8 s.
7 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.7 s
1.7 sReal visitors wait 1.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 113 ms
113 msReal visitors wait 113 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: 557 ms
557 msReal visitors wait 557 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 21.9 MB in 397 requests
21.9 MBYour homepage downloads 21.9 MB in 397 requests on a phone: media 16.7 MB (4), scripts 2.4 MB (174) and images 1.0 MB (41). Under 2 MB keeps phones on slow connections fast.
5 images in older formats
5 images (1,014 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.
About 6.2 g of CO₂ per visit
6.21 gBy the Sustainable Web Design model, a visit to your homepage emits about 6.21 g of CO₂e: 745.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
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
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.
2 tap targets too small
2 tap targets are too small or too close together to hit reliably with a finger.
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h1 → h4, h2 → h4 and h2 → h4), 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 35 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 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 2 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
3 H1 headlines
There are 3 <h1> headlines (“”, “” and “WagWellies® Mojave - Red”). One clear main headline is easier for people and search engines.
Structured data has 1 problem
Structured data found (untyped) but with 1 problem, for example “ld+json block 1 is not valid JSON (Expected double-quoted property name in JSON at position 269)”.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
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.
90 internal links, 6 external
The homepage links to 90 pages on wagwear.com.au and 6 external pages.
6 checks passed
Meta description: 121 characters
Your meta description is 121 characters: “Fashion & Style for the design minded dog. The internet's favorite dog boot has arrived in Australia. Meet the Wagwelli…”.
Title: 55 characters
Your title is a healthy 55 characters: “Wagwear | For the Design Minded Dog – wagwear-australia”.
Canonical URL set
The canonical URL is https://wagwear.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://wagwear.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 (506 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://wagwear.com.au/llms.txt (5 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
14 pages share a meta description
https://wagwear.com.au/products/wagwellies%C2%AE-mojave-sage-copy-1, https://wagwear.com.au/products/wagwellies%C2%AE-mojave-sage-copy, https://wagwear.com.au/products/wagwellies%C2%AE-mojave-sand-copy, https://wagwear.com.au/products/wagwellies%C2%AE-mojave, https://wagwear.com.au/products/wagwellies%C2%AE-mojave-neon-green and https://wagwear.com.au/products/wagwellies%C2%AE-mojave-neon-orange and 6 others use the same meta description. A description written for each page earns more clicks.
12 links to non-canonical URLs
Your homepage links to 12 pages by a URL that isn't their canonical one, for example https://wagwear.com.au/products/wagwellies%C2%AE-mojave-sage-copy-1, whose canonical is https://wagwear.com.au/products/wagwellies%c2%ae-mojave-sage-copy-1. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 30 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.
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
Deprecated browser APIs
The page uses 2 deprecated browser APIs that will stop working in future browsers (“CSS appearance value `slider-vertical` is not standardized and will be removed.”).
2 JavaScript errors while loading
2 errors were 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
41 of 42 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: 39 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 701 words of copy
The homepage carries about 701 words of visible text.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP NOW”.
8 calls to action
The homepage has 8 calls to action, for example “Contact”, “SHOP NOW” and “Shop Now”.
5 short forms
5 short forms (2 fields at most) are right on the homepage.
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.
12 cookies set on arrival
12Opening the homepage sets 12 cookies, 1 of them by other companies (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.
21 other companies contacted
Loading the homepage contacts 21 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 wagwear.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 6 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Precom Coming Soon Preorders · Selecty · Fabrikator Inventory Assistant · loox.io · googleapis.com · klaviyo.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 36 issues on wagwear.com.au, including 17 speed issues, 4 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.