Website readiness profile · Snapshot 23 October 2026
puzzlist.com
puzzlist.com's public homepage, certificate and DNS checked against 31 practices and compared with 522 Puzzles & Video Games sites.
- Readiness index
- 48/100
- Ahead of
- 19%
- Practices observed
- 11/29
- Popularity band
- Top 50K
Puzzles & Video Games median 60
of measured Puzzles & Video Games sites
2 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: puzzlist.com. Thin bar: Puzzles & Video Games peer median.
Enable
44/100
Peers 74
Harden
43/100
Peers 50
Accelerate
67/100
Peers 60
Recover
0/100
Peers 7
Priority fixes for puzzlist.com
Ordered by impact and by how common each practice is among peers.
Priority 1 · Enable
Meta description written
Observed: The homepage had no meta description.
Why it matters: Search engines often use it for the snippet under your link, so a clear description can improve click-through.
What to do: Write a short, specific description of the page for people, not a list of keywords.
93% of Puzzles & Video Games peers do this. Limit: Based on the homepage HTML delivered to an automated client; scripts that run later were not executed.
Guide: Meta Titles and Descriptions That Match Search Intent
Priority 2 · Accelerate
Static files cached for 30 days or more
Observed: A same-site stylesheet or script was cacheable for 4 hours, short of the 30-day benchmark.
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.
44% of Puzzles & Video Games peers do this.
Priority 3 · Enable
XML sitemap discoverable
Observed: No sitemap was listed in robots.txt or found at /sitemap.xml.
What to do: Generate an XML sitemap of canonical URLs, reference it in robots.txt and submit it in Google Search Console.
60% of Puzzles & Video Games peers do this.
Guide: XML Sitemap Guide: Include Only URLs You Stand Behind
Priority 4 · 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 Cloudflare: Enable HSTS under SSL/TLS > Edge Certificates > HTTP Strict Transport Security and raise max-age gradually.
23% of Puzzles & Video Games peers do this.
What puzzlist.com already does well
Practices fewer than half of Puzzles & Video Games peers use.
- Reachable over IPv6IPv6 address published.50% of peers
What we saw
- Homepage checked
- https://puzzlist.com/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, HTTP/2
- Certificate
- Google Trust Services, 90-day validity, expiring 2026-11-23
- CDN or edge
- Cloudflare
- DNS operators
- Cloudflare
- DMARC policy
- p=none
- Homepage HTML
- 1 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 18
- HSTS kept for at least a year
- CAA records limit who can issue certificates
- DNSSEC signed
- security.txt published
- DMARC policy enforces quarantine or reject
- X-Content-Type-Options: nosniff
- Framing restricted
- Content Security Policy present
- Referrer-Policy set
- HTTP/3 advertised
- Static files cached for 30 days or more
- XML sitemap discoverable
- Canonical URL declared
- Meta description written
- Structured data present
- Social preview image set
- Page language declared
- Nameservers spread across providers
Observed 11
- HTTP requests move to HTTPS
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- Certificate lifetime of 100 days or less
- HTTP/2 negotiated
- HTML compressed
- No render-blocking scripts in <head>
- robots.txt published
- Reachable over IPv6
- Mobile viewport configured
- At most one redirect to the homepage
Not measured 2
- Modern image formats in use
- Offscreen images lazy-loaded
Own puzzlist.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: puzzlist.com. This profile covers configuration only.