www.gov.pl

Readiness by lane

Green: www.gov.pl. Thin bar: Government Services peer median.

Priority fixes for www.gov.pl

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

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

   55% of Government Services peers do this. Limit: Certificate and protocol were observed from one vantage point; CDNs can present different certificates by region.

   Guide: CDN Guide for Website Owners

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.

   42% of Government Services peers do this.

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

3. Priority 3 · Accelerate

   No render-blocking scripts in <head>

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

   39% of Government Services peers do this.

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

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.

   58% of Government Services peers do this.

   Guide: Meta Titles and Descriptions That Match Search Intent

What www.gov.pl already does well

Practices fewer than half of Government Services peers use.

• DNSSEC signedDNSSEC delegation (DS record) present.19% of peers
• Reachable over IPv6IPv6 address published.27% of peers
• Static files cached for 30 days or moreLong-lived caching on static files.30% of peers

What we saw

Homepage checked

https://www.gov.pl/

Homepage response

HTTP 200

TLS

TLSv1.3

Certificate

Asseco Data Systems S.A., 364-day validity, expiring 2026-12-31

DNS operators

1 self-run or other nameserver domain

HSTS

max-age 365 days, includeSubDomains, preload

DMARC policy

p=quarantine

Homepage HTML

39 KB, gzip

Images on homepage

68 (svg 46)

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 Government Services sites

• btl.gov.il56
• dgii.gov.do56
• immigration.govt.nz57
• indianfrro.gov.in57
• moncompteformation.gouv.fr57

Government Services readiness benchmark