aramya.in

Readiness by lane

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

Priority fixes for aramya.in

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

1. Priority 1 · Accelerate

   HTML compressed

   Observed: The homepage HTML (363 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 Shopify: this setting is largely controlled by the platform. Check the platform's settings and documentation, or ask its support team whether it can be changed for your domain.

   97% of E-Commerce & Marketplaces 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

2. Priority 2 · Accelerate

   Modern image formats in use

   Observed: The homepage had 138 images and none used WebP or AVIF.

   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 Shopify: Shopify's image CDN can serve modern formats; follow Shopify's web performance guidance for themes.

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

   Guide: AVIF, WebP, JPEG, and PNG: Choose the Right Image Format

3. Priority 3 · 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 Azure Front Door/CDN: Add a response header action in a Front Door rule set.

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

   Guide: HTTPS and TLS Guide for Website Owners

4. Priority 4 · Harden

   DMARC policy enforces quarantine or reject

   Observed: The DMARC policy for aramya.in was p=none, which asks receivers to take no action on failing mail.

   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

What aramya.in already does well

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

• Referrer-Policy setReferrer-Policy present.20% of peers
• Content Security Policy presentContent-Security-Policy present.48% of peers

What we saw

Homepage checked

https://aramya.in/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

DigiCert, 184-day validity, expiring 2027-01-20

CDN or edge

Azure Front Door/CDN

Platform or framework

Shopify, Next.js

DNS operators

Azure DNS

DMARC policy

p=none

Homepage HTML

363 KB, uncompressed

Images on homepage

138 (svg 84, png 42, jpg 10, gif 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

Compare with other E-Commerce & Marketplaces sites

• agrieuro.com61
• altovalleavisos.com61
• appteka.store61
• askul.co.jp61
• autokarma.ro61

E-Commerce & Marketplaces readiness benchmark