wyndhamhotels.com

Readiness by lane

Green: wyndhamhotels.com. Thin bar: Hotels peer median.

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

   89% of Hotels 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

   Static files cached for 30 days or more

   Observed: A same-site stylesheet or script was cacheable for 0 seconds, short of the 30-day benchmark.

   What to do: Give versioned (fingerprinted) CSS, JavaScript, fonts and images Cache-Control: public, max-age=31536000, immutable, and change the file name whenever the content changes.

   51% of Hotels peers do this.

   Guide: Browser Caching Guide for Website Owners

3. Priority 3 · Accelerate

   Modern image formats in use

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

   37% of Hotels peers do this.

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

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

   38% of Hotels peers do this.

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

What wyndhamhotels.com already does well

Practices fewer than half of Hotels peers use.

• HSTS kept for at least a yearHSTS with a 365-day max-age covering subdomains.36% of peers
• DMARC policy enforces quarantine or rejectDMARC policy p=reject.41% of peers

What we saw

Homepage checked

https://www.wyndhamhotels.com/

Homepage response

HTTP 200

TLS

TLSv1.2, HTTP/2

Certificate

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

CDN or edge

Akamai

Platform or framework

Adobe Experience Manager

DNS operators

Akamai Edge DNS

HSTS

max-age 365 days, includeSubDomains, preload

DMARC policy

p=reject

Homepage HTML

668 KB, gzip

Images on homepage

105 (svg 55, png 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 Hotels sites

• capfun.com62
• dormy-hotels.com62
• eurostarshotels.com63
• isrotel.co.il63
• travelodge.co.uk63

Hotels readiness benchmark