Website readiness profile · Snapshot 23 October 2026
evozen.fr
evozen.fr's public homepage, certificate and DNS checked against 31 practices and compared with 343 Uncategorized sites.
- Readiness index
- 77/100
- Ahead of
- 85%
- Practices observed
- 21/31
- Popularity band
- Top 50K
Uncategorized median 62
of measured Uncategorized sites
0 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: evozen.fr. Thin bar: Uncategorized peer median.
Enable
85/100
Peers 80
Harden
68/100
Peers 54
Accelerate
90/100
Peers 58
Recover
0/100
Peers 12
Priority fixes for evozen.fr
Ordered by impact and by how common each practice is among peers.
Priority 1 · Enable
Canonical URL declared
Observed: The homepage did not declare a canonical URL.
Why it matters: A canonical link tells search engines which URL to show when the same page is reachable at several addresses.
What to do: Add a self-referencing canonical link to every indexable page, using the final https:// URL.
73% of Uncategorized peers do this. Limit: Based on the homepage HTML delivered to an automated client; scripts that run later were not executed.
Priority 2 · Harden
Framing restricted
Observed: The homepage did not send frame-ancestors or X-Frame-Options, so other sites may frame it.
What to do: Send Content-Security-Policy: frame-ancestors 'self' (or a list of trusted origins). X-Frame-Options: SAMEORIGIN covers older browsers.
43% of Uncategorized peers do this.
Priority 3 · Accelerate
HTTP/3 advertised
Observed: The homepage did not advertise HTTP/3 through an Alt-Svc header.
What to do: Turn on HTTP/3 at your CDN. Browsers fall back to HTTP/2 automatically, so the risk is low.
33% of Uncategorized peers do this.
Priority 4 · Harden
Content Security Policy present
Observed: The homepage response did not include a Content-Security-Policy header.
What to do: Start with Content-Security-Policy-Report-Only to see what would break, tighten the policy over a few weeks, then enforce it.
24% of Uncategorized peers do this.
Guide: Payment Security and PCI DSS: What Website Owners Need to Know
What evozen.fr already does well
Practices fewer than half of Uncategorized peers use.
- DNSSEC signedDNSSEC delegation (DS record) present.9.3% of peers
- Modern image formats in useWebP or AVIF images detected.33% of peers
- HSTS kept for at least a yearHSTS with a 730-day max-age.34% of peers
What we saw
- Homepage checked
- https://www.evozen.fr/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, HTTP/2
- Certificate
- Let's Encrypt, 89-day validity, expiring 2027-01-18
- Platform or framework
- WordPress
- DNS operators
- OVHcloud DNS
- HSTS
- max-age 730 days
- DMARC policy
- p=quarantine
- Homepage HTML
- 87 KB, br
- Images on homepage
- 23 (svg 14, jpg 6, png 2, webp 1)
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
Not observed 10
Observed 21
- HTTP requests move to HTTPS
- HSTS kept for at least a year
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- Certificate lifetime of 100 days or less
- DNSSEC signed
- DMARC policy enforces quarantine or reject
- HTTP/2 negotiated
- HTML compressed
- Static files cached for 30 days or more
- Modern image formats in use
- Offscreen images lazy-loaded
- No render-blocking scripts in <head>
- robots.txt published
- XML sitemap discoverable
- Meta description written
- Mobile viewport configured
- Structured data present
- Social preview image set
- Page language declared
- At most one redirect to the homepage
Own evozen.fr?
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: evozen.fr. This profile covers configuration only.