mihmansho.com

Readiness by lane

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

Priority fixes for mihmansho.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 · Enable

   XML sitemap discoverable

   Observed: No sitemap was listed in robots.txt or found at /sitemap.xml.

   What to do: Generate an XML sitemap of canonical URLs, reference it in robots.txt and submit it in Google Search Console.

   85% of Hotels peers do this.

   Guide: XML Sitemap Guide: Include Only URLs You Stand Behind

3. Priority 3 · Harden

   HSTS kept for at least a year

   Observed: The homepage response did not include a Strict-Transport-Security header.

   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.

   Guide: HTTPS and TLS Guide for Website Owners

4. Priority 4 · Accelerate

   Modern image formats in use

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

What mihmansho.com already does well

Practices fewer than half of Hotels peers use.

• Content Security Policy presentContent-Security-Policy present.30% of peers
• No render-blocking scripts in <head>Head scripts load without blocking.38% of peers
• DMARC policy enforces quarantine or rejectDMARC policy p=quarantine.41% of peers

What we saw

Homepage checked

https://www.mihmansho.com/

Homepage response

HTTP 200

TLS

TLSv1.2, HTTP/2

Certificate

Asseco Data Systems S.A., 364-day validity, expiring 2026-12-30

DNS operators

1 self-run or other nameserver domain

DMARC policy

p=quarantine

Homepage HTML

150 KB, br

Images on homepage

61 (svg 4, 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
• online-reservations.com55
• spa.cz58
• wyndhamhotels.com63

Hotels readiness benchmark