Meena Bazaar
Audit Overview
Your store's untapped revenue potential — and how to unlock it
Why We Created This Audit
We analyzed https://meenabazaar.com the same way we've audited 350+ e-commerce stores — looking for the specific gaps between your current experience and what top-performing Fashion & Apparel stores deliver. Every finding in this report is a revenue opportunity backed by industry data and competitive benchmarks.
What We Analyzed
- UX & Conversion Design findings
- Performance & Speedvs 3 competitors
- Technology & App StackPlatform + 5 apps
- Industry BenchmarksFashion & Apparel
Pages Analyzed
- Homepage findings
- Collection Pages findings
- Product Pages (PDP) findings
- Cart & Checkout findings
This audit was prepared by Growisto — a CRO-led Website development team behind 167% conversion growth for Atomberg, 46% CR lift for TyresNmore, and 350+ e-commerce projects.
Performance & Technology
Speed benchmarks, Core Web Vitals, and technology assessment for Meena Bazaar
Mobile PageSpeed Score
Meena Bazaar's 31/100 mobile Lighthouse score reflects heavy main-thread blocking (TBT ~900ms) and slow visual delivery — although real-user (CrUX) field data shows the live experience is actually competitive on LCP, INP, and CLS.
Competitive Comparison
Benchmarked against 3 leading Fashion & Apparel stores in your market
| Store | Mobile Score | Desktop Score | Mobile LCP | Mobile CLS | Mobile TBT |
|---|---|---|---|---|---|
| Meena Bazaar | 31 | 21 | 3.1s | 0.00 | 900ms |
| Biba | 28 | 55 | 2.3s | 0.00 | 450ms |
| W for Woman | 26 | 20 | 5.0s | 0.00 | 148ms |
| Libas | 46 | 35 | 5.2s | 0.081 | 1094ms |
⚠ Note: Biba, W for Woman score lower than Meena Bazaar on mobile PageSpeed. This reflects the Fashion & Apparel category average — even established brands in this space struggle with mobile performance. The opportunity is to leapfrog the category, not just match it.
Core Web Vitals — Google's UX Quality Signals
Sites failing Core Web Vitals may rank lower in Google mobile search results
LCP How fast content appears
FCP First visual response
TBT Main thread blocking
CLS Visual stability
INP Tap/click responsiveness
What This Means for Revenue
The silver lining: real-world CrUX field data shows Meena Bazaar is competitive on the metrics that matter to users — INP 143ms, CLS 0, LCP 3.1s — beating W for Woman (5.0s LCP) and Libas (5.2s LCP, CLS 0.081) on mobile. The lab score is dragged down by render-blocking JS that hurts the entire ethnic-wear category (Biba 28, W for Woman 26, Libas 46 — all <50). Trimming the 900ms of mobile TBT through script deferral and third-party tag pruning would let Meena Bazaar leapfrog the category, not just match it.
Technology Stack
Platform
Shopify
Meena Bazaar runs on Shopify with an Online Store 2.0 theme architecture, hosted on Shopify's global PCI-compliant infrastructure with 99.99% uptime SLA, auto-scaling for traffic spikes, and full ownership of theme code. The product JSON endpoint is exposed (typical for OS 2.0) and integrations with Judge.me reviews and Growify storefront tooling are wired in via Liquid + JavaScript. Shopify gives the brand a strong foundation — what's holding mobile back is the front-end weight, not the platform.
Theme
RTS W Carousel (customised by Growify)
- Type: Online Store 2.0 — custom fork
- Fork of the 'RTS W Carousel' base theme labelled 'Copy of New RTS W Carousel — Meena Bazaar', customised by agency Growify (footer credit visible).
- Standard Shopify cart page (no drawer overlay). Mobile bottom navigation not implemented. Hamburger menu only — no inline category strip on mobile header.
Checkout & Payments
Shopify native (no Shopflo / GoKwik overlay) via Shopify Payments + Razorpay (multi-rail)
- Guest checkout available via the standard Shopify flow — no forced account creation.
- Express checkout not surfaced on the cart page. Only a single CHECK OUT button is visible — Shop Pay / Apple Pay / Google Pay buttons are NOT exposed before checkout.
- Visa, Mastercard, American Express, Maestro, Apple Pay, Google Pay, PayPal, Shop Pay — comprehensive coverage of card + UPI-adjacent rails.
Technology Assessment
Meena Bazaar's tech foundation is solid — Shopify with a customised Online Store 2.0 theme, native checkout, Razorpay-backed multi-rail payments, Shopify CDN. The platform isn't the bottleneck. What is: (1) front-end weight pulling the mobile Lighthouse lab score to 31 (TBT ~900ms from third-party tags), (2) the absence of conversion-lever apps the category expects — Snapmint/BNPL on PDP, pincode + COD eligibility check, predictive search, cart cross-sell, and express checkout buttons above the standard checkout flow, (3) no mobile bottom navigation (4 of 5 India fashion benchmarks use it), and (4) Judge.me is installed but reviews aren't being collected, leaving the social-proof real estate empty. Each of these is an installable app or a theme tweak — the upgrade path is short, not a re-platform.
UX & Conversion Findings
Page-by-page analysis with visual comparisons against top Fashion & Apparel stores
- Homepage product tiles show only image, title, and price -- no heart, no quick-add, no quick view.
- Every action on a tile requires a full PDP navigation.
- Wishlist on tiles is a 10/10 standard pattern across the fashion benchmark set.
- Add a heart/wishlist icon to every product tile and persist it to the customer profile.
- Add a Quick Add button that opens a variant picker overlay when the product has multiple sizes.
- Reveal both icons on tap to keep the tile clean until the shopper engages.
- Typing in the search bar produces no dropdown -- shoppers must hit Enter and load a results page to see anything.
- Predictive search is a 10/10 standard in the fashion benchmark set.
- Ethnic-wear queries are often occasion-based (haldi, mehendi, reception) where instant suggestions speed discovery.
- Install a predictive search app (Searchanise, Boost AI, Algolia) that shows product results and category links while typing.
- Handle misspells with a Did-you-mean fallback and a no-results suggestion strip.
- Surface trending and recently-viewed terms in the empty state.
- Collection cards show only image, title, and price -- no size pills, no colour dots, no variant indicator.
- Shoppers cannot tell whether their size is in stock without clicking each tile.
- Variant indicators on cards are a growing standard at 7/10 across the benchmark set.
- Add size pills to each collection card showing in-stock sizes; strike out OOS sizes.
- Show up to four colour dots under the card with a plus-N overflow indicator.
- Tapping a swatch should swap the card image without a PDP load.
- The collection page renders every product on one page with no pagination, no Load More button, and no lazy-load sentinel.
- On mobile this inflates DOM weight and breaks scroll-depth analytics.
- Pagination or lazy-load is a 9/10 standard in the fashion benchmark set.
- Load the first batch of products on initial render, then expose a Load More control.
- Show the running count (Viewing X of N) so shoppers know how much catalogue remains.
- Add numbered pagination at the bottom for users who want to skip ahead.
- Product title and price render above the fold with no rating or review count.
- The Judge.me widget further down reads Be the first to write a review -- zero ratings collected on this SKU.
- Star rating + review count above the fold is a 7/10 growing standard across benchmarks.
- Run a post-delivery review campaign (Judge.me + Klaviyo) to seed reviews on top SKUs.
- Once seeded, render an inline star + review count beneath the product title, linked to the reviews section.
- Aggregate parent-product reviews to the variant level so all colours and fabrics inherit the rating.
- The PDP shows variant pills (Size, Colour, Fabric) followed directly by Add To Cart -- no quantity stepper.
- Bridal-party and gifting orders force shoppers to add and then edit in the cart, doubling friction.
- Quantity steppers are a 10/10 universal pattern across the fashion benchmark set.
- Add a minus/plus quantity stepper between the variant block and the ADD TO CART button.
- Mirror the stepper inside the cart so the selection persists.
- Track add-to-cart quantity in analytics to spot bridal-party demand spikes.
- The PDP shows generic shipping copy but offers no pincode input to confirm serviceability or delivery date.
- Tier-2 and tier-3 buyers, a meaningful share of the Indian ethnic-wear market, need to know if COD is available before adding to cart.
- Pincode checkers are a 5/5 standard across the India ethnic-wear benchmark set.
- Install a pincode checker above ADD TO CART that returns expected delivery date and COD eligibility in one call.
- Render the response inline without a page reload.
- Cache the entered pincode against the customer profile so the check auto-runs on subsequent PDPs.
- The cart renders only line items, subtotal, T&C checkbox and CHECK OUT -- no FBT, no Complete the Look, no Bestsellers strip.
- Ethnic-wear orders naturally pair with dupattas, fall-edging, blouse pieces and matching accessories -- the cart is the highest-intent place to expose them.
- Cart cross-sell is a 7/10 growing standard across the fashion benchmark set.
- Add a Complete the Look strip below the cart summary with curated pairings per parent category (Suit/Dupatta, Saree/Blouse, Lehenga/Jewellery).
- Allow one-tap add-to-cart on each pairing without leaving the cart page.
- Fall back to category bestsellers when manual curation is missing for a SKU.
- Cart exposes only a single CHECK OUT button -- no Shop Pay, no Google Pay, no UPI/Razorpay Magic.
- Returning Shopify customers with a stored Shop Pay token could skip the full address and payment step if the button were exposed.
- Express checkout adoption is rising fast on India ethnic-wear (Shopflo and Razorpay Magic on Libas and W for Woman).
- Enable Shop Pay accelerated checkout in Shopify admin and surface the Shop Pay button above the standard CHECK OUT.
- Add Razorpay Magic or Shopflo to compress address and payment into a single screen for returning users.
- Surface Google Pay or UPI as a third express tile for first-time mobile buyers who prefer UPI.
- Cart copy reads discount codes calculated at checkout -- the promo input is only one screen later.
- A shopper expecting a campaign or influencer code cannot validate it before committing to checkout, fuelling drop-off when the code fails.
- Cart-level coupon fields are present on 4/5 India ethnic-wear benchmarks.
- Expose a collapsible Apply promo code input on the cart page directly above the subtotal.
- Validate the code via the Shopify Discount API and render the saving inline once applied.
- Pre-fill the field automatically when the customer arrives from a coupon-bearing campaign URL.
- The cart summary shows only Subtotal -- no aggregated savings line.
- Each line item shows the discounted price but not the per-line saving, so the shopper cannot see the value they are capturing across a discounted catalogue.
- Aggregated savings displays are a 4/5 India standard across the benchmark set.
- Add a green You saved line above the Subtotal, summing MRP minus sale price across all line items.
- Mirror the same savings line on the checkout summary so the value claim follows the shopper.
- Use the same typographic weight as Subtotal to make the saving feel real.
App Ecosystem
What's installed vs what's missing from best-in-class Fashion & Apparel stores
Detected
Missing
Present (5)
Missing (8)
App Stack Assessment
5 apps detected, 8 critical gaps identified
Confidential — Prepared for Meena Bazaar by Growisto | June 2026