Website readiness profile · Snapshot 23 October 2026
oziva.in
oziva.in's public homepage, certificate and DNS checked against 31 practices and compared with 5,718 E-Commerce & Marketplaces sites.
- Readiness index
- 85/100
- Ahead of
- 97%
- Practices observed
- 23/29
- Popularity band
- Top 50K
E-Commerce & Marketplaces median 71
of measured E-Commerce & Marketplaces sites
2 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: oziva.in. Thin bar: E-Commerce & Marketplaces peer median.
Enable
100/100
Peers 86
Harden
80/100
Peers 60
Accelerate
80/100
Peers 69
Recover
0/100
Peers 11
Priority fixes for oziva.in
Ordered by impact and by how common each practice is among peers.
Priority 1 · Accelerate
Modern image formats in use
Observed: The homepage had 5 images and none used WebP or AVIF.
Why it matters: WebP and AVIF are typically much smaller than JPEG or PNG at similar quality, and images are often the heaviest part of a page.
What to do: Serve WebP or AVIF with a JPEG or PNG fallback, either through an image CDN or by generating both formats at build time.
On Cloudflare: Cloudflare Polish can convert images to WebP.
47% of E-Commerce & Marketplaces peers do this. Limit: Based on the homepage HTML delivered to an automated client; scripts that run later were not executed.
Guide: AVIF, WebP, JPEG, and PNG: Choose the Right Image Format
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 Cloudflare: Add the header with a response header transform rule.
70% of E-Commerce & Marketplaces peers do this.
Priority 3 · Harden
security.txt published
Observed: No valid /.well-known/security.txt with a Contact field was returned.
What to do: Publish /.well-known/security.txt with at least Contact and Expires fields, as RFC 9116 requires, and review it before it expires.
On Cloudflare: Cloudflare Security Center can serve a security.txt file for the zone.
7.6% of E-Commerce & Marketplaces peers do this.
Priority 4 · Harden
DNSSEC signed
Observed: No DS record was found for oziva.in at its parent zone, so its DNS answers are not DNSSEC-signed.
What to do: Enable DNSSEC at your DNS provider, then add the DS record at your registrar. Plan provider moves carefully: a stale DS record can make the domain fail to resolve.
On Cloudflare: Enable DNSSEC in DNS > Settings and add the DS record at the registrar.
7.7% of E-Commerce & Marketplaces peers do this.
Guide: Website Uptime Readiness: Prepare Before Traffic Arrives
What oziva.in already does well
Practices fewer than half of E-Commerce & Marketplaces peers use.
- CAA records limit who can issue certificatesCAA limits issuance to digicert.com, globalsign.com, letsencrypt.org and others.16% of peers
- HSTS kept for at least a yearHSTS with a 365-day max-age.32% of peers
- DMARC policy enforces quarantine or rejectDMARC policy p=reject.39% of peers
What we saw
- Homepage checked
- https://www.oziva.in/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, HTTP/2
- Certificate
- Let's Encrypt, 89-day validity, expiring 2026-12-26
- CDN or edge
- Cloudflare, Shopify
- Platform or framework
- Shopify
- DNS operators
- GoDaddy DNS
- HSTS
- max-age 365 days
- DMARC policy
- p=reject
- Homepage HTML
- 78 KB, br
- Images on homepage
- 5 (svg 2, png 2, jpg 2)
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 6
Observed 23
- HTTP requests move to HTTPS
- HSTS kept for at least a year
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- Certificate lifetime of 100 days or less
- CAA records limit who can issue certificates
- DMARC policy enforces quarantine or reject
- X-Content-Type-Options: nosniff
- Content Security Policy present
- HTTP/2 negotiated
- HTTP/3 advertised
- HTML compressed
- No render-blocking scripts in <head>
- robots.txt published
- XML sitemap discoverable
- Reachable over IPv6
- Canonical URL declared
- Meta description written
- Mobile viewport configured
- Structured data present
- Social preview image set
- Page language declared
- At most one redirect to the homepage
Not measured 2
- Static files cached for 30 days or more
- Offscreen images lazy-loaded
Own oziva.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: oziva.in. This profile covers configuration only.