oesterreich.gv.at

Readiness by lane

Green: oesterreich.gv.at. Thin bar: Government Services peer median.

Priority fixes for oesterreich.gv.at

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

   No render-blocking scripts in <head>

   Observed: The homepage <head> loaded 1 external script 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 Next.js: Use the next/script component with an appropriate loading strategy.

   39% of Government Services peers do this.

   Guide: Control Third-Party Scripts Before They Control Your Page

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

4. Priority 4 · Accelerate

   Modern image formats in use

   Observed: The homepage had 13 images and none used WebP or AVIF.

   What to do: Serve WebP or AVIF with a JPEG or PNG fallback, either through an image CDN or by generating both formats at build time.

   On Next.js: The next/image component serves optimized formats automatically.

   15% of Government Services peers do this.

   Guide: AVIF, WebP, JPEG, and PNG: Choose the Right Image Format

What oesterreich.gv.at already does well

Practices fewer than half of Government Services peers use.

• security.txt publishedsecurity.txt with a contact found.8% of peers
• CAA records limit who can issue certificatesCAA limits issuance to digicert.com, harica.gr, letsencrypt.org.17% of peers
• Nameservers spread across providersNameservers spread across more than one operator.25% of peers

What we saw

Homepage checked

https://www.oesterreich.gv.at/

Homepage response

HTTP 200, after 1 redirect

TLS

TLSv1.3, http/1.1

Certificate

Hellenic Academic and Research Institutions CA, 198-day validity, expiring 2027-02-07

Platform or framework

Next.js

DNS operators

2 self-run or other nameserver domains

HSTS

max-age 365 days, includeSubDomains

DMARC policy

p=quarantine

Homepage HTML

212 KB, gzip

Images on homepage

13 (svg 2)

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

• gov-online.go.jp73
• migrationsverket.se73
• mom.gov.sg73
• ontario.ca73
• pishkhan24.com73

Government Services readiness benchmark