britishairways.com

Readiness by lane

Green: britishairways.com. Thin bar: Airlines peer median.

Priority fixes for britishairways.com

Ordered by impact and by how common each practice is among peers.

1. Priority 1 · Harden

   HSTS kept for at least a year

   Observed: The homepage response did not include a Strict-Transport-Security header.

   Why it matters: HSTS tells browsers to use HTTPS for your host on every later visit, which removes the window where a first HTTP request can be intercepted.

   What to do: Send Strict-Transport-Security on HTTPS responses. Start with a short max-age (for example 300 seconds), confirm every subdomain works over HTTPS, then raise it in steps to 31536000. Add includeSubDomains only when all subdomains are HTTPS. HSTS preload is optional and hard to undo; hstspreload.org itself does not recommend it by default.

   60% of Airlines peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.

   Guide: HTTPS and TLS Guide for Website Owners

2. Priority 2 · Accelerate

   Static files cached for 30 days or more

   Observed: A same-site stylesheet or script was cacheable for 6 hours, short of the 30-day benchmark.

   What to do: Give versioned (fingerprinted) CSS, JavaScript, fonts and images Cache-Control: public, max-age=31536000, immutable, and change the file name whenever the content changes.

   40% of Airlines peers do this.

   Guide: Browser Caching Guide for Website Owners

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.

   84% of Airlines peers do this.

   Guide: Meta Titles and Descriptions That Match Search Intent

4. Priority 4 · Enable

   Canonical URL declared

   Observed: The homepage did not declare a canonical URL.

   What to do: Add a self-referencing canonical link to every indexable page, using the final https:// URL.

   60% of Airlines peers do this.

   Guide: Canonical Tags: A Decision Guide for Duplicate URLs

What britishairways.com already does well

Practices fewer than half of Airlines peers use.

• Nameservers spread across providersNameservers spread across more than one operator.19% of peers
• No render-blocking scripts in <head>Head scripts load without blocking.45% of peers

What we saw

Homepage checked

https://www.britishairways.com/

Homepage response

HTTP 200, after 1 redirect

TLS

TLSv1.3, HTTP/2

Certificate

GlobalSign, 396-day validity, expiring 2026-12-01

CDN or edge

Akamai

DNS operators

Akamai Edge DNS, plus 1 self-run or other nameserver domain

DMARC policy

p=reject

Homepage HTML

14 KB, gzip

Images on homepage

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

Compare with other Airlines sites

• aeroflot.ru52
• aircanada.com56
• ar-svx.ru55
• flyasiana.com55
• saudia.com54

Airlines readiness benchmark