Website readiness profile · Snapshot 23 October 2026
tilannehuone.fi
tilannehuone.fi's public homepage, certificate and DNS checked against 31 practices and compared with 3,856 News & Media sites.
- Readiness index
- 45/100
- Ahead of
- 2.5%
- Practices observed
- 12/31
- Popularity band
- Top 50K
News & Media median 68
of measured News & Media sites
0 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: tilannehuone.fi. Thin bar: News & Media peer median.
Enable
49/100
Peers 89
Harden
43/100
Peers 56
Accelerate
48/100
Peers 68
Recover
0/100
Peers 11
Priority fixes for tilannehuone.fi
Ordered by impact and by how common each practice is among peers.
Priority 1 · Enable
robots.txt published
Observed: No robots.txt file was returned at the site root.
Why it matters: robots.txt is where crawlers look first for crawl rules and sitemap locations. Without it, they assume everything is open.
What to do: Publish /robots.txt with any crawl rules you need and a Sitemap: line pointing to your XML sitemap.
98% of News & Media peers do this. Limit: Only the standard location was requested, once, at the time of the check.
Guide: Robots.txt Guide: Control Crawling Without Hiding Mistakes
Priority 2 · 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.
87% of News & Media peers do this.
Guide: XML Sitemap Guide: Include Only URLs You Stand Behind
Priority 3 · 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.
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.
60% of News & Media peers do this.
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.
35% of News & Media peers do this.
What tilannehuone.fi already does well
Practices fewer than half of News & Media peers use.
- HTTP/3 advertisedHTTP/3 advertised.36% of peers
What we saw
- Homepage checked
- https://www.tilannehuone.fi/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, HTTP/2
- Certificate
- Google Trust Services, 90-day validity, expiring 2027-01-14
- CDN or edge
- Cloudflare
- DNS operators
- Cloudflare
- Homepage HTML
- 84 KB, br
- Images on homepage
- 58 (png 118, gif 15, jpg 4)
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 19
- 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
- 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
- Canonical URL declared
- Structured data present
- Page language declared
- Nameservers spread across providers
Observed 12
- 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
- HTTP/3 advertised
- HTML compressed
- Reachable over IPv6
- Meta description written
- Mobile viewport configured
- Social preview image set
- At most one redirect to the homepage
Own tilannehuone.fi?
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: tilannehuone.fi. This profile covers configuration only.