kiwi.com

Readiness by lane

Green: kiwi.com. Thin bar: Travel Bookings & Trip Planning peer median.

Priority fixes for kiwi.com

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

1. Priority 1 · Harden

   Certificate has more than 14 days left

   Observed: The certificate from Certainly was due to expire on 2026-11-07 (14 days after the check).

   Why it matters: An expired certificate makes browsers show a full-page warning. Renewing well ahead of expiry leaves time to fix a failed renewal.

   What to do: Automate renewal with ACME (for example Let's Encrypt or your CDN's managed certificates) and add a renewal review to your release calendar so any certificate inside 21 days of expiry gets attention.

   99% of Travel Bookings & Trip Planning peers do this. Limit: Certificate and protocol were observed from one vantage point; CDNs can present different certificates by region.

   Guide: HTTPS and TLS Guide for Website Owners

2. Priority 2 · Accelerate

   Modern image formats in use

   Observed: The homepage had 52 images and none used WebP or AVIF.

   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 Next.js: The next/image component serves optimized formats automatically.

   41% of Travel Bookings & Trip Planning peers do this.

   Guide: AVIF, WebP, JPEG, and PNG: Choose the Right Image Format

3. Priority 3 · Accelerate

   No render-blocking scripts in <head>

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

   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.

   On Next.js: Use the next/script component with an appropriate loading strategy.

   44% of Travel Bookings & Trip Planning peers do this.

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

4. Priority 4 · Harden

   CAA records limit who can issue certificates

   Observed: No CAA record was found for kiwi.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.

   10% of Travel Bookings & Trip Planning peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

What kiwi.com already does well

Practices fewer than half of Travel Bookings & Trip Planning peers use.

• security.txt publishedsecurity.txt with a contact found.17% of peers
• Content Security Policy presentContent-Security-Policy present.30% of peers
• HTTP/3 advertisedHTTP/3 advertised.33% of peers

What we saw

Homepage checked

https://www.kiwi.com/

Homepage response

HTTP 200, after 1 redirect

TLS

TLSv1.3, HTTP/2

Certificate

Certainly, 29-day validity, expiring 2026-11-07

CDN or edge

Fastly, Google edge

Platform or framework

Next.js

DNS operators

Google Cloud DNS

HSTS

max-age 365 days, includeSubDomains

DMARC policy

p=reject

Homepage HTML

1,162 KB, gzip

Images on homepage

52 (png 6, svg 3, jpg 2)

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 Travel Bookings & Trip Planning sites

• flytoday.ir77
• holidayextras.com77
• japan.travel77
• reisenaktuell.com77
• skyscanner.com.br77

Travel Bookings & Trip Planning readiness benchmark