Website readiness profile · Snapshot 23 October 2026
wired.com
wired.com's public homepage, certificate and DNS checked against 31 practices and compared with 3,856 News & Media sites.
- Readiness index
- 81/100
- Ahead of
- 92%
- Practices observed
- 24/31
- Popularity band
- Top 50K
News & Media median 68
of measured News & Media sites
0 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: wired.com. Thin bar: News & Media peer median.
Enable
100/100
Peers 89
Harden
69/100
Peers 56
Accelerate
85/100
Peers 68
Recover
0/100
Peers 11
Priority fixes for wired.com
Ordered by impact and by how common each practice is among peers.
Priority 1 · Harden
HSTS kept for at least a year
Observed: The homepage response did not include a Strict-Transport-Security header.
Why it matters: HSTS tells browsers to use HTTPS for your host on every later visit, which removes the window where a first HTTP request can be intercepted.
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.
35% of News & Media peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.
Priority 2 · Accelerate
Modern image formats in use
Observed: The homepage had 53 images and none used WebP or AVIF.
What to do: Serve WebP or AVIF with a JPEG or PNG fallback, either through an image CDN or by generating both formats at build time.
On Cloudflare: Cloudflare Polish can convert images to WebP.
44% of News & Media peers do this.
Guide: AVIF, WebP, JPEG, and PNG: Choose the Right Image Format
Priority 3 · Harden
CAA records limit who can issue certificates
Observed: No CAA record was found for wired.com, so any public certificate authority may issue for it.
What to do: Publish CAA records naming every CA you actually use, including the CAs your CDN uses for managed certificates. Add an iodef contact if you want reports.
On Cloudflare: Cloudflare documents which CAs its managed certificates need; include them in your CAA records.
13% of News & Media peers do this.
Priority 4 · Harden
security.txt published
Observed: No valid /.well-known/security.txt with a Contact field was returned.
What to do: Publish /.well-known/security.txt with at least Contact and Expires fields, as RFC 9116 requires, and review it before it expires.
On Cloudflare: Cloudflare Security Center can serve a security.txt file for the zone.
6.2% of News & Media peers do this.
What wired.com already does well
Practices fewer than half of News & Media peers use.
- Content Security Policy presentContent-Security-Policy present.29% of peers
- HTTP/3 advertisedHTTP/3 advertised.36% of peers
- DMARC policy enforces quarantine or rejectDMARC policy p=reject.37% of peers
What we saw
- Homepage checked
- https://www.wired.com/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, HTTP/2
- Certificate
- Let's Encrypt, 89-day validity, expiring 2026-12-05
- CDN or edge
- Cloudflare, Amazon CloudFront
- DNS operators
- Amazon Route 53
- DMARC policy
- p=reject
- Homepage HTML
- 1,592 KB, br
- Images on homepage
- 53 (jpg 475, gif 18, png 12, svg 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 7
Observed 24
- HTTP requests move to HTTPS
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- Certificate lifetime of 100 days or less
- DMARC policy enforces quarantine or reject
- X-Content-Type-Options: nosniff
- Framing restricted
- Content Security Policy present
- HTTP/2 negotiated
- HTTP/3 advertised
- HTML compressed
- Static files cached for 30 days or more
- Offscreen images lazy-loaded
- No render-blocking scripts in <head>
- robots.txt published
- XML sitemap discoverable
- Reachable over IPv6
- Canonical URL declared
- Meta description written
- Mobile viewport configured
- Structured data present
- Social preview image set
- Page language declared
- At most one redirect to the homepage
Own wired.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: wired.com. This profile covers configuration only.