Website readiness profile · Snapshot 23 October 2026
orientalinsurance.org.in
orientalinsurance.org.in's public homepage, certificate and DNS checked against 31 practices and compared with 203 Insurance & Financial Planning sites.
- Readiness index
- 55/100
- Ahead of
- 18%
- Practices observed
- 14/29
- Popularity band
- Top 50K
Insurance & Financial Planning median 69
of measured Insurance & Financial Planning sites
2 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: orientalinsurance.org.in. Thin bar: Insurance & Financial Planning peer median.
Enable
82/100
Peers 81
Harden
38/100
Peers 64
Accelerate
60/100
Peers 60
Recover
0/100
Peers 19
Priority fixes for orientalinsurance.org.in
Ordered by impact and by how common each practice is among peers.
Priority 1 · Accelerate
HTML compressed
Observed: The homepage HTML (8 KB) was delivered without gzip, Brotli or zstd compression.
Why it matters: Compression usually shrinks HTML several times over, so the first bytes of the page arrive sooner on slow connections.
What to do: Enable Brotli or gzip for text responses (HTML, CSS, JavaScript, JSON, SVG) at the CDN or origin.
On Amazon CloudFront: Enable Compress objects automatically on the cache behaviour.
89% of Insurance & Financial Planning peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.
Guide: How to Set a Website Performance Budget That Teams Can Keep
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 Amazon CloudFront: Attach a response headers policy with Strict-Transport-Security to each distribution.
60% of Insurance & Financial Planning peers do this.
Priority 3 · Harden
DMARC policy enforces quarantine or reject
Observed: No DMARC record was found at _dmarc.orientalinsurance.org.in.
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.
69% of Insurance & Financial Planning peers do this.
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.
82% of Insurance & Financial Planning peers do this.
What orientalinsurance.org.in already does well
Practices fewer than half of Insurance & Financial Planning peers use.
- Reachable over IPv6IPv6 address published.26% of peers
- No render-blocking scripts in <head>Head scripts load without blocking.43% of peers
What we saw
- Homepage checked
- https://orientalinsurance.org.in/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, HTTP/2
- Certificate
- Amazon, 197-day validity, expiring 2027-03-07
- CDN or edge
- Amazon CloudFront
- DNS operators
- Amazon Route 53
- Homepage HTML
- 8 KB, uncompressed
- Images on homepage
- 0
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
Not observed 15
- HSTS kept for at least a year
- Certificate lifetime of 100 days or less
- CAA records limit who can issue certificates
- DNSSEC signed
- security.txt published
- DMARC policy enforces quarantine or reject
- X-Content-Type-Options: nosniff
- Framing restricted
- Content Security Policy present
- Referrer-Policy set
- HTTP/3 advertised
- HTML compressed
- Canonical URL declared
- Social preview image set
- Nameservers spread across providers
Observed 14
- HTTP requests move to HTTPS
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- HTTP/2 negotiated
- Static files cached for 30 days or more
- No render-blocking scripts in <head>
- robots.txt published
- XML sitemap discoverable
- Reachable over IPv6
- Meta description written
- Mobile viewport configured
- Structured data present
- Page language declared
- At most one redirect to the homepage
Not measured 2
- Modern image formats in use
- Offscreen images lazy-loaded
Own orientalinsurance.org.in?
Re-run the checks after a change, or verify the site in a free workspace to save reports with history, compare against similar sites and competitors, and track a private action plan. What owners get.
Live status for this site: Status Is Down: orientalinsurance.org.in. This profile covers configuration only.