starhealth.in

Readiness by lane

Green: starhealth.in. Thin bar: Insurance & Financial Planning peer median.

Priority fixes for starhealth.in

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

1. Priority 1 · Accelerate

   Static files cached for 30 days or more

   Observed: A same-site stylesheet or script was cacheable for 22 days, short of the 30-day benchmark.

   Why it matters: Returning visitors and later page views reuse cached files instead of downloading them again.

   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.

   51% of Insurance & Financial Planning peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.

   Guide: Browser Caching Guide for Website Owners

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

3. Priority 3 · Harden

   X-Content-Type-Options: nosniff

   Observed: The homepage response did not include X-Content-Type-Options: nosniff.

   What to do: Send X-Content-Type-Options: nosniff on all responses and make sure each file is served with the correct Content-Type.

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

   66% of Insurance & Financial Planning peers do this.

   Guide: A Practical Website Health Check for Owners

4. Priority 4 · Harden

   CAA records limit who can issue certificates

   Observed: No CAA record was found for starhealth.in, so any public certificate authority may issue for it.

   What to do: Publish CAA records naming every CA you actually use, including the CAs your CDN uses for managed certificates. Add an iodef contact if you want reports.

   15% of Insurance & Financial Planning peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

What starhealth.in already does well

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

• HTTP/3 advertisedHTTP/3 advertised.18% of peers
• Reachable over IPv6IPv6 address published.26% of peers
• Modern image formats in useWebP or AVIF images detected.43% of peers

What we saw

Homepage checked

https://www.starhealth.in/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

DigiCert, 198-day validity, expiring 2027-05-08

CDN or edge

Akamai

Platform or framework

Next.js

DNS operators

1 self-run or other nameserver domain

HSTS

max-age 365 days, includeSubDomains, preload

DMARC policy

p=reject

Homepage HTML

900 KB, gzip

Images on homepage

256 (svg 292, webp 31)

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

• acko.com76
• axismaxlife.com76
• tameeni.com77
• tk.de76
• utua.com75

Insurance & Financial Planning readiness benchmark