www.gov.pt

Readiness by lane

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

Priority fixes for www.gov.pt

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 · Harden

   DMARC policy enforces quarantine or reject

   Observed: No DMARC record was found at _dmarc.www.gov.pt.

   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.

   52% of Government Services peers do this.

   Guide: A Practical Website Health Check for Owners

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

   61% of Government Services peers do this.

   Guide: Robots.txt Guide: Control Crawling Without Hiding Mistakes

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

What www.gov.pt already does well

Practices fewer than half of Government Services peers use.

• Static files cached for 30 days or moreLong-lived caching on static files.30% of peers
• Referrer-Policy setReferrer-Policy present.39% of peers
• No render-blocking scripts in <head>Head scripts load without blocking.39% of peers

What we saw

Homepage checked

https://www.gov.pt/

Homepage response

HTTP 200

TLS

TLSv1.3, http/1.1

Certificate

GlobalSign, 396-day validity, expiring 2027-01-13

Platform or framework

Next.js

HSTS

max-age 365 days, includeSubDomains

Homepage HTML

229 KB, gzip

Images on homepage

12

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

• cadastre.gouv.fr50
• dpsa.gov.za50
• seg-social.pt51
• tntenders.gov.in51
• uppolice.gov.in51

Government Services readiness benchmark