ostrovok.ru

Readiness by lane

Green: ostrovok.ru. Thin bar: Hotels peer median.

Priority fixes for ostrovok.ru

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

1. Priority 1 · Accelerate

   HTTP/2 negotiated

   Observed: The TLS handshake selected http/1.1 instead of HTTP/2.

   Why it matters: HTTP/2 sends many files over one connection, which speeds up pages with lots of images, styles and scripts.

   What to do: Enable HTTP/2 on your CDN or server. Most CDNs do this by default.

   90% of Hotels peers do this. Limit: Certificate and protocol were observed from one vantage point; CDNs can present different certificates by region.

   Guide: CDN 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 no max-age, 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.

   On WordPress: Caching plugins or your host can set long browser cache lifetimes for theme and plugin assets.

   51% of Hotels peers do this.

   Guide: Browser Caching Guide for Website Owners

3. Priority 3 · Harden

   HSTS kept for at least a year

   Observed: Strict-Transport-Security was sent with a max-age of 30 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.

   36% of Hotels peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

4. Priority 4 · Enable

   Canonical URL declared

   Observed: The homepage did not declare a canonical URL.

   What to do: Add a self-referencing canonical link to every indexable page, using the final https:// URL.

   84% of Hotels peers do this.

   Guide: Canonical Tags: A Decision Guide for Duplicate URLs

What ostrovok.ru already does well

Practices fewer than half of Hotels peers use.

• Referrer-Policy setReferrer-Policy present.29% of peers
• No render-blocking scripts in <head>Head scripts load without blocking.38% of peers
• DMARC policy enforces quarantine or rejectDMARC policy p=reject.41% of peers

What we saw

Homepage checked

https://ostrovok.ru/

Homepage response

HTTP 200

TLS

TLSv1.3, http/1.1

Certificate

GlobalSign, 199-day validity, expiring 2027-02-21

Platform or framework

WordPress

DNS operators

1 self-run or other nameserver domain

HSTS

max-age 30 days

DMARC policy

p=reject

Homepage HTML

576 KB, gzip

Images on homepage

20

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

• mihmansho.com62
• online-reservations.com55
• pierreetvacances.com54
• spa.cz58
• yukoyuko.net51

Hotels readiness benchmark