dges.gov.pt

Readiness by lane

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

Priority fixes for dges.gov.pt

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

1. Priority 1 · Accelerate

   HTML compressed

   Observed: The homepage HTML (2 KB) was delivered without gzip, Brotli or zstd compression.

   Why it matters: Compression usually shrinks HTML several times over, so the first bytes of the page arrive sooner on slow connections.

   What to do: Enable Brotli or gzip for text responses (HTML, CSS, JavaScript, JSON, SVG) at the CDN or origin.

   74% of Government Services peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.

   Guide: How to Set a Website Performance Budget That Teams Can Keep

2. Priority 2 · Harden

   TLS 1.3 negotiated

   Observed: The TLS connection negotiated TLSv1.2.

   What to do: Enable TLS 1.3 on your CDN or server. Keep TLS 1.2 available for older clients unless you have checked your audience.

   77% of Government Services peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

3. Priority 3 · Accelerate

   HTTP/2 negotiated

   Observed: The TLS handshake selected http/1.1 instead of HTTP/2.

   What to do: Enable HTTP/2 on your CDN or server. Most CDNs do this by default.

   55% of Government Services peers do this.

   Guide: CDN Guide for Website Owners

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

   On Azure Front Door/CDN: Add a response header action in a Front Door rule set.

   51% of Government Services peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

What dges.gov.pt already does well

Practices fewer than half of Government Services peers use.

• CAA records limit who can issue certificatesCAA limits issuance to digicert.com, harica.gr, letsencrypt.org.17% of peers
• DNSSEC signedDNSSEC delegation (DS record) present.19% of peers
• Nameservers spread across providersNameservers spread across more than one operator.25% of peers

What we saw

Homepage checked

https://dges.gov.pt/

Homepage response

HTTP 200, after 1 redirect

TLS

TLSv1.2, http/1.1

Certificate

Hellenic Academic and Research Institutions CA, 365-day validity, expiring 2026-11-10

CDN or edge

Azure Front Door/CDN

DNS operators

2 self-run or other nameserver domains

DMARC policy

p=reject

Homepage HTML

2 KB, uncompressed

Images on homepage

1 (jpg 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 Government Services sites

• browardclerk.org42
• bseh.org.in42
• dian.gov.co42
• etrade.gov.et42
• www.gob.mx43

Government Services readiness benchmark