jetsmart.com

Readiness by lane

Green: jetsmart.com. Thin bar: Airlines peer median.

Priority fixes for jetsmart.com

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

1. Priority 1 · Harden

   TLS 1.3 negotiated

   Observed: The TLS connection negotiated TLSv1.2.

   Why it matters: TLS 1.3 removes legacy cipher suites and completes the handshake in fewer round trips, so it is both safer and faster for new connections.

   What to do: Enable TLS 1.3 on your CDN or server. Keep TLS 1.2 available for older clients unless you have checked your audience.

   91% of Airlines 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 · Harden

   HSTS kept for at least a year

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

   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 Fastly: Add the header in VCL or a header rule as described in Fastly's HSTS guide.

   60% of Airlines peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

3. Priority 3 · Accelerate

   No render-blocking scripts in <head>

   Observed: The homepage <head> loaded 2 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.

   45% of Airlines peers do this.

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

4. Priority 4 · Accelerate

   Offscreen images lazy-loaded

   Observed: The homepage had 249 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.

   50% of Airlines peers do this.

   Guide: Lazy Loading Without Broken Pages

What jetsmart.com already does well

Practices fewer than half of Airlines peers use.

• Modern image formats in useWebP or AVIF images detected.31% of peers
• Static files cached for 30 days or moreLong-lived caching on static files.40% of peers
• Social preview image setog:image present.44% of peers

What we saw

Homepage checked

https://jetsmart.com/

Homepage response

HTTP 200, after 1 redirect

TLS

TLSv1.2, HTTP/2

Certificate

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

CDN or edge

Fastly

DNS operators

NS1

HSTS

max-age 0 days

DMARC policy

p=reject

Homepage HTML

841 KB, gzip

Images on homepage

249 (png 170, jpg 58, svg 21)

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

• flightconnections.com60
• flyfrontier.com61
• gatwickairport.com60
• royalairmaroc.com62
• volaris.com63

Airlines readiness benchmark