Website readiness profile · Snapshot 23 October 2026
who.int
who.int's public homepage, certificate and DNS checked against 31 practices and compared with 613 Fitness & Health sites.
- Readiness index
- 87/100
- Ahead of
- 98%
- Practices observed
- 26/31
- Popularity band
- Top 50K
Fitness & Health median 67
of measured Fitness & Health sites
0 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: who.int. Thin bar: Fitness & Health peer median.
Enable
95/100
Peers 82
Harden
89/100
Peers 59
Accelerate
75/100
Peers 63
Recover
100/100
Peers 10
Priority fixes for who.int
Ordered by impact and by how common each practice is among peers.
Priority 1 · Accelerate
Modern image formats in use
Observed: The homepage had 25 images and none used WebP or AVIF.
Why it matters: WebP and AVIF are typically much smaller than JPEG or PNG at similar quality, and images are often the heaviest part of a page.
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 Cloudflare: Cloudflare Polish can convert images to WebP.
45% of Fitness & Health peers do this. Limit: Based on the homepage HTML delivered to an automated client; scripts that run later were not executed.
Guide: AVIF, WebP, JPEG, and PNG: Choose the Right Image Format
Priority 2 · Accelerate
Offscreen images lazy-loaded
Observed: The homepage had 25 images and none used loading="lazy".
What to do: Add loading="lazy" to images below the fold. Do not lazy-load the main hero image, because that delays the largest visible element.
68% of Fitness & Health peers do this.
Priority 3 · Harden
security.txt published
Observed: No valid /.well-known/security.txt with a Contact field was returned.
What to do: Publish /.well-known/security.txt with at least Contact and Expires fields, as RFC 9116 requires, and review it before it expires.
On Cloudflare: Cloudflare Security Center can serve a security.txt file for the zone.
7.3% of Fitness & Health peers do this.
Priority 4 · Harden
DNSSEC signed
Observed: No DS record was found for who.int at its parent zone, so its DNS answers are not DNSSEC-signed.
What to do: Enable DNSSEC at your DNS provider, then add the DS record at your registrar. Plan provider moves carefully: a stale DS record can make the domain fail to resolve.
On Cloudflare: Enable DNSSEC in DNS > Settings and add the DS record at the registrar.
9% of Fitness & Health peers do this.
Guide: Website Uptime Readiness: Prepare Before Traffic Arrives
What who.int already does well
Practices fewer than half of Fitness & Health peers use.
- Nameservers spread across providersNameservers spread across more than one operator.9.9% of peers
- CAA records limit who can issue certificatesCAA limits issuance to awstrust.com, digicert.com, godaddy.com and others.11% of peers
- HTTP/3 advertisedHTTP/3 advertised.29% of peers
What we saw
- Homepage checked
- https://www.who.int/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, HTTP/2
- Certificate
- Google Trust Services, 90-day validity, expiring 2026-12-27
- CDN or edge
- Cloudflare
- DNS operators
- 2 self-run or other nameserver domains
- HSTS
- max-age 365 days, preload
- DMARC policy
- p=reject
- Homepage HTML
- 135 KB, gzip
- Images on homepage
- 25 (jpg 18, png 6, svg 4)
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 5
Observed 26
- 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
- CAA records limit who can issue certificates
- DMARC policy enforces quarantine or reject
- X-Content-Type-Options: nosniff
- Framing restricted
- Content Security Policy present
- Referrer-Policy set
- HTTP/2 negotiated
- HTTP/3 advertised
- HTML compressed
- Static files cached for 30 days or more
- No render-blocking scripts in <head>
- robots.txt published
- XML sitemap discoverable
- Canonical URL declared
- Meta description written
- Mobile viewport configured
- Structured data present
- Social preview image set
- Page language declared
- At most one redirect to the homepage
- Nameservers spread across providers
Own who.int?
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: who.int. This profile covers configuration only.