Website readiness profile · Snapshot 23 October 2026
yugioh-wiki.net
yugioh-wiki.net's public homepage, certificate and DNS checked against 31 practices and compared with 696 Literary & Knowledge sites.
- Readiness index
- 86/100
- Ahead of
- 98%
- Practices observed
- 24/29
- Popularity band
- Top 50K
Literary & Knowledge median 62
of measured Literary & Knowledge sites
2 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: yugioh-wiki.net. Thin bar: Literary & Knowledge peer median.
Enable
92/100
Peers 78
Harden
88/100
Peers 51
Accelerate
80/100
Peers 62
Recover
0/100
Peers 6
Priority fixes for yugioh-wiki.net
Ordered by impact and by how common each practice is among peers.
Priority 1 · Accelerate
Static files cached for 30 days or more
Observed: A same-site stylesheet or script was cacheable for 1 days, short of the 30-day benchmark.
Why it matters: Returning visitors and later page views reuse cached files instead of downloading them again.
What to do: Give versioned (fingerprinted) CSS, JavaScript, fonts and images Cache-Control: public, max-age=31536000, immutable, and change the file name whenever the content changes.
On Cloudflare: Use Cache Rules to set edge and browser TTLs for static file paths.
49% of Literary & Knowledge peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.
Priority 2 · Enable
Structured data present
Observed: The homepage had no JSON-LD structured data.
What to do: Add JSON-LD for your organization and main content types, then test it with Google's Rich Results Test.
46% of Literary & Knowledge peers do this.
Priority 3 · Harden
CAA records limit who can issue certificates
Observed: No CAA record was found for yugioh-wiki.net, 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 Literary & Knowledge 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.
5% of Literary & Knowledge peers do this.
What yugioh-wiki.net already does well
Practices fewer than half of Literary & Knowledge peers use.
- DNSSEC signedDNSSEC delegation (DS record) present.5.7% of peers
- Content Security Policy presentContent-Security-Policy present.18% of peers
- DMARC policy enforces quarantine or rejectDMARC policy p=reject.22% of peers
What we saw
- Homepage checked
- https://yugioh-wiki.net/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, HTTP/2
- Certificate
- Google Trust Services, 90-day validity, expiring 2027-01-04
- CDN or edge
- Cloudflare
- DNS operators
- Cloudflare
- HSTS
- max-age 365 days, includeSubDomains
- DMARC policy
- p=reject
- Homepage HTML
- 35 KB, br
- 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 5
Observed 24
- HTTP requests move to HTTPS
- HSTS kept for at least a year
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- Certificate lifetime of 100 days or less
- DNSSEC signed
- DMARC policy enforces quarantine or reject
- X-Content-Type-Options: nosniff
- Framing restricted
- Content Security Policy present
- Referrer-Policy set
- HTTP/2 negotiated
- HTTP/3 advertised
- HTML compressed
- No render-blocking scripts in <head>
- robots.txt published
- XML sitemap discoverable
- Reachable over IPv6
- Canonical URL declared
- Meta description written
- Mobile viewport configured
- Social preview image set
- Page language declared
- At most one redirect to the homepage
Not measured 2
- Modern image formats in use
- Offscreen images lazy-loaded
Own yugioh-wiki.net?
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: yugioh-wiki.net. This profile covers configuration only.