in-pocasi.cz

Readiness by lane

Green: in-pocasi.cz. Thin bar: Weather Forecast peer median.

Priority fixes for in-pocasi.cz

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 Weather Forecast 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 · 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.

   39% of Weather Forecast peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

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

   66% of Weather Forecast peers do this.

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

4. Priority 4 · Accelerate

   No render-blocking scripts in <head>

   Observed: The homepage <head> loaded 3 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.

   56% of Weather Forecast peers do this.

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

What in-pocasi.cz already does well

Practices fewer than half of Weather Forecast peers use.

• DNSSEC signedDNSSEC delegation (DS record) present.12% of peers
• Nameservers spread across providersNameservers spread across more than one operator.14% of peers
• Static files cached for 30 days or moreLong-lived caching on static files.48% of peers

What we saw

Homepage checked

https://www.in-pocasi.cz/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Let's Encrypt, 89-day validity, expiring 2026-11-30

DNS operators

3 self-run or other nameserver domains

Homepage HTML

59 KB, gzip

Images on homepage

35 (svg 32, jpg 2, gif 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 Weather Forecast sites

• buienradar.be51
• donnerwetter.de52
• meteomaroc.com51
• sat24.com52
• weather.gc.ca51

Weather Forecast readiness benchmark