Website readiness profile · Snapshot 23 October 2026
vorwerk.com
vorwerk.com's public homepage, certificate and DNS checked against 31 practices and compared with 5,718 E-Commerce & Marketplaces sites.
- Readiness index
- 55/100
- Ahead of
- 11%
- Practices observed
- 13/28
- Popularity band
- Top 50K
E-Commerce & Marketplaces median 71
of measured E-Commerce & Marketplaces sites
3 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: vorwerk.com. Thin bar: E-Commerce & Marketplaces peer median.
Enable
64/100
Peers 86
Harden
54/100
Peers 60
Accelerate
50/100
Peers 69
Recover
0/100
Peers 11
Priority fixes for vorwerk.com
Ordered by impact and by how common each practice is among peers.
Priority 1 · Accelerate
HTML compressed
Observed: The homepage HTML (221 KB) was delivered without gzip, Brotli or zstd compression.
Why it matters: Compression usually shrinks HTML several times over, so the first bytes of the page arrive sooner on slow connections.
What to do: Enable Brotli or gzip for text responses (HTML, CSS, JavaScript, JSON, SVG) at the CDN or origin.
On Amazon CloudFront: Enable Compress objects automatically on the cache behaviour.
97% of E-Commerce & Marketplaces peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.
Guide: How to Set a Website Performance Budget That Teams Can Keep
Priority 2 · Enable
Meta description written
Observed: The homepage had no meta description.
What to do: Write a short, specific description of the page for people, not a list of keywords.
95% of E-Commerce & Marketplaces peers do this.
Guide: Meta Titles and Descriptions That Match Search Intent
Priority 3 · 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 Amazon CloudFront: Attach a response headers policy with Strict-Transport-Security to each distribution.
32% of E-Commerce & Marketplaces peers do this.
Priority 4 · Enable
Canonical URL declared
Observed: The homepage did not declare a canonical URL.
What to do: Add a self-referencing canonical link to every indexable page, using the final https:// URL.
85% of E-Commerce & Marketplaces peers do this.
What vorwerk.com already does well
Practices fewer than half of E-Commerce & Marketplaces peers use.
- security.txt publishedsecurity.txt with a contact found.7.6% of peers
- DMARC policy enforces quarantine or rejectDMARC policy p=reject.39% of peers
- Reachable over IPv6IPv6 address published.40% of peers
What we saw
- Homepage checked
- https://www.vorwerk.com/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, HTTP/2
- Certificate
- Amazon, 394-day validity, expiring 2027-02-17
- CDN or edge
- Amazon CloudFront
- DNS operators
- Amazon Route 53
- DMARC policy
- p=reject
- Homepage HTML
- 221 KB, uncompressed
- Images on homepage
- 0
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 15
- HSTS kept for at least a year
- Certificate lifetime of 100 days or less
- CAA records limit who can issue certificates
- DNSSEC signed
- X-Content-Type-Options: nosniff
- Framing restricted
- Content Security Policy present
- Referrer-Policy set
- HTTP/3 advertised
- HTML compressed
- Canonical URL declared
- Meta description written
- Structured data present
- Social preview image set
- Nameservers spread across providers
Observed 13
- HTTP requests move to HTTPS
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- security.txt published
- DMARC policy enforces quarantine or reject
- HTTP/2 negotiated
- No render-blocking scripts in <head>
- robots.txt published
- XML sitemap discoverable
- Reachable over IPv6
- Mobile viewport configured
- Page language declared
- At most one redirect to the homepage
Not measured 3
- Static files cached for 30 days or more
- Modern image formats in use
- Offscreen images lazy-loaded
Own vorwerk.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: vorwerk.com. This profile covers configuration only.