flysafair.co.za

Readiness by lane

Green: flysafair.co.za. Thin bar: Airlines peer median.

Priority fixes for flysafair.co.za

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

1. Priority 1 · Accelerate

   No render-blocking scripts in <head>

   Observed: The homepage <head> loaded 1 external script without async or defer.

   Why it matters: A plain <script src> in the head stops the browser from showing anything until that file has downloaded and run.

   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.

   45% of Airlines peers do this. Limit: Based on the homepage HTML delivered to an automated client; scripts that run later were not executed.

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

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

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

   On Cloudflare: Add the header with a response header transform rule.

   60% of Airlines peers do this.

   Guide: A Practical Website Health Check for Owners

4. 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.

   32% of Airlines peers do this.

   Guide: Payment Security and PCI DSS: What Website Owners Need to Know

What flysafair.co.za already does well

Practices fewer than half of Airlines peers use.

• HTTP/3 advertisedHTTP/3 advertised.16% of peers
• Reachable over IPv6IPv6 address published.35% of peers
• Certificate lifetime of 100 days or lessShort-lived 90-day certificate from Google Trust Services, already inside the 2027 limit.39% of peers

What we saw

Homepage checked

https://www.flysafair.co.za/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Google Trust Services, 90-day validity, expiring 2026-12-17

CDN or edge

Cloudflare, Amazon CloudFront

DNS operators

Cloudflare

HSTS

max-age 365 days, includeSubDomains, preload

DMARC policy

p=reject

Homepage HTML

7 KB, gzip

Images on homepage

0

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

• airtrip.jp69
• flypobeda.ru75
• ghasedak24.com74
• malaysiaairlines.com73
• partocrs.ir71

Airlines readiness benchmark