STATUS IS UPREADINESS PROFILE

Website readiness profile · Snapshot 23 October 2026

gov.hr

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

Readiness index
44/100

Government Services median 53

Ahead of
26%

of measured Government Services sites

Practices observed
12/31

0 of 31 could not be measured

Popularity band
Top 50K

Chrome UX Report top-sites list

Measured 2026-10-23 12:20:16 UTC from one location. How we measure

Readiness by lane

Green: gov.hr. Thin bar: Government Services peer median.

Enable

33/100

Peers 59

Harden

63/100

Peers 59

Accelerate

20/100

Peers 41

Recover

100/100

Peers 25

Priority fixes for gov.hr

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.

  2. Priority 2 · Harden

    DMARC policy enforces quarantine or reject

    Observed: No DMARC record was found at _dmarc.gov.hr.

    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.

  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.

  4. Priority 4 · Accelerate

    Static files cached for 30 days or more

    Observed: A same-site stylesheet or script was cacheable for 7 days, short of the 30-day benchmark.

    What to do: Give versioned (fingerprinted) CSS, JavaScript, fonts and images Cache-Control: public, max-age=31536000, immutable, and change the file name whenever the content changes.

    30% of Government Services peers do this.

What gov.hr already does well

Practices fewer than half of Government Services peers use.

  • Nameservers spread across providersNameservers spread across more than one operator.25% of peers
  • Referrer-Policy setReferrer-Policy present.39% of peers

What we saw

Homepage checked
https://gov.hr/
Homepage response
HTTP 200
TLS
TLSv1.3
Certificate
Entrust Limited, 376-day validity, expiring 2027-02-21
DNS operators
3 self-run or other nameserver domains
HSTS
max-age 365 days
Homepage HTML
18 KB, gzip
Images on homepage
10 (svg 7)

Limits: homepage only, one location, one moment. Header checks reflect the homepage response; other pages may differ.

All 31 checks

Select a gap for the method and fix. How each check works

Own gov.hr?

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: gov.hr. This profile covers configuration only.

Compare with other Government Services sites