maxmilhas.com.br

Readiness by lane

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

Priority fixes for maxmilhas.com.br

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

1. Priority 1 · Harden

   HSTS kept for at least a year

   Observed: Strict-Transport-Security was sent with a max-age of 180 days, below the one-year benchmark.

   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 Amazon CloudFront: Attach a response headers policy with Strict-Transport-Security to each distribution.

   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 5 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

   HTTP/3 advertised

   Observed: The homepage did not advertise HTTP/3 through an Alt-Svc header.

   What to do: Turn on HTTP/3 at your CDN. Browsers fall back to HTTP/2 automatically, so the risk is low.

   On Amazon CloudFront: Select HTTP/3 in the distribution's supported HTTP versions.

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

   Guide: CDN Guide for Website 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.

   On Next.js: Next.js documents nonce-based CSP with middleware.

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

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

What maxmilhas.com.br already does well

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

• Referrer-Policy setReferrer-Policy present.32% of peers
• No render-blocking scripts in <head>Head scripts load without blocking.44% 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.maxmilhas.com.br/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Amazon, 197-day validity, expiring 2027-04-25

CDN or edge

Amazon CloudFront

Platform or framework

Next.js

DNS operators

Cloudflare

HSTS

max-age 180 days

DMARC policy

p=reject

Homepage HTML

53 KB, gzip

Images on homepage

5

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

• aviasales.ru73
• esky.ro73
• logitravel.com73
• ncl.com73
• pelago.com73

Travel Bookings & Trip Planning readiness benchmark