Website review, no card needed
wwd.com website review
Visit site (opens in a new tab)Reviewed 12 October 202626 issues · 65 checks
This review found 26 issues worth fixing on wwd.com, 10 of them high impact, across 65 checks. The most urgent: fails Core Web Vitals for real visitors. Google's speed test didn't respond, so speed is not measured here; your full playbook measures it. 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
Not scored yet: Google's speed test didn't run in this review. Re-run the review to get a score.
Show as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 18, 2026 | 2.0 s |
| Apr 25, 2026 | 2.0 s |
| May 2, 2026 | 2.0 s |
| May 9, 2026 | 2.0 s |
| May 16, 2026 | 2.0 s |
| May 23, 2026 | 2.0 s |
| May 30, 2026 | 2.0 s |
| Jun 6, 2026 | 2.0 s |
| Jun 13, 2026 | 2.0 s |
| Jun 20, 2026 | 1.9 s |
| Jun 27, 2026 | 1.9 s |
| Jul 4, 2026 | 1.8 s |
| Jul 11, 2026 | 1.8 s |
| Jul 18, 2026 | 1.8 s |
| Jul 25, 2026 | 1.8 s |
| Aug 1, 2026 | 1.8 s |
| Aug 8, 2026 | 1.8 s |
| Aug 15, 2026 | 1.8 s |
| Aug 22, 2026 | 1.8 s |
| Aug 29, 2026 | 1.8 s |
| Sep 5, 2026 | 1.8 s |
| Sep 12, 2026 | 1.7 s |
| Sep 19, 2026 | 1.7 s |
| Sep 26, 2026 | 1.7 s |
| Oct 3, 2026 | 1.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 18, 2026 | 208 ms |
| Apr 25, 2026 | 205 ms |
| May 2, 2026 | 197 ms |
| May 9, 2026 | 191 ms |
| May 16, 2026 | 180 ms |
| May 23, 2026 | 177 ms |
| May 30, 2026 | 180 ms |
| Jun 6, 2026 | 179 ms |
| Jun 13, 2026 | 178 ms |
| Jun 20, 2026 | 176 ms |
| Jun 27, 2026 | 171 ms |
| Jul 4, 2026 | 169 ms |
| Jul 11, 2026 | 170 ms |
| Jul 18, 2026 | 170 ms |
| Jul 25, 2026 | 170 ms |
| Aug 1, 2026 | 169 ms |
| Aug 8, 2026 | 166 ms |
| Aug 15, 2026 | 165 ms |
| Aug 22, 2026 | 167 ms |
| Aug 29, 2026 | 169 ms |
| Sep 5, 2026 | 167 ms |
| Sep 12, 2026 | 167 ms |
| Sep 19, 2026 | 163 ms |
| Sep 26, 2026 | 161 ms |
| Oct 3, 2026 | 160 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
Speed
Not measured in this review.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on your site (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Real-user CLS: 0.31
0.31For real visitors the layout shifts by 0.31 (75th percentile). Good is under 0.1.
6 checks passed
Real-user LCP: 1.8 s
1.8 sReal visitors wait 1.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 159 ms
159 msReal visitors wait 159 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.5 s
1.5 sReal visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 565 ms
565 msReal visitors wait 565 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 22% faster for real visitors
-22%Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' tap response (inp) went from 208 ms to 160 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 12% faster for real visitors
-12%Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' largest content (lcp) went from 2.0 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 4.5 MB
4.5 MBYour homepage downloads 4.5 MB on a phone, 340 KiB of it images (7%). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
27 KiB1 image is downloaded at several times the size a phone draws it, for example WWD20261009_cover.jpg at 250 px wide, shown at 60 px. Resized copies would save about 27 KiB.
About 1.3 g of CO₂ per visit
1.27 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.27 g of CO₂e: 152.4 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 load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
17 tap targets too small
17 tap targets are too small or too close together to hit reliably with a finger.
Hidden but focusable
13 elements hidden from screen readers can still receive keyboard focus.
Interactive controls must not be nested (5 elements)
Interactive controls must not be nested: 5 elements on the page fail this check, rated serious by axe-core.
Frames without titles
2 frames have no title, so screen-reader users cannot tell what they contain.
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
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.
31 links without text
31 visible links have no text or label, so screen readers cannot say where they go.
3 form fields without a label
3 form fields have no label, so screen readers announce an empty box and autofill guesses.
2 checks passed
Every image has alt text
All 63 images in the HTML carry an alt attribute.
46 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: 46 passed and 7 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is long (153 characters)
Your title is 153 characters, so Google will cut it off around 60: “WWD – Women's Wear Daily brings you breaking news about the fashion industry, designers, …”.
333 internal links, 80 external
The homepage links to 333 pages on wwd.com and 80 external pages.
6 checks passed
Meta description: 147 characters
Your meta description is 147 characters: “Women's Wear Daily brings you breaking news about the fashion industry, designers, celebrity trend setters, and extensi…”.
Canonical URL set
The canonical URL is https://wwd.com/.
Structured data in place
Structured data found: Organization and WebPage.
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://wwd.com/sitemap_index.xml.
AI search readiness
robots.txt blocks 3 AI answer engine crawlers
3 of 6Your robots.txt shuts out ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User) and Perplexity (PerplexityBot). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
No llms.txt
There is no /llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.
Opted out of AI training for 5 crawlers
robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.
1 checks passed
Text is in the HTML
Your server sends the page's text in the HTML (2,069 words), so crawlers that don't run JavaScript still read it.
Other pages
11 pages without a meta description
/footwear-news, /sourcing-journal, /p/wwd-weekend, /beauty-industry-news, /news-tip and /wwd-publications/digital-daily/2026-10-09-1239334802 and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example /runway, whose canonical is /runway/spring-2027. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
9 pages without an H1
/footwear-news, /sourcing-journal, /p/wwd-weekend, /beauty-industry-news, /wwd-publications/digital-daily/2026-10-09-1239334802 and /fashion-news and 3 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 180 found) and read each the way a search engine does.
4 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.
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 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=25063342&Ver=2&mid=dbfae26a-1950-4a41-b866-516e75c24435&bo=1&sid=c94b03c0c5e711f1845d8111715621da&vid=c94b28d0c5e711f1a44a9f306eacf8c1&vids=1&msclkid=N&pi=918639831&lg.
12 small tap targets
12 of 37 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
1 checks passed
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 phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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,382 words of copy
The homepage carries about 1,382 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “LOG IN SIGN UP”.
18 calls to action
The homepage has 18 calls to action, for example “Log In Sign Up”, “Subscribe to our Newsletter” and “Sign Up Sign Up”.
4 short forms
4 short forms (1 field at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, Hotjar and LinkedIn Insight.
Privacy and tracking
16 trackers load before any consent
16Before a visitor clicks anything, the page loads Amazon Ads, Comscore, Criteo, Google Ads and Google Analytics and 11 mores (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.
47 cookies set on arrival
47Opening the homepage sets 47 cookies (measured from a US location before any click).
97 other companies contacted
Loading the homepage contacts 97 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) loads with the page.
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 wwd.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Go beyond the website
What your $25 Growth Playbook adds
This review found 26 issues on wwd.com, including 2 speed issues, 2 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.