Website readiness profile · Snapshot 23 October 2026
wwesupercard.com
wwesupercard.com's public homepage, certificate and DNS checked against 31 practices and compared with 485 Gaming Platforms & Consoles sites.
- Readiness index
- 88/100
- Ahead of
- 99%
- Practices observed
- 26/31
- Popularity band
- Top 50K
Gaming Platforms & Consoles median 62
of measured Gaming Platforms & Consoles sites
0 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: wwesupercard.com. Thin bar: Gaming Platforms & Consoles peer median.
Enable
100/100
Peers 76
Harden
74/100
Peers 53
Accelerate
100/100
Peers 63
Recover
100/100
Peers 6
Priority fixes for wwesupercard.com
Ordered by impact and by how common each practice is among peers.
Priority 1 · Harden
Certificate lifetime of 100 days or less
Observed: The certificate from Amazon had a 197-day validity period, longer than the 100-day maximum that applies from March 2027.
Why it matters: Under CA/Browser Forum Ballot SC-081v3, the maximum lifetime of public TLS certificates fell to 200 days on 15 March 2026 and falls to 100 days on 15 March 2027 and 47 days on 15 March 2029. Sites that renew by hand will need to renew far more often.
What to do: Move to automated issuance and renewal now, while you still have time to test it.
76% of Gaming Platforms & Consoles peers do this. Limit: Certificate and protocol were observed from one vantage point; CDNs can present different certificates by region.
Priority 2 · Harden
X-Content-Type-Options: nosniff
Observed: The homepage response did not include X-Content-Type-Options: nosniff.
What to do: Send X-Content-Type-Options: nosniff on all responses and make sure each file is served with the correct Content-Type.
On Amazon CloudFront: Enable it in a response headers policy (security headers section).
38% of Gaming Platforms & Consoles peers do this.
Priority 3 · Harden
CAA records limit who can issue certificates
Observed: No CAA record was found for wwesupercard.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.
11% of Gaming Platforms & Consoles 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.
3.7% of Gaming Platforms & Consoles peers do this.
What wwesupercard.com already does well
Practices fewer than half of Gaming Platforms & Consoles peers use.
- Nameservers spread across providersNameservers spread across more than one operator.5.8% of peers
- Content Security Policy presentContent-Security-Policy present.22% of peers
- DMARC policy enforces quarantine or rejectDMARC policy p=reject.26% of peers
What we saw
- Homepage checked
- https://www.wwesupercard.com/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, HTTP/2
- Certificate
- Amazon, 197-day validity, expiring 2027-02-22
- CDN or edge
- Amazon CloudFront
- Platform or framework
- Next.js
- DNS operators
- NS1, plus 1 self-run or other nameserver domain
- HSTS
- max-age 365 days, includeSubDomains, preload
- DMARC policy
- p=reject
- Homepage HTML
- 1,076 KB, gzip
- Images on homepage
- 131 (png 1608, jpg 497)
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 5
Observed 26
- HTTP requests move to HTTPS
- HSTS kept for at least a year
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- DMARC policy enforces quarantine or reject
- Framing restricted
- Content Security Policy present
- Referrer-Policy set
- HTTP/2 negotiated
- HTTP/3 advertised
- HTML compressed
- Static files cached for 30 days or more
- Modern image formats in use
- 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
- Nameservers spread across providers
Own wwesupercard.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: wwesupercard.com. This profile covers configuration only.