goias.gov.br

Readiness by lane

Green: goias.gov.br. Thin bar: Government Services peer median.

Priority fixes for goias.gov.br

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

   HSTS kept for at least a year

   Observed: Strict-Transport-Security was sent with a max-age of 91 days, below the one-year benchmark.

   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.

   51% of Government Services peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

3. Priority 3 · Accelerate

   No render-blocking scripts in <head>

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

   On WordPress: Since WordPress 6.3, scripts can be registered with a defer or async loading strategy.

   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 goias.gov.br already does well

Practices fewer than half of Government Services peers use.

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

What we saw

Homepage checked

https://goias.gov.br/

Homepage response

HTTP 200

TLS

TLSv1.3

Certificate

Let's Encrypt, 89-day validity, expiring 2027-01-07

Platform or framework

WordPress

DNS operators

2 self-run or other nameserver domains

HSTS

max-age 91 days, includeSubDomains

DMARC policy

p=quarantine

Homepage HTML

170 KB, gzip

Images on homepage

35 (jpg 9, png 6)

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

• ctet.nic.in62
• isro.gov.in62
• mppe.gob.ve62
• rnp.gob.pe63
• sssalud.gob.ar63

Government Services readiness benchmark