grundos.cafe

Readiness by lane

Green: grundos.cafe. Thin bar: Forums & Communities peer median.

Priority fixes for grundos.cafe

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.

   90% of Forums & Communities 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

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

   61% of Forums & Communities peers do this.

   Guide: XML Sitemap Guide: Include Only URLs You Stand Behind

3. Priority 3 · Harden

   DMARC policy enforces quarantine or reject

   Observed: The DMARC policy for grundos.cafe was p=none, which asks receivers to take no action on failing mail.

   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.

   31% of Forums & Communities peers do this.

   Guide: A Practical Website Health Check for Owners

4. Priority 4 · Accelerate

   No render-blocking scripts in <head>

   Observed: The homepage <head> loaded 2 external scripts without async or defer.

   What to do: Add defer to scripts that need the DOM, async to independent ones such as analytics, or move them to the end of the body.

   41% of Forums & Communities peers do this.

   Guide: Control Third-Party Scripts Before They Control Your Page

What grundos.cafe already does well

Practices fewer than half of Forums & Communities peers use.

• Content Security Policy presentContent-Security-Policy present.17% of peers
• Referrer-Policy setReferrer-Policy present.25% of peers
• HSTS kept for at least a yearHSTS with a 365-day max-age covering subdomains.28% of peers

What we saw

Homepage checked

https://grundos.cafe/

Homepage response

HTTP 200, after 1 redirect

TLS

TLSv1.3, HTTP/2

Certificate

Google Trust Services, 90-day validity, expiring 2026-11-27

CDN or edge

Cloudflare

DNS operators

Cloudflare

HSTS

max-age 365 days, includeSubDomains, preload

DMARC policy

p=none

Homepage HTML

26 KB, br

Images on homepage

2 (gif 1, png 1)

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

Compare with other Forums & Communities sites

• discord-ch.site68
• filmmakers.co.kr68
• furbooru.org68
• head-fi.org68
• hiveworkshop.com68

Forums & Communities readiness benchmark