in.canon

Readiness by lane

Green: in.canon. Thin bar: E-Commerce & Marketplaces peer median.

Priority fixes for in.canon

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

1. Priority 1 · Accelerate

   Modern image formats in use

   Observed: The homepage had 15 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.

   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

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

   85% of E-Commerce & Marketplaces peers do this.

   Guide: Canonical Tags: A Decision Guide for Duplicate URLs

3. Priority 3 · Harden

   DMARC policy enforces quarantine or reject

   Observed: No DMARC record was found at _dmarc.in.canon.

   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.

   39% of E-Commerce & Marketplaces peers do this.

   Guide: A Practical Website Health Check for Owners

4. Priority 4 · Accelerate

   Offscreen images lazy-loaded

   Observed: The homepage had 15 images and none used loading="lazy".

   What to do: Add loading="lazy" to images below the fold. Do not lazy-load the main hero image, because that delays the largest visible element.

   72% of E-Commerce & Marketplaces peers do this.

   Guide: Lazy Loading Without Broken Pages

What in.canon already does well

Practices fewer than half of E-Commerce & Marketplaces peers use.

• Referrer-Policy setReferrer-Policy present.20% of peers
• HSTS kept for at least a yearHSTS with a 365-day max-age.32% of peers
• No render-blocking scripts in <head>Head scripts load without blocking.44% of peers

What we saw

Homepage checked

https://in.canon/

Homepage response

HTTP 200, after 3 redirects

TLS

TLSv1.3, HTTP/2

Certificate

Amazon, 394-day validity, expiring 2027-03-05

CDN or edge

Amazon CloudFront

DNS operators

Amazon Route 53

HSTS

max-age 365 days

Homepage HTML

154 KB, gzip

Images on homepage

15 (png 15)

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 E-Commerce & Marketplaces sites

• hungmobile.vn65
• idmarket.com65
• ikman.lk65
• intimissimi.com65
• jomashop.com65

E-Commerce & Marketplaces readiness benchmark