Website readiness profile · Snapshot 23 October 2026
debeste.de
debeste.de's public homepage, certificate and DNS checked against 31 practices and compared with 377 Forums & Communities sites.
- Readiness index
- 37/100
- Ahead of
- 4.2%
- Practices observed
- 10/31
- Popularity band
- Top 50K
Forums & Communities median 62
of measured Forums & Communities sites
0 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: debeste.de. Thin bar: Forums & Communities peer median.
Enable
51/100
Peers 74
Harden
34/100
Peers 54
Accelerate
30/100
Peers 60
Recover
0/100
Peers 7
Priority fixes for debeste.de
Ordered by impact and by how common each practice is among peers.
Priority 1 · Accelerate
HTTP/2 negotiated
Observed: The TLS handshake selected http/1.1 instead of HTTP/2.
Why it matters: HTTP/2 sends many files over one connection, which speeds up pages with lots of images, styles and scripts.
What to do: Enable HTTP/2 on your CDN or server. Most CDNs do this by default.
87% of Forums & Communities peers do this. Limit: Certificate and protocol were observed from one vantage point; CDNs can present different certificates by region.
Priority 2 · Harden
TLS 1.3 negotiated
Observed: The TLS connection negotiated TLSv1.2.
What to do: Enable TLS 1.3 on your CDN or server. Keep TLS 1.2 available for older clients unless you have checked your audience.
88% of Forums & Communities peers do this.
Priority 3 · Enable
robots.txt published
Observed: No robots.txt file was returned at the site root.
What to do: Publish /robots.txt with any crawl rules you need and a Sitemap: line pointing to your XML sitemap.
90% of Forums & Communities peers do this.
Guide: Robots.txt Guide: Control Crawling Without Hiding Mistakes
Priority 4 · 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.
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.
51% of Forums & Communities peers do this.
What we saw
- Homepage checked
- https://debeste.de/
- Homepage response
- HTTP 200
- TLS
- TLSv1.2, http/1.1
- Certificate
- Let's Encrypt, 89-day validity, expiring 2026-12-29
- DNS operators
- OVHcloud DNS
- Homepage HTML
- 38 KB, gzip
- Images on homepage
- 28 (png 15, jpg 9, gif 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 21
- HSTS kept for at least a year
- TLS 1.3 negotiated
- 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/2 negotiated
- HTTP/3 advertised
- Static files cached for 30 days or more
- Modern image formats in use
- No render-blocking scripts in <head>
- robots.txt published
- XML sitemap discoverable
- Reachable over IPv6
- Canonical URL declared
- Structured data present
- Nameservers spread across providers
Observed 10
- HTTP requests move to HTTPS
- Certificate has more than 14 days left
- Certificate lifetime of 100 days or less
- HTML compressed
- Offscreen images lazy-loaded
- Meta description written
- Mobile viewport configured
- Social preview image set
- Page language declared
- At most one redirect to the homepage
Own debeste.de?
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: debeste.de. This profile covers configuration only.