myvi.in

Readiness by lane

Green: myvi.in. Thin bar: Telecommunications & Internet peer median.

Priority fixes for myvi.in

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.

   72% of Telecommunications & Internet 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

   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.

   37% of Telecommunications & Internet peers do this.

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

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

   48% of Telecommunications & Internet peers do this.

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

4. Priority 4 · Harden

   CAA records limit who can issue certificates

   Observed: No CAA record was found for myvi.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 Telecommunications & Internet peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

What myvi.in already does well

Practices fewer than half of Telecommunications & Internet peers use.

• Referrer-Policy setReferrer-Policy present.33% of peers
• Static files cached for 30 days or moreLong-lived caching on static files.41% of peers

What we saw

Homepage checked

https://www.myvi.in/

Homepage response

HTTP 200

TLS

TLSv1.3

Certificate

DigiCert, 198-day validity, expiring 2027-01-17

Platform or framework

Next.js

DNS operators

1 self-run or other nameserver domain

HSTS

max-age 730 days, includeSubDomains, preload

DMARC policy

p=reject

Homepage HTML

223 KB, gzip

Images on homepage

64 (webp 50, png 13, svg 11)

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 Telecommunications & Internet sites

• bell.ca74
• claro.com.ar74
• o2online.de74
• straighttalk.com75
• three.co.uk74

Telecommunications & Internet readiness benchmark