Website readiness profile · Snapshot 23 October 2026
wefashion.com
wefashion.com's public homepage, certificate and DNS checked against 31 practices and compared with 5,718 E-Commerce & Marketplaces sites.
- Readiness index
- 72/100
- Ahead of
- 54%
- Practices observed
- 19/29
- Popularity band
- Top 50K
E-Commerce & Marketplaces median 71
of measured E-Commerce & Marketplaces sites
2 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: wefashion.com. Thin bar: E-Commerce & Marketplaces peer median.
Enable
79/100
Peers 86
Harden
60/100
Peers 60
Accelerate
87/100
Peers 69
Recover
100/100
Peers 11
Priority fixes for wefashion.com
Ordered by impact and by how common each practice is among peers.
Priority 1 · Harden
TLS 1.3 negotiated
Observed: The TLS connection negotiated TLSv1.2.
Why it matters: TLS 1.3 removes legacy cipher suites and completes the handshake in fewer round trips, so it is both safer and faster for new connections.
What to do: Enable TLS 1.3 on your CDN or server. Keep TLS 1.2 available for older clients unless you have checked your audience.
On Cloudflare: Turn on TLS 1.3 under SSL/TLS > Edge Certificates.
93% of E-Commerce & Marketplaces peers do this. Limit: Certificate and protocol were observed from one vantage point; CDNs can present different certificates by region.
Priority 2 · Harden
HSTS kept for at least a year
Observed: The homepage response did not include a Strict-Transport-Security header.
What to do: Send Strict-Transport-Security on HTTPS responses. Start with a short max-age (for example 300 seconds), confirm every subdomain works over HTTPS, then raise it in steps to 31536000. Add includeSubDomains only when all subdomains are HTTPS. HSTS preload is optional and hard to undo; hstspreload.org itself does not recommend it by default.
On Cloudflare: Enable HSTS under SSL/TLS > Edge Certificates > HTTP Strict Transport Security and raise max-age gradually.
32% of E-Commerce & Marketplaces peers do this.
Priority 3 · Accelerate
HTTP/3 advertised
Observed: The homepage did not advertise HTTP/3 through an Alt-Svc header.
What to do: Turn on HTTP/3 at your CDN. Browsers fall back to HTTP/2 automatically, so the risk is low.
On Cloudflare: Enable HTTP/3 (with QUIC) under Speed > Optimization > Protocol Optimization.
47% of E-Commerce & Marketplaces peers do this.
Priority 4 · Harden
Certificate lifetime of 100 days or less
Observed: The certificate from Sectigo Limited had a 379-day validity period, longer than the 100-day maximum that applies from March 2027.
What to do: Move to automated issuance and renewal now, while you still have time to test it.
70% of E-Commerce & Marketplaces peers do this.
What wefashion.com already does well
Practices fewer than half of E-Commerce & Marketplaces peers use.
- DNSSEC signedDNSSEC delegation (DS record) present.7.7% of peers
- Nameservers spread across providersNameservers spread across more than one operator.11% of peers
- DMARC policy enforces quarantine or rejectDMARC policy p=reject.39% of peers
What we saw
- Homepage checked
- https://www.wefashion.com/
- Homepage response
- HTTP 200
- TLS
- TLSv1.2, HTTP/2
- Certificate
- Sectigo, 379-day validity, expiring 2026-12-08
- CDN or edge
- Cloudflare
- DNS operators
- 3 self-run or other nameserver domains
- DMARC policy
- p=reject
- Homepage HTML
- 40 KB, br
- Images on homepage
- 1
Limits: homepage only, one location, one moment. Header checks reflect the homepage response; other pages may differ.
Stack and providers
Seen in the homepage response, certificate and DNS. Provider pages compare how their customers configure the same checks.
All 31 checks
Select a gap for the method and fix. How each check works
Not observed 10
Observed 19
- HTTP requests move to HTTPS
- Certificate has more than 14 days left
- DNSSEC signed
- DMARC policy enforces quarantine or reject
- X-Content-Type-Options: nosniff
- Framing restricted
- Content Security Policy present
- HTTP/2 negotiated
- HTML compressed
- Static files cached for 30 days or more
- No render-blocking scripts in <head>
- robots.txt published
- XML sitemap discoverable
- Canonical URL declared
- Meta description written
- Mobile viewport configured
- Page language declared
- At most one redirect to the homepage
- Nameservers spread across providers
Not measured 2
- Modern image formats in use
- Offscreen images lazy-loaded
Own wefashion.com?
Re-run the checks after a change, or verify the site in a free workspace to save reports with history, compare against similar sites and competitors, and track a private action plan. What owners get.
Live status for this site: Status Is Down: wefashion.com. This profile covers configuration only.