Website readiness profile · Snapshot 23 October 2026
finnair.com
finnair.com's public homepage, certificate and DNS checked against 31 practices and compared with 91 Airlines sites.
- Readiness index
- 79/100
- Ahead of
- 87%
- Practices observed
- 20/29
- Popularity band
- Top 50K
Airlines median 63
of measured Airlines sites
2 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: finnair.com. Thin bar: Airlines peer median.
Enable
74/100
Peers 74
Harden
80/100
Peers 60
Accelerate
87/100
Peers 56
Recover
0/100
Peers 19
Priority fixes for finnair.com
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.
60% of Airlines peers do this. Limit: Based on the homepage HTML delivered to an automated client; scripts that run later were not executed.
Priority 2 · Enable
Social preview image set
Observed: The homepage had no og:image, so shared links may show without a preview image.
What to do: Add Open Graph tags, including og:image with a 1200 x 630 image.
44% of Airlines 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.
16% of Airlines peers do this.
Priority 4 · Harden
CAA records limit who can issue certificates
Observed: No CAA record was found for finnair.com, so any public certificate authority may issue for it.
What to do: Publish CAA records naming every CA you actually use, including the CAs your CDN uses for managed certificates. Add an iodef contact if you want reports.
9.9% of Airlines peers do this.
What finnair.com already does well
Practices fewer than half of Airlines peers use.
- Content Security Policy presentContent-Security-Policy present.32% of peers
- Reachable over IPv6IPv6 address published.35% of peers
- Certificate lifetime of 100 days or lessShort-lived 89-day certificate from Let's Encrypt, already inside the 2027 limit.39% of peers
What we saw
- Homepage checked
- https://www.finnair.com/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, HTTP/2
- Certificate
- Let's Encrypt, 89-day validity, expiring 2026-12-31
- CDN or edge
- Akamai
- Platform or framework
- Angular
- DNS operators
- Amazon Route 53
- HSTS
- max-age 365 days
- DMARC policy
- p=reject
- Homepage HTML
- 410 KB, gzip
- Images on homepage
- 1 (jpg 8)
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 9
Observed 20
- 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
- DMARC policy enforces quarantine or reject
- X-Content-Type-Options: nosniff
- Framing restricted
- Content Security Policy present
- HTTP/2 negotiated
- HTML compressed
- Static files cached for 30 days or more
- No render-blocking scripts in <head>
- robots.txt published
- XML sitemap discoverable
- Reachable over IPv6
- Meta description written
- Mobile viewport configured
- Page language declared
- At most one redirect to the homepage
Not measured 2
- Modern image formats in use
- Offscreen images lazy-loaded
Own finnair.com?
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: finnair.com. This profile covers configuration only.