trip.com

Readiness by lane

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

Priority fixes for trip.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.

   46% of Travel Bookings & Trip Planning 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 · Enable

   XML sitemap discoverable

   Observed: No sitemap was listed in robots.txt or found at /sitemap.xml.

   What to do: Generate an XML sitemap of canonical URLs, reference it in robots.txt and submit it in Google Search Console.

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

   Guide: XML Sitemap Guide: Include Only URLs You Stand Behind

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

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

   Guide: Lazy Loading Without Broken Pages

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.

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

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

What trip.com already does well

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

• HTTP/3 advertisedHTTP/3 advertised.33% of peers
• Reachable over IPv6IPv6 address published.36% of peers
• Modern image formats in useWebP or AVIF images detected.41% of peers

What we saw

Homepage checked

https://www.trip.com/

Homepage response

HTTP 200, after 1 redirect

TLS

TLSv1.3, HTTP/2

Certificate

DigiCert, 198-day validity, expiring 2027-04-03

DNS operators

Akamai Edge DNS

DMARC policy

p=reject

Homepage HTML

149 KB, gzip

Images on homepage

25 (png 18, svg 5, avif 1, jpg 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 Travel Bookings & Trip Planning sites

• airasia.com72
• pelago.com73
• reisereporter.de73
• traum-ferienwohnungen.de73
• yasisland.com73

Travel Bookings & Trip Planning readiness benchmark