STATUS IS UPREADINESS PROFILE

Website readiness profile · Snapshot 23 October 2026

sefaz.rs.gov.br

sefaz.rs.gov.br's public homepage, certificate and DNS checked against 31 practices and compared with 954 Government Services sites.

Readiness index
31/100

Government Services median 53

Ahead of
6.3%

of measured Government Services sites

Practices observed
9/30

1 of 31 could not be measured

Popularity band
Top 50K

Chrome UX Report top-sites list

Measured 2026-10-23 11:46:11 UTC from one location. How we measure

Readiness by lane

Green: sefaz.rs.gov.br. Thin bar: Government Services peer median.

Enable

56/100

Peers 59

Harden

25/100

Peers 59

Accelerate

15/100

Peers 41

Recover

0/100

Peers 25

Priority fixes for sefaz.rs.gov.br

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

  1. Priority 1 · Harden

    HTTP requests move to HTTPS

    Observed: A request to http://www.sefaz.rs.gov.br/ was not redirected to HTTPS.

    Why it matters: Visitors who type the address or follow an old link start on unencrypted HTTP. A redirect moves them to the encrypted site before any cookies or form data are sent.

    What to do: Add a permanent (301 or 308) redirect from every http:// URL to the same https:// URL at your CDN, load balancer or web server.

    88% of Government Services peers do this. Limit: Measured for the homepage only, from one location, at the time of the check.

  2. Priority 2 · Accelerate

    HTML compressed

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

    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.

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

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

What sefaz.rs.gov.br already does well

Practices fewer than half of Government Services peers use.

  • Social preview image setog:image present.36% of peers
  • No render-blocking scripts in <head>Head scripts load without blocking.39% of peers

What we saw

Homepage checked
https://www.sefaz.rs.gov.br/
Homepage response
HTTP 200, after 3 redirects
TLS
TLSv1.2
Certificate
DigiCert, 198-day validity, expiring 2026-11-21
DNS operators
1 self-run or other nameserver domain
DMARC policy
p=none
Homepage HTML
115 KB, uncompressed
Images on homepage
45 (png 56, svg 5)

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

Own sefaz.rs.gov.br?

Re-run the checks after a change, or verify the site in a free workspace to save reports with history, compare against similar sites and competitors, and track a private action plan. What owners get.

Live status for this site: Status Is Down: sefaz.rs.gov.br. This profile covers configuration only.

Compare with other Government Services sites