Website review, no card needed
whatwears.com website review
Visit site (opens in a new tab)Reviewed 13 November 202625 issues · 65 checks
This review found 25 issues worth fixing on whatwears.com, 7 of them high impact, across 65 checks. The most urgent: images must have alternative text (1 element). 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
One score from every part of this review. How it works
Speed
Improve image delivery
350 ms · 979 KiB18 images could be 979 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.
Mobile performance score: 73
73/100Your mobile performance score is 73. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
450 ms · 85 KiBAbout 85 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.
Reduce unused CSS
450 ms · 38 KiBAbout 38 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
Render-blocking requests
400 ms12 files block the first paint until they finish downloading. Deferring or inlining them could save about 400 ms.
5 third-party services on the page
5 third-party services load with your homepage (Privy, Shopify and shopclimb.com and others), adding 339 KiB and 122 ms of main-thread time.
1 long task on the main thread
1 long task block the main thread while loading, the longest for 99 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
14 KiB3 files are served with short cache lifetimes, so returning visitors download them again (14 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.
2 checks passed
Main-thread work: 1.0 s
A phone's processor spends 1.0 s on main-thread work while loading, 321 ms of it running JavaScript. That is comfortably low.
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: 11.6 s
11.6 sYour largest element takes 11.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: 12.0 s
12.0 sThe page becomes fully interactive after 12.0 s. Good is under 3.8 s.
Speed Index: 3.7 s
3.7 sVisually, the page fills in at 3.7 s (Speed Index). Good is under 3.4 s.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
3 checks passed
First Contentful Paint: 1.8 s
1.8 sThe first text or image appears after 1.8 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.001
0.001The layout barely moves while loading (CLS 0.001, good is under 0.1).
Total Blocking Time: 25 ms
25 msScripts block the page for only 25 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 3.3 MB in 198 requests
3.3 MBYour homepage downloads 3.3 MB in 198 requests on a phone: images 2.1 MB (56), other files 729 KiB (85) and scripts 355 KiB (40). Under 2 MB keeps phones on slow connections fast.
About 0.9 g of CO₂ per visit
0.93 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.93 g of CO₂e: 111.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
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
Images must have alternative text (1 element)
Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.
3 text elements with low contrast
3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 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.
Alternative text of images should not be repeated as text (7 elements)
Alternative text of images should not be repeated as text: 7 elements on the page fail this check, rated minor by axe-core.
1 checks passed
43 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 5 failed. 1 more 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.
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Canonical points to another host
Your canonical URL points to mangocouture.com, not whatwears.com, so Google may credit that host instead.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
83 internal links, 4 external
The homepage links to 83 pages on whatwears.com and 4 external pages.
4 checks passed
Title: 63 characters
Your title is a healthy 63 characters: “Mangocouture Fashion Online Store for Affordable Women Clothing”.
Structured data in place
Structured data found: Organization and WebSite.
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://whatwears.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 (268 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://whatwears.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
8 pages without a meta description
https://whatwears.com/collections/dress-main, https://whatwears.com/collections/bottom, https://whatwears.com/collections/rompers-jumpsuits, https://whatwears.com/collections/matching-sets-main, https://whatwears.com/collections/tops and https://whatwears.com/collections/outerwear and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 32 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.
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.
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
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Uncaught (in promise) TypeError: Cannot destructure property 'name' of 'e' as it is undefined.”.
2 checks passed
Tap targets are thumb-sized
32 of 33 tappable elements near the top are at least 24 px.
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.
Thin social proof
Social proof on the homepage: 32 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.
Only about 168 words
The homepage has only about 168 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
3 checks passed
6 calls to action
The homepage has 6 calls to action, for example “register”, “Subscribe” and “Contact Us”.
3 short forms
3 short forms (1 field at most) are right on the homepage, asking for an email.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
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.
11 cookies set on arrival
11Opening the homepage sets 11 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.
12 other companies contacted
Loading the homepage contacts 12 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 whatwears.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 2 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
privy.com · shopclimb.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
- Framework
- Bootstrap
- 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 whatwears.com, including 8 speed issues, 4 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.