oyorooms.com

Readiness by lane

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

Priority fixes for oyorooms.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: Strict-Transport-Security was sent with a max-age of 182 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.

   36% of Hotels 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 63 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

3. Priority 3 · Accelerate

   Offscreen images lazy-loaded

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

   58% of Hotels peers do this.

   Guide: Lazy Loading Without Broken Pages

4. Priority 4 · Harden

   Certificate lifetime of 100 days or less

   Observed: The certificate from DigiCert Inc had a 198-day validity period, longer than the 100-day maximum that applies from March 2027.

   What to do: Move to automated issuance and renewal now, while you still have time to test it.

   52% of Hotels peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

What oyorooms.com already does well

Practices fewer than half of Hotels peers use.

• CAA records limit who can issue certificatesCAA limits issuance to amazon.com, amazonaws.com, digicert.com and others.15% of peers
• Content Security Policy presentContent-Security-Policy present.30% of peers
• Reachable over IPv6IPv6 address published.33% of peers

What we saw

Homepage checked

https://www.oyorooms.com/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

DigiCert, 198-day validity, expiring 2027-02-17

DNS operators

Akamai Edge DNS

HSTS

max-age 182 days, includeSubDomains

DMARC policy

p=quarantine

Homepage HTML

401 KB, gzip

Images on homepage

63 (png 63)

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

• greatwolf.com75
• jajiga.com76
• lekkeslaap.co.za75
• sandaya.fr79
• toyoko-inn.com78

Hotels readiness benchmark