Website review, no card needed
thewolfgang.com website review
Visit site (opens in a new tab)Reviewed 8 November 202638 issues · 92 checks
This review found 38 issues worth fixing on thewolfgang.com, 9 of them high impact, across 92 checks. The most urgent: improve image delivery. 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- #9,989 of 99,948 reviewed websitesbeats 86%
- #5,970 of 54,914 online storesbeats 85%
- #5,787 of 49,854 Shopify storesbeats 83%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.9 s |
| May 23, 2026 | 1.9 s |
| May 30, 2026 | 1.8 s |
| Jun 6, 2026 | 1.8 s |
| Jun 13, 2026 | 1.6 s |
| Jun 20, 2026 | 1.6 s |
| Jun 27, 2026 | 1.5 s |
| Jul 4, 2026 | 1.5 s |
| Jul 11, 2026 | 1.5 s |
| Jul 18, 2026 | 1.5 s |
| Jul 25, 2026 | 1.5 s |
| Aug 1, 2026 | 1.5 s |
| Aug 8, 2026 | 1.5 s |
| Aug 15, 2026 | 1.5 s |
| Aug 22, 2026 | 1.6 s |
| Aug 29, 2026 | 1.5 s |
| Sep 5, 2026 | 1.6 s |
| Sep 12, 2026 | 1.7 s |
| Sep 19, 2026 | 1.7 s |
| Sep 26, 2026 | 1.6 s |
| Oct 3, 2026 | 1.6 s |
| Oct 10, 2026 | 1.7 s |
| Oct 17, 2026 | 1.7 s |
| Oct 24, 2026 | 1.8 s |
| Oct 31, 2026 | 1.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 192 ms |
| May 23, 2026 | 187 ms |
| May 30, 2026 | 185 ms |
| Jun 6, 2026 | 188 ms |
| Jun 13, 2026 | 227 ms |
| Jun 20, 2026 | 239 ms |
| Jun 27, 2026 | 244 ms |
| Jul 4, 2026 | 237 ms |
| Jul 11, 2026 | 212 ms |
| Jul 18, 2026 | 187 ms |
| Jul 25, 2026 | 188 ms |
| Aug 1, 2026 | 187 ms |
| Aug 8, 2026 | 200 ms |
| Aug 15, 2026 | 220 ms |
| Aug 22, 2026 | 225 ms |
| Aug 29, 2026 | 237 ms |
| Sep 5, 2026 | 245 ms |
| Sep 12, 2026 | 242 ms |
| Sep 19, 2026 | 241 ms |
| Sep 26, 2026 | 270 ms |
| Oct 3, 2026 | 268 ms |
| Oct 10, 2026 | 285 ms |
| Oct 17, 2026 | 287 ms |
| Oct 24, 2026 | 280 ms |
| Oct 31, 2026 | 266 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
Improve image delivery
2.6 s · 1.2 MB24 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.6 s faster on a phone.
Main-thread work: 7.6 s
A phone's processor spends 7.6 s on main-thread work while loading, 2.0 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 (Shopify, Google Tag Manager and Clarity and others), adding 8.0 MB and 741 ms of main-thread time.
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 ms5 files block the first paint until they finish downloading. Deferring or inlining them could save about 850 ms.
Vimeo adds 104 ms
104 msVimeo costs a phone 104 ms of main-thread work and 6.9 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.
Reduce unused JavaScript
467 KiBAbout 467 KiB of JavaScript is downloaded but never used on this page.
Shopify adds 181 ms
181 msShopify costs a phone 181 ms of main-thread work and 668 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.
2,299 HTML elements
The page has 2,299 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 140 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
111 KiB17 files are served with short cache lifetimes, so returning visitors download them again (111 KiB).
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Reduce unused CSS
45 KiBAbout 45 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
42 KiBPolyfills for old browsers add 42 KiB JavaScript that modern phones do not need.
Minify JavaScript
22 KiB22 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.
Duplicated JavaScript
3 KiB3 KiB JavaScript is shipped twice across bundles.
Minify CSS
2 KiB2 KiB could be saved by minifying CSS.
1 checks passed
Server response: 13 ms
13 msYour server sent the HTML in 13 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 7.6 s
7.6 sYour largest element takes 7.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 16.1 s
16.1 sThe page becomes fully interactive after 16.1 s. Good is under 3.8 s.
Tap response (INP) got 44% slower for real visitors
+44%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 192 ms to 266 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Speed Index: 3.7 s
3.7 sVisually, the page fills in at 3.7 s (Speed Index). Good is under 3.4 s.
Largest content (LCP) held steady for real visitors
-5%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.9 s to 1.8 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: 155 ms
155 msReal visitors wait 155 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: 412 ms
412 msReal visitors wait 412 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.4 s
1.4 sThe first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.
Total Blocking Time: 124 ms
124 msScripts block the page for only 124 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.023
0.023The layout barely moves while loading (CLS 0.023, good is under 0.1).
Images and page weight
Page weight: 10.8 MB in 368 requests
10.8 MBYour homepage downloads 10.8 MB in 368 requests on a phone: other files 7.3 MB (153), images 1.5 MB (29) and scripts 1.5 MB (141). Under 2 MB keeps phones on slow connections fast.
2 images far larger than shown
349 KiB2 images are downloaded at several times the size a phone draws them, for example Resort_16x9_2_trim_4.5s_small_973250e7-0b85-4bdb-8af8-e79e44 at 390 px wide, shown at 53 px. Resized copies would save about 349 KiB.
1 image in older formats
1 image (358 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 3.1 g of CO₂ per visit
3.07 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.07 g of CO₂e: 368.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
5 buttons without a name
5 buttons have no accessible name, so screen readers announce just “button”.
26 tap targets too small
26 tap targets are too small or too close together to hit reliably with a finger.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
The skip-link target should exist and be focusable (1 element)
The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.
34 links without text
34 visible links have no text or label, so screen readers cannot say where they go.
26 form fields without a label
26 form fields have no label, so screen readers announce an empty box and autofill guesses.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
Headings should not be empty (2 elements)
Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 66 images in the HTML carry an alt attribute.
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 8 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is long (232 characters)
Your meta description is 232 characters; Google truncates after about 160, so the end of your pitch is cut.
179 internal links, 8 external
The homepage links to 179 pages on thewolfgang.com and 8 external pages.
7 checks passed
One H1 headline
Your main headline reads: “The Wolf Gang — bold print dresses & colourful Australian fashion”.
Title: 63 characters
Your title is a healthy 63 characters: “The Wolf Gang | Bold Print Dresses & Australian Women's Fashion”.
Canonical URL set
The canonical URL is https://thewolfgang.com/.
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://thewolfgang.com/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 (703 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://thewolfgang.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://thewolfgang.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.
2 linked pages hidden from search
https://thewolfgang.com/collections/coming-soon and https://thewolfgang.com/customer_authentication/redirect are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
5 pages without a meta description
https://thewolfgang.com/collections/shop-all-usa, https://thewolfgang.com/collections/private-sale-usa, https://thewolfgang.com/customer_authentication/redirect, https://thewolfgang.com/collections/bottoms and https://thewolfgang.com/collections/all-accessories-bags have no meta description, so Google writes the search snippet from whatever text it finds.
2 links to non-canonical URLs
Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://thewolfgang.com/collections/shop-all-usa, whose canonical is https://thewolfgang.com/collections/shop-all. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
15 pages without an H1
https://thewolfgang.com/collections/shop-all-usa, https://thewolfgang.com/collections/new-arrivals, https://thewolfgang.com/collections/best-sellers, https://thewolfgang.com/collections/coming-soon, https://thewolfgang.com/collections/private-sale-usa and https://thewolfgang.com/customer_authentication/redirect and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.
7 pages with very little text
https://thewolfgang.com/collections/new-arrivals, https://thewolfgang.com/collections/best-sellers, https://thewolfgang.com/collections/private-sale-usa, https://thewolfgang.com/collections/tops, https://thewolfgang.com/collections/bottoms and https://thewolfgang.com/collections/outerwear and 1 other have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 63 found) and read each the way a search engine does.
2 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Titles are unique
Every page we checked has its own title.
Best practices
10 broken images
10 images failed to load on a phone, for example https://thewolfgang.com/.
51 small tap targets
51 of 117 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 third-party cookies
2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://a.klaviyo.com/media/css/public/klaviyo_subscribe.css' from origin 'https://thewolf…”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 5 testimonial or review blocks. 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.
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 421 words of copy
The homepage carries about 421 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop New Arrivals”.
7 calls to action
The homepage has 7 calls to action, for example “Shop All”, “Shop New Arrivals” and “Preorder Open: Shop the Tippia Dress”.
8 short forms
8 short forms (6 fields at most) are right on the homepage.
Analytics in place
Analytics detected: Google Analytics and Microsoft Clarity.
Privacy and tracking
9 trackers load before any consent
9Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 4 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.
23 cookies set on arrival
23Opening the homepage sets 23 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.
41 other companies contacted
Loading the homepage contacts 41 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 thewolfgang.com, 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
Judge Me Reviews · Klaviyo Email Marketing Sms · Inbox · Microsoft Clarity · Twg Cart · amazonaws.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
- Analytics
- Google 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 38 issues on thewolfgang.com, including 13 speed issues, 1 SEO issue 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.