pierreetvacances.com

Readiness by lane

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

Priority fixes for pierreetvacances.com

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

1. Priority 1 · Harden

   HTTP requests move to HTTPS

   Observed: A request to http://www.pierreetvacances.com/ was not redirected to HTTPS.

   Why it matters: Visitors who type the address or follow an old link start on unencrypted HTTP. A redirect moves them to the encrypted site before any cookies or form data are sent.

   What to do: Add a permanent (301 or 308) redirect from every http:// URL to the same https:// URL at your CDN, load balancer or web server.

   93% of Hotels peers do this. Limit: Measured for the homepage only, from one location, at the time of the check.

   Guide: HTTPS and TLS Guide for Website Owners

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

   On Next.js: Add the header in the headers() option of next.config.js for all routes.

   36% of Hotels peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

3. Priority 3 · Harden

   DMARC policy enforces quarantine or reject

   Observed: The DMARC policy for pierreetvacances.com was p=none, which asks receivers to take no action on failing mail.

   What to do: Publish DMARC with p=none and a reporting address first, fix any legitimate senders that fail SPF or DKIM alignment, then move to quarantine and finally reject.

   41% of Hotels peers do this.

   Guide: A Practical Website Health Check for Owners

4. Priority 4 · Accelerate

   Modern image formats in use

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

   37% of Hotels peers do this.

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

What pierreetvacances.com already does well

Practices fewer than half of Hotels peers use.

• Referrer-Policy setReferrer-Policy present.29% of peers

What we saw

Homepage checked

https://www.pierreetvacances.com/

Homepage response

HTTP 200, after 1 redirect

TLS

TLSv1.3, HTTP/2

Certificate

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

CDN or edge

Akamai

Platform or framework

Next.js

DNS operators

Amazon Route 53

DMARC policy

p=none

Homepage HTML

391 KB, gzip

Images on homepage

42 (svg 21, jpg 20, png 7)

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

• online-reservations.com55
• ostrovok.ru55
• princehotels.co.jp49
• spa.cz58
• yukoyuko.net51

Hotels readiness benchmark