service-public.gouv.fr

Readiness by lane

Green: service-public.gouv.fr. Thin bar: Government Services peer median.

Priority fixes for service-public.gouv.fr

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

   DMARC policy enforces quarantine or reject

   Observed: No DMARC record was found at _dmarc.service-public.gouv.fr.

   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.

   Guide: A Practical Website Health Check for Owners

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

   39% of Government Services peers do this.

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

4. Priority 4 · Accelerate

   Modern image formats in use

   Observed: The homepage had 16 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.

   15% of Government Services peers do this.

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

What service-public.gouv.fr 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 certigna.com, globalsign.com, letsencrypt.org and others.17% of peers
• Static files cached for 30 days or moreLong-lived caching on static files.30% of peers

What we saw

Homepage checked

https://www.service-public.gouv.fr/

Homepage response

HTTP 200

TLS

TLSv1.3

Certificate

Sectigo, 365-day validity, expiring 2027-03-04

DNS operators

1 self-run or other nameserver domain

HSTS

max-age 730 days, includeSubDomains, preload

Homepage HTML

52 KB, gzip

Images on homepage

16 (svg 12)

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

• fcm.org.co69
• myscheme.gov.in70
• oregon.gov70
• sarkaricsc.com70
• woah.org70

Government Services readiness benchmark