Aramya (aramya.in) — Website Traffic Estimation

Domain: aramya.in | Parent: DSLR Technologies Pvt. Ltd. | Analysis date: 2026-08-18 Methodology: User-provided SimilarWeb panel data (highest-priority source) cross-referenced against StatShow and WorthOfWeb. Business context from business-analysis.md (CrUX device split, ARR claim, catalog scale).


1. Sources Consulted

SourceStatusData ReturnedNotes
SimilarWeb (user-provided)✅ Used as primaryVisits, engagement, country splitServer IP is blocklisted by SimilarWeb's CloudFront (403/JS-challenge), so the user supplied the figures from their own browser. Treated as ground truth per skill priority rule.
StatShow⚠️ Unreliable — discarded"≈30 visits/month, $10 worth"Resolved to a Shopify/AWS CDN IP (52.85.193.119) and massively undercounts. This is a known StatShow limitation for Shopify-served stores (skill Pitfall #11). Ignored.
WorthOfWeb❌ BlockedNoneReturns a Cloudflare "Just a moment… / Enable JavaScript" challenge; no data extractable.

No corroborating third-party tool was reachable. All quantitative figures below come from the user-provided SimilarWeb data. StatShow's contradicting micro-number is explicitly excluded as a Shopify-CDN artifact.


2. Raw Numbers (SimilarWeb — user-provided)

MetricValue
Total Monthly Visits890,500
Pages / Visit3.23
Avg Visit Duration00:03:47 (227 sec)
Bounce Rate41.93%
Country RankNot available
CategoryNot available
Category RankNot available

Web Traffic by Country

CountryShareEst. Monthly Visits
India77.64%~691,400
United States11.95%~106,400
United Kingdom3.71%~33,000
Germany2.72%~24,200
Pakistan1.92%~17,100
Others2.07%~18,400

(Secondary demographic signal from business-analysis.md, also attributed to SimilarWeb: 56.87% female / 43.13% male — the male share likely includes gift-buyers. Device split per CrUX: 100% phone / 0% desktop — see §4.)


3. Aggregated Summary (Derived Metrics)

MetricValueHow derived
Monthly Visits890,500Direct (SimilarWeb)
Monthly Pageviews~2,876,300890,500 × 3.23 pages/visit
Daily Visits~29,700890,500 ÷ 30
Yearly Visits (run-rate)~10.69M890,500 × 12
Pages / Visit3.23Direct
Avg Session3m 47sDirect
Bounce Rate41.93%Direct
Traffic TierUpper-Medium (100K–1M band; near Large threshold of 1M)Skill tier reference

4. Key Insights

1. Traffic scale — a solid upper-Medium D2C storefront. 890,500 monthly visits places aramya.in in the upper end of the "Medium" tier (regional brands / popular e-commerce), within striking distance of "Large" (1M+). For a single-brand Indian ethnic-wear D2C site (not a marketplace), this is a high-traffic, well-funded challenger — consistent with the ₹80 Cr Series A (Feb 2026) and ~₹200 Cr+ ARR claim in business-analysis.md.

2. Engagement is strong for e-commerce.

  • 3.23 pages/visit — healthy browsing depth (category/collection exploration), above the ~2–4 "normal" band.
  • 3m 47s average session — well above typical e-commerce bounce-and-leave behaviour; suggests genuine catalog engagement (2,183 SKUs / 172 collections give shoppers room to browse).
  • 41.93% bounce rate — low/good. Under ~45% bounce is a positive signal for a product-led store; visitors land and continue.

None of these point to a thin or parked site (contrast StatShow's bogus ~30-visit reading, which is a Shopify-CDN artifact).

3. Audience is overwhelmingly India + mobile.

  • India = 77.64% of visits, matching the brand's pan-India D2C model (free delivery >₹699, COD).
  • The 100% phone device split (CrUX, business-analysis.md §5a) aligns perfectly with an India-heavy, mobile-commerce audience. Desktop is a non-factor — the funnel must be mobile-first.
  • US 11.95% / UK 3.71% / Germany 2.72% is a classic Indian diaspora pattern. Note from business-analysis.md: aramya.in shows no international shipping signal — so this overseas traffic is browsing/NRI interest, not fulfilled cross-border orders. A diaspora/international-shipping launch is a plausible upside lever (flagged as a catalog gap in the business analysis).
  • Pakistan 1.92% reflects broader South-Asian ethnic-wear interest.

4. Traffic vs. claimed revenue — D2C web is one of several channels. The brand claims ₹200 Cr+ ARR. A simple sanity cross-check:

  • 890,500 monthly visits × ~2% D2C conversion × ~₹650 AOV ≈ ₹1.16 Cr/month D2C revenue (~7% of claimed ARR).

That gap is expected and not a contradiction: Aramya is omni-channel — 13 profitable Bengaluru COCO stores, Amazon/Flipkart/Myntra marketplaces, a mobile app, and FOCO franchise all contribute revenue outside the D2C website. The web traffic figure is therefore consistent with a multi-channel brand where the website is a top-of-funnel + repeat-purchase channel rather than the sole revenue engine. (If D2C were the entire business, the ARR claim would be unsupported by traffic — but it isn't the entire business.)

5. "Worth / ad-revenue" estimates are not applicable. Standard traffic-tool "website worth" and "ad revenue" numbers assume an ad-monetized site. Aramya is a product-selling e-commerce store, so any such figure would be meaningless (skill Pitfall #4). No worth/revenue estimate is reported here.


5. Caveats

  • Single-source dependency. SimilarWeb is the only usable quantitative source. StatShow (discarded — Shopify-CDN undercount) and WorthOfWeb (Cloudflare-blocked) could not corroborate. Treat the absolute visit count as a panel-based estimate, not audited truth.
  • User-provided snapshot. Figures were hand-captured by the user from their browser; no date stamp was supplied. SimilarWeb's panels refresh continuously — re-verify before long-range planning.
  • Country/Category ranks missing. SimilarWeb returned "data not available" for Country Rank, Category, and Category Rank, so rank-based competitive positioning isn't computable from this data.
  • Derived pageviews are inferred. Monthly pageviews (~2.88M) are computed from visits × pages/visit; they inherit any error in the underlying visit estimate.
  • Diaspora traffic is non-converting (currently). Overseas visits cannot yet transact (no international shipping), so US/UK/DE numbers represent demand, not revenue.
  • For precise first-party truth, GA4 integration would replace these panel estimates with actual server-side visits and conversion data — recommended once client analytics access is available.

Confidence: [Medium] — primary figures are user-provided SimilarWeb panel data (treated as authoritative per skill priority rule); cross-reference tools were unreachable/unreliable. No figures were fabricated; the StatShow micro-count was explicitly excluded as a known Shopify-CDN artifact.