Website review, no card needed
wildthreadsco.com website review
Visit site (opens in a new tab)Reviewed 6 November 202628 issues · 75 checks
This review found 28 issues worth fixing on wildthreadsco.com, 6 of them high impact, across 75 checks. The most urgent: 41 tap targets too small. 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,849 of 98,383 reviewed websitesbeats 86%
- #5,848 of 53,710 online storesbeats 84%
- #5,666 of 48,711 Shopify storesbeats 83%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.2 s |
| May 23, 2026 | 1.1 s |
| May 30, 2026 | 1.0 s |
| Jun 6, 2026 | 935 ms |
| Jun 13, 2026 | 911 ms |
| Jun 20, 2026 | 908 ms |
| Jun 27, 2026 | 922 ms |
| Jul 4, 2026 | 950 ms |
| Jul 11, 2026 | 957 ms |
| Jul 18, 2026 | 943 ms |
| Jul 25, 2026 | 932 ms |
| Aug 1, 2026 | 912 ms |
| Aug 8, 2026 | 908 ms |
| Aug 15, 2026 | 911 ms |
| Aug 22, 2026 | 909 ms |
| Aug 29, 2026 | 911 ms |
| Sep 5, 2026 | 927 ms |
| Sep 12, 2026 | 924 ms |
| Sep 19, 2026 | 931 ms |
| Sep 26, 2026 | 961 ms |
| Oct 3, 2026 | 933 ms |
| Oct 10, 2026 | 974 ms |
| Oct 17, 2026 | 971 ms |
| Oct 24, 2026 | 918 ms |
| Oct 31, 2026 | 914 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 87 ms |
| May 23, 2026 | 87 ms |
| May 30, 2026 | 87 ms |
| Jun 6, 2026 | 88 ms |
| Jun 13, 2026 | 92 ms |
| Jun 20, 2026 | 94 ms |
| Jun 27, 2026 | 96 ms |
| Jul 4, 2026 | 96 ms |
| Jul 11, 2026 | 96 ms |
| Jul 18, 2026 | 96 ms |
| Jul 25, 2026 | 95 ms |
| Aug 1, 2026 | 94 ms |
| Aug 8, 2026 | 95 ms |
| Aug 15, 2026 | 95 ms |
| Aug 22, 2026 | 95 ms |
| Aug 29, 2026 | 95 ms |
| Sep 5, 2026 | 96 ms |
| Sep 12, 2026 | 96 ms |
| Sep 19, 2026 | 96 ms |
| Sep 26, 2026 | 96 ms |
| Oct 3, 2026 | 96 ms |
| Oct 10, 2026 | 97 ms |
| Oct 17, 2026 | 96 ms |
| Oct 24, 2026 | 96 ms |
| Oct 31, 2026 | 93 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.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Reduce unused JavaScript
321 KiBAbout 321 KiB of JavaScript is downloaded but never used on this page.
Render-blocking requests
300 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 300 ms.
Shopify adds 137 ms
137 msShopify costs a phone 137 ms of main-thread work and 466 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.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, Klaviyo and sealsubscriptions.com and others), adding 675 KiB and 198 ms of main-thread time.
Improve image delivery
135 KiB5 images could be 135 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 122 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
68 KiB10 files are served with short cache lifetimes, so returning visitors download them again (68 KiB).
Reduce unused CSS
53 KiBAbout 53 KiB of CSS is downloaded but never applied on this page.
Minify JavaScript
27 KiB27 KiB could be saved by minifying JavaScript.
Legacy JavaScript
19 KiBPolyfills for old browsers add 19 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.
3 checks passed
Mobile performance score: 96
96/100Your mobile performance score is 96. That is in Google's “good” band (90 and up).
Main-thread work: 1.3 s
A phone's processor spends 1.3 s on main-thread work while loading, 551 ms of it running JavaScript. That is comfortably low.
Server response: 6 ms
6 msYour server sent the HTML in 6 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 8.4 s
8.4 sThe page becomes fully interactive after 8.4 s. Good is under 3.8 s.
Speed Index: 4.3 s
4.3 sVisually, the page fills in at 4.3 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 1.9 s
1.9 sThe first text or image appears after 1.9 s on a phone. Good is under 1.8 s.
Tap response (INP) held steady for real visitors
+9%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 87 ms to 93 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
10 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: 87 ms
87 msReal visitors wait 87 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.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 675 ms
675 msReal visitors wait 675 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 19% faster for real visitors
-19%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.2 s to 0.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest Contentful Paint: 1.9 s
1.9 sYour largest element renders in 1.9 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “WILD CHILD COLLECTION”.
Cumulative Layout Shift: 0.022
0.022The layout barely moves while loading (CLS 0.022, good is under 0.1).
Total Blocking Time: 39 ms
39 msScripts block the page for only 39 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 2.3 MB in 219 requests
2.3 MBYour homepage downloads 2.3 MB in 219 requests on a phone: scripts 883 KiB (58), other files 811 KiB (117) and images 486 KiB (34). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
Festive_Stock_Up_Sale_Banner.png 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).
About 0.6 g of CO₂ per visit
0.65 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.65 g of CO₂e: 77.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
41 tap targets too small
41 tap targets are too small or too close together to hit reliably with a finger.
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.
3 links without text
3 visible links have no text or label, so screen readers cannot say where they go.
2 checks passed
Every image has alt text
All 46 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 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 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
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Title is short (15 characters)
Your title is only 15 characters: “Wild Threads Co”. Between 30 and 65 characters leaves room to say what you do and for whom.
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.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
120 internal links, 3 external
The homepage links to 120 pages on wildthreadsco.com and 3 external pages.
4 checks passed
One H1 headline
Your main headline reads: “Wild Threads Co”.
Canonical URL set
The canonical URL is https://www.wildthreadsco.com/.
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.wildthreadsco.com/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 (449 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.wildthreadsco.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page points its canonical at the homepage
https://www.wildthreadsco.com/products/wild-threads-t-shirt-club-2 declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.
2 pages share a title
/ and https://www.wildthreadsco.com/products/wild-threads-t-shirt-club-2 all use the title “Wild Threads Co”. Search engines can't tell which page to show for a search, so each competes with the others.
14 pages without a meta description
https://www.wildthreadsco.com/collections/shop-all-top-36, https://www.wildthreadsco.com/collections/hunting-top-6, https://www.wildthreadsco.com/collections/fishing-top-6, https://www.wildthreadsco.com/collections/wild-child-top-6, https://www.wildthreadsco.com/collections/holiday-top-6 and https://www.wildthreadsco.com/collections/bible-verse-top-6 and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.
13 pages without an H1
https://www.wildthreadsco.com/collections/shop-all-top-36, https://www.wildthreadsco.com/collections/hunting-top-6, https://www.wildthreadsco.com/collections/fishing-top-6, https://www.wildthreadsco.com/collections/wild-child-top-6, https://www.wildthreadsco.com/collections/holiday-top-6 and https://www.wildthreadsco.com/collections/bible-verse-top-6 and 7 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 41 found) and read each the way a search engine does.
3 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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
35 small tap targets
35 of 66 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
1 checks passed
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 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 267 words of copy
The homepage carries about 267 words of visible text.
2 checks passed
24 calls to action
The homepage has 24 calls to action, for example “Contact Us”, “Quick Shop” and “icon-email Subscribe”.
3 short forms
3 short forms (1 field at most) are right on the homepage.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Klaviyo 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.
16 cookies set on arrival
16Opening the homepage sets 16 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.
18 other companies contacted
Loading the homepage contacts 18 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 wildthreadsco.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 10 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Klaviyo Email Marketing Sms · Attentive · Slide Cart · Freegifts · jsdelivr.net · jst.ai · cloudfront.net · sealsubscriptions.com · attn.tv · postscript.io
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 28 issues on wildthreadsco.com, including 6 speed issues, 5 SEO issues and 4 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.