STATUS IS UPREADINESS PROFILE

Website readiness profile · Snapshot 23 October 2026

trauerhilfe.at

trauerhilfe.at's public homepage, certificate and DNS checked against 31 practices and compared with 69 Family & Heritage sites.

Readiness index
51/100

Family & Heritage median 67

Ahead of
8.7%

of measured Family & Heritage sites

Practices observed
13/31

0 of 31 could not be measured

Popularity band
Top 50K

Chrome UX Report top-sites list

Measured 2026-10-23 12:13:32 UTC from one location. How we measure

Readiness by lane

Green: trauerhilfe.at. Thin bar: Family & Heritage peer median.

Enable

56/100

Peers 80

Harden

48/100

Peers 61

Accelerate

53/100

Peers 60

Recover

0/100

Peers 7

Priority fixes for trauerhilfe.at

Ordered by impact and by how common each practice is among peers.

  1. 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.

    94% of Family & Heritage peers do this. Limit: Only the standard location was requested, once, at the time of the check.

  2. Priority 2 · 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.

    43% of Family & Heritage peers do this.

  3. Priority 3 · Harden

    DMARC policy enforces quarantine or reject

    Observed: No DMARC record was found at _dmarc.trauerhilfe.at.

    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.

    46% of Family & Heritage peers do this.

  4. Priority 4 · 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.

    88% of Family & Heritage peers do this.

What we saw

Homepage checked
https://www.trauerhilfe.at/
Homepage response
HTTP 200
TLS
TLSv1.3, HTTP/2
Certificate
Let's Encrypt, 89-day validity, expiring 2026-11-24
DNS operators
1 self-run or other nameserver domain
Homepage HTML
18 KB, gzip
Images on homepage
12 (jpg 6, gif 4, png 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

Observed 13

  • 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
  • HTML compressed
  • Static files cached for 30 days or more
  • XML sitemap discoverable
  • Canonical URL declared
  • Mobile viewport configured
  • Page language declared
  • At most one redirect to the homepage

Own trauerhilfe.at?

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: trauerhilfe.at. This profile covers configuration only.

Compare with other Family & Heritage sites