Website readiness profile · Snapshot 23 October 2026
22s5.com
22s5.com's public homepage, certificate and DNS checked against 31 practices and compared with 233 Data & Analytics sites.
- Readiness index
- 55/100
- Ahead of
- 21%
- Practices observed
- 14/29
- Popularity band
- Top 10K
Data & Analytics median 63
of measured Data & Analytics sites
2 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: 22s5.com. Thin bar: Data & Analytics peer median.
Enable
51/100
Peers 78
Harden
48/100
Peers 56
Accelerate
80/100
Peers 63
Recover
0/100
Peers 8
Priority fixes for 22s5.com
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 no max-age, 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 Data & Analytics peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.
Priority 2 · Harden
HSTS kept for at least a year
Observed: Strict-Transport-Security was sent with a max-age of 0 days, below the one-year benchmark.
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.
34% of Data & Analytics peers do this.
Priority 3 · Enable
Meta description written
Observed: The homepage had no meta description.
What to do: Write a short, specific description of the page for people, not a list of keywords.
92% of Data & Analytics peers do this.
Guide: Meta Titles and Descriptions That Match Search Intent
Priority 4 · 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.
63% of Data & Analytics peers do this.
Guide: XML Sitemap Guide: Include Only URLs You Stand Behind
What 22s5.com already does well
Practices fewer than half of Data & Analytics peers use.
- HTTP/3 advertisedHTTP/3 advertised.37% of peers
- X-Content-Type-Options: nosniffnosniff header present.46% of peers
- Reachable over IPv6IPv6 address published.49% of peers
What we saw
- Homepage checked
- https://22s5.com/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, HTTP/2
- Certificate
- Google Trust Services, 90-day validity, expiring 2026-12-10
- CDN or edge
- Cloudflare
- DNS operators
- Cloudflare
- HSTS
- max-age 0 days
- Homepage HTML
- 4 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 15
- 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
- Framing restricted
- Content Security Policy present
- Referrer-Policy set
- Static files cached for 30 days or more
- XML sitemap discoverable
- Canonical URL declared
- Meta description written
- Structured data present
- Social preview image set
- Nameservers spread across providers
Observed 14
- HTTP requests move to HTTPS
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- Certificate lifetime of 100 days or less
- X-Content-Type-Options: nosniff
- HTTP/2 negotiated
- HTTP/3 advertised
- HTML compressed
- No render-blocking scripts in <head>
- robots.txt published
- Reachable over IPv6
- Mobile viewport configured
- Page language declared
- At most one redirect to the homepage
Not measured 2
- Modern image formats in use
- Offscreen images lazy-loaded
Own 22s5.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: 22s5.com. This profile covers configuration only.