virginvoyages.com

Readiness by lane

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

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

   On Next.js: Add the header in the headers() option of next.config.js for all routes.

   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 · Accelerate

   Modern image formats in use

   Observed: The homepage had 92 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 4 external scripts 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

   X-Content-Type-Options: nosniff

   Observed: The homepage response did not include X-Content-Type-Options: nosniff.

   What to do: Send X-Content-Type-Options: nosniff on all responses and make sure each file is served with the correct Content-Type.

   On Next.js: Add it in next.config.js headers().

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

   Guide: A Practical Website Health Check for Owners

What virginvoyages.com already does well

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

• Content Security Policy presentContent-Security-Policy present.30% of peers
• HTTP/3 advertisedHTTP/3 advertised.33% of peers
• Static files cached for 30 days or moreLong-lived caching on static files.49% of peers

What we saw

Homepage checked

https://www.virginvoyages.com/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

GoDaddy, 198-day validity, expiring 2026-12-16

CDN or edge

Google edge

Platform or framework

Next.js

DNS operators

Amazon Route 53

DMARC policy

p=reject

Homepage HTML

1,111 KB, gzip

Images on homepage

92 (png 116, svg 93, jpg 53)

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

• adr.it71
• itaka.pl72
• prontotour.com72
• royalbrothers.com72
• workaway.info72

Travel Bookings & Trip Planning readiness benchmark