Website readiness profile · Snapshot 23 October 2026
runescape.wiki
runescape.wiki's public homepage, certificate and DNS checked against 31 practices and compared with 696 Literary & Knowledge sites.
- Readiness index
- 84/100
- Ahead of
- 96%
- Practices observed
- 26/31
- Popularity band
- Top 10K
Literary & Knowledge median 62
of measured Literary & Knowledge sites
0 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: runescape.wiki. Thin bar: Literary & Knowledge peer median.
Enable
100/100
Peers 78
Harden
85/100
Peers 51
Accelerate
70/100
Peers 62
Recover
0/100
Peers 6
Priority fixes for runescape.wiki
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 300 seconds, 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 · Accelerate
Modern image formats in use
Observed: The homepage had 28 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.
31% of Literary & Knowledge peers do this.
Guide: AVIF, WebP, JPEG, and PNG: Choose the Right Image Format
Priority 3 · Harden
DMARC policy enforces quarantine or reject
Observed: No DMARC record was found at _dmarc.runescape.wiki.
What to do: Publish DMARC with p=none and a reporting address first, fix any legitimate senders that fail SPF or DKIM alignment, then move to quarantine and finally reject.
22% 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 runescape.wiki already does well
Practices fewer than half of Literary & Knowledge peers use.
- DNSSEC signedDNSSEC delegation (DS record) present.5.7% of peers
- CAA records limit who can issue certificatesCAA limits issuance to comodoca.com, digicert.com, letsencrypt.org and others.13% of peers
- Content Security Policy presentContent-Security-Policy present.18% of peers
What we saw
- Homepage checked
- https://runescape.wiki/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, HTTP/2
- Certificate
- Let's Encrypt, 89-day validity, expiring 2026-12-02
- CDN or edge
- Cloudflare, Google edge
- DNS operators
- Cloudflare
- HSTS
- max-age 365 days, includeSubDomains, preload
- Homepage HTML
- 58 KB, br
- Images on homepage
- 28 (png 52, svg 2)
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
- 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/2 negotiated
- HTTP/3 advertised
- HTML compressed
- 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 runescape.wiki?
Re-run the checks after a change, keep a private action plan in a free workspace, or report a mistake.
Live status for this site: Status Is Down: runescape.wiki. This profile covers configuration only.