sravni.ru

Readiness by lane

Green: sravni.ru. Thin bar: Insurance & Financial Planning peer median.

Priority fixes for sravni.ru

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

1. Priority 1 · Enable

   XML sitemap discoverable

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

   Why it matters: A sitemap helps search engines find new and updated pages, especially on large or frequently updated sites.

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

   81% of Insurance & Financial Planning peers do this. Limit: Only the standard location was requested, once, at the time of the check.

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

2. Priority 2 · Harden

   Framing restricted

   Observed: The homepage did not send frame-ancestors or X-Frame-Options, so other sites may frame it.

   What to do: Send Content-Security-Policy: frame-ancestors 'self' (or a list of trusted origins). X-Frame-Options: SAMEORIGIN covers older browsers.

   On Next.js: Add it in next.config.js headers().

   69% of Insurance & Financial Planning peers do this.

   Guide: A Practical Website Health Check for Owners

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

   On Next.js: Use the next/script component with an appropriate loading strategy.

   43% of Insurance & Financial Planning peers do this.

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

4. Priority 4 · Harden

   Content Security Policy present

   Observed: The homepage response did not include a Content-Security-Policy header.

   What to do: Start with Content-Security-Policy-Report-Only to see what would break, tighten the policy over a few weeks, then enforce it.

   On Next.js: Next.js documents nonce-based CSP with middleware.

   51% of Insurance & Financial Planning peers do this.

   Guide: Payment Security and PCI DSS: What Website Owners Need to Know

What sravni.ru already does well

Practices fewer than half of Insurance & Financial Planning peers use.

• security.txt publishedsecurity.txt with a contact found.9.9% of peers
• Modern image formats in useWebP or AVIF images detected.43% of peers

What we saw

Homepage checked

https://www.sravni.ru/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

GlobalSign, 396-day validity, expiring 2027-01-02

Platform or framework

Next.js

DNS operators

1 self-run or other nameserver domain

HSTS

max-age 365 days, includeSubDomains

DMARC policy

p=quarantine

Homepage HTML

612 KB, gzip

Images on homepage

187 (png 223, svg 123, jpg 20, webp 3)

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 Insurance & Financial Planning sites

• anthem.com72
• cigna.com70
• harel-group.co.il69
• mijnpensioenoverzicht.nl71
• uhc.com72

Insurance & Financial Planning readiness benchmark