Jaipur Kurti
01

Audit Overview

Your store's untapped revenue potential — and how to unlock it

Why We Created This Audit

We analyzed https://jaipurkurti.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.

1 Critical
4 Important
0 Opportunities

What We Analyzed

  • UX & Conversion Design5 findings
  • Performance & Speedvs 3 competitors
  • Technology & App StackPlatform + 7 apps
  • Industry BenchmarksFashion & Apparel

Pages Analyzed

  • Homepage2 findings
  • Collection Pages1 findings
  • Product Pages (PDP)2 findings
Growisto 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.
02

Performance & Technology

Speed benchmarks, Core Web Vitals, and technology assessment for Jaipur Kurti

37

Mobile PageSpeed Score

Mobile lab score of 37/100 sits in the same band as every benchmarked competitor (Libas 33, Soch 36, Biba 40) — slow mobile pages are a category-wide norm in Indian ethnic wear, not a Jaipur Kurti-specific weakness. The lab bottleneck is render-blocking work: a 23.3s Largest Contentful Paint and 1,013ms of main-thread blocking, against a near-perfect layout stability score of 0.001.

Competitive Comparison

Benchmarked against 3 leading Fashion & Apparel stores in your market

Store Mobile Score Desktop Score Mobile LCP Mobile CLS Mobile TBT
Jaipur Kurti (Client)375723.3s0.0011,013ms
Libas3358———
Biba4041———
Soch3651———
Good
Needs Improvement
Poor

⚠ Note: Libas, Soch score lower than Jaipur Kurti 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.

⚡ A 1-second delay in mobile load time can reduce conversions by up to 7%. For every 100ms improvement in LCP, conversion rates increase by ~0.4%. Source: Google/Deloitte, 2024

Core Web Vitals — Google's UX Quality Signals

Sites failing Core Web Vitals may rank lower in Google mobile search results

⚠ 2 of 5 Core Web Vitals passed
LCP How fast content appears
23.3s
Target: ≤ 2.5s
Fail
FCP First visual response
2.4s
Target: ≤ 1.8s
Fail
TBT Main thread blocking
1013ms
Target: ≤ 200ms
Fail
CLS Visual stability
0.001
Target: ≤ 0.1
Pass
INP Tap/click responsiveness
127ms
Target: ≤ 200ms
N/A

What This Means for Revenue

Jaipur Kurti scores 37/100 on mobile and 57/100 on desktop in Lighthouse lab conditions — mid-pack against Libas (33), Soch (36) and Biba (40). The more important number is the field data: real visitors on jaipurkurti.com record a 1.6s LCP, 127ms INP and 0.00 CLS, all of which Google classifies as FAST, giving the origin an overall FAST rating. In other words, actual customers are not experiencing the slowness the lab test simulates on a throttled mid-tier device. That gap matters for prioritisation: speed work would buy real but incremental gains, whereas the conversion gaps documented in the UX section are where the larger, faster upside sits. Layout stability (0.001 lab, 0.00 field) is already best-in-class and should be protected by any future changes.

Technology Stack

⚠ 4 of 6 technology areas are well-configured — payments verification and cookie consent need attention
Modern Platform

Platform

Shopify

Shopify-hosted storefront with checkout on the primary domain (jaipurkurti.com/checkouts/...) — auto-scaling, PCI-compliant, no self-managed infrastructure risk.

Prestige 10.11.0

Theme

Prestige

  • Type: Premium Shopify theme (Archetype Themes) — OS 2.0 / Online Store 2.0 compatible
  • Theme schema reports version 10.11.0, a current Prestige release
  • Section-based OS 2.0 theme with native predictive search, size-chart modal, and image-zoom support
Native

Checkout & Payments

Native Shopify Checkout via Shopify Payments (gateway not fully exposed pre-address; COD available)

  • Guest checkout: Enabled — checkout offers 'Email or mobile phone number' with an optional 'or sign in', no forced account creation
  • Express checkout: No Shop Pay / Google Pay / PayPal accelerated button observed above the contact form on the checkout's first screen
  • Cash on Delivery (via Releasit COD Fee app); card/UPI/wallet methods only surface after address entry in the native checkout, not independently verified in this pass

Technology Assessment

Jaipur Kurti runs on Shopify with the premium Prestige theme (v10.11.0) and native Shopify checkout — a solid, low-risk technical foundation with no custom checkout override. Guest checkout is enabled and the storefront carries a full analytics stack (GTM, GA4, Google Ads, Meta Pixel/CAPI). The main technical gaps are a missing cookie-consent banner, no visible express-checkout button (Shop Pay/GPay) on the checkout's first screen, and no BNPL/EMI option surfaced on product pages — all straightforward additions on top of the existing Shopify + Prestige stack.

03

UX & Conversion Findings

Page-by-page analysis with visual comparisons against top Fashion & Apparel stores

Add a clickable Shop Now button to the hero banner — all 5 rotating slides link only via a full-bleed image with zero visible CTA text
Jaipur Kurti — Mobile
Jaipur Kurti — Mobile
Libas — Mobile
Libas — Mobile
Observations
  • The homepage hero is a 5-slide auto-rotating carousel (Sarees/'Timeless Grace', 'Happy Raksha Bandhan', 'Workwear that works for you', and more) — every slide checked live has decorative headline text over a photo, but no button element with action copy.
  • The entire hero image is wrapped in one large link to a collection page, so a tap anywhere 'works', but there is no visual affordance telling the shopper where the tap will take them or that it's clickable at all.
  • Two of the slides even carry strong supporting copy (USP icon rows, festive messaging) that would justify a real CTA button, but neither converts that into an explicit 'Shop Now'/'Explore' action.
  • The hero occupies the entire first screen on a 390px-wide phone — the highest-visibility real estate on the homepage — so an unclear CTA here costs engagement before the shopper even reaches the category grid.
Recommendations
  • Add a high-contrast button (e.g. 'SHOP SAREES', 'EXPLORE WORKWEAR') to every hero slide, matching the specific collection each slide promotes.
  • Keep the full-image tap target for forgiving UX, but layer the button on top so the CTA is visually explicit, not just implied.
  • A/B test button copy per slide (festive vs. workwear vs. everyday) since each slide currently targets a different shopper intent.
Standard — prominent hero CTA buttons are the norm among direct ethnic-wear competitors (see Libas 'EXPLORE >')
Surface the offers you already run in a top announcement bar — the homepage's top strip sells retail credentials, not a reason to buy today
Jaipur Kurti — Mobile
Jaipur Kurti — Mobile
Libas — Mobile
Libas — Mobile
Observations
  • The full-width strip at the very top of the homepage is spent on brand credentials — “Since 2012 : Retail Presence : Shoppers Stop : TRENDS : CENTRO : AVANTRA : & 250+ MBOs”. That is strong authority, but it carries no offer, no urgency and no reason to act today, and it occupies the highest-attention slot on the page.
  • Below it the hero carousel advertises a festive collection (“Celebrate Every Tradition”, “FESTIVE COLLECTION”) with no discount, coupon or deadline attached. Sweeping the full homepage in both directions surfaced no promotional bar anywhere — the only price-related text on the page is the “SALE PRICE” label on individual product cards.
  • The offers do exist, they are just held back until much later in the journey: the PDP carries a “Best Offers” block (a Razorpay “EXTRA 5% OFF (Max. ₹300) on orders above ₹999” plus a prepaid-order offer) and the cart applies a Flat 350 OFF coupon. A visitor who bounces from the homepage never learns that any of it exists.
  • Libas runs a live “Flash Sale Ends In” countdown bar above its header, plus a second ticker carrying “₹200 OFF | CODE: SALE200 | BUY FOR MIN. ₹2499” — so the offer, the code and the deadline are among the first things a visitor reads.
Recommendations
  • Move the strongest existing offer into that top strip, or into a second bar directly beneath it — the Razorpay prepaid discount is already funded, so this is a surfacing change rather than a new promotion.
  • Rotate two or three messages (offer, shipping and returns promise, festive edit) instead of a single static line, so the slot keeps earning its position.
  • Keep the retail-presence credential, but pair it with a deadline where one genuinely applies — festive demand in this category is date-bound, and a real deadline is what turns an offer into a reason to buy now.
Growing — 7/10 fashion stores in our benchmark run an announcement or promo bar
Show color swatches on all product cards so shoppers compare 3+ shades without opening each PDP — currently only size pills appear on Suit Sets cards
Jaipur Kurti — Mobile
Jaipur Kurti — Mobile
Biba — Mobile
Biba — Mobile
Observations
  • Every product card on the Suit Sets collection shows a SAVE% badge, a wishlist heart, strikethrough MRP + sale price, and a row of size buttons (S/M/L/XL/XXL) — but zero color swatches anywhere on the card.
  • Checked across multiple rows of the live grid (scrolled through 10+ cards): the pattern is consistent — size-pills-only, no color circles.
  • Many of the suit-set styles shown are available in 2+ colorways (confirmed on individual PDPs), so the collection grid is hiding real variant choice that would otherwise pull a shopper deeper into a specific listing.
  • This is an industry-specific gap for fashion: color is typically a bigger purchase driver than size at the browse stage, since size is personal and known, but color needs to be seen to be chosen.
Recommendations
  • Add small color-swatch circles below the price on each collection card, sourced from the product's available variants.
  • Make swatches interactive — tapping a swatch should swap the card's thumbnail to that color, the way Biba does it, so shoppers can browse colorways without leaving the grid.
  • Cap visible swatches at 4-5 with a '+N' overflow indicator for products with many colorways, to keep the card from feeling cluttered.
Differentiator — only 4/10 fashion stores in our benchmark show color swatches on collection cards, so this is a competitive edge rather than table stakes
Surface star rating and review count above the fold on the Rs. 1,199 kurta PDP — zero social proof appears near the title or price today
Jaipur Kurti — Mobile
Jaipur Kurti — Mobile
Libas — Mobile
Libas — Mobile
Observations
  • The product title, price (Rs. 1,199, struck-through Rs. 3,999), and image gallery all appear above the fold on this PDP — but no star rating or review count sits anywhere near them.
  • Scrolling through the full above-fold area and the entire buy-box zone (size, color, quantity, Add to Cart, wishlist, postal-code check, delivery/return text) confirms there is no rating widget anywhere on the page at all, not just below the fold.
  • First-time visitors have to make a Rs. 1,199 purchase decision with zero peer validation, which is a much bigger trust gap than a store where reviews merely load slowly or sit lower on the page.
  • This is flagged as a high-priority gap industry-wide — fashion buyers rely heavily on fit and quality validation from other shoppers before purchasing apparel sight-unseen.
Recommendations
  • Install a review app (Judge.me, Loox, or similar) and surface the aggregate star rating + review count directly under the product title, matching the price-proximity placement competitors use.
  • Backfill ratings from historic order data or a review-request email flow if the catalog currently has no collected reviews yet.
  • Make the rating clickable so it jumps to a full reviews section further down the page.
Growing — 7/10 fashion stores in our benchmark show star ratings on the PDP
Add a Buy Now button beside Add to Cart to cut checkout to 1 tap — this Rs. 1,199 PDP offers only the single Add to Cart action
Jaipur Kurti — Mobile
Jaipur Kurti — Mobile
Global Desi — Mobile
Global Desi — Mobile
Observations
  • The buy-box on this PDP has exactly two buttons: 'ADD TO CART' (black, primary) and 'ADD TO WISHLIST' (dark grey, secondary) — no third 'Buy Now' option that skips the cart page entirely.
  • Every shopper who wants to check out immediately (a common intent on a single-item Rs. 1,199 impulse-adjacent purchase) is forced through Add to Cart -> view cart -> Checkout, three taps and two page loads instead of one.
  • Global Desi places a clearly outlined 'BUY NOW' button directly under the black 'ADD TO BAG' button on every PDP, giving decisive shoppers a direct line to checkout.
Recommendations
  • Add a secondary 'Buy Now' button under the existing Add to Cart button that adds the item and routes straight to checkout, bypassing the cart page.
  • Keep Add to Cart as the primary (filled) button and Buy Now as a secondary (outlined) button, matching the visual hierarchy Global Desi uses.
  • Verify the Buy Now flow respects the selected size/color/quantity exactly as Add to Cart does before shipping it.
Growing — a direct Buy Now shortcut is a common conversion lever among competitor PDPs (see Global Desi)
04

App Ecosystem

What's installed vs what's missing from best-in-class Fashion & Apparel stores

7 Apps
Detected
3 Critical Categories
Missing
Fashion D2C stores at this scale typically run 8-12 purpose-built apps spanning reviews, email/SMS, upsell, loyalty, chat, and shipping. Jaipur Kurti covers wishlist, COD handling, a chat widget, and a full analytics stack, but has no review platform installed at all — the single highest-leverage gap given the missing PDP-01/PDP-11 social proof findings.

Present (7)

✓
Wishlist Hero
Wishlist & Save for Later
Wishlist heart icon present and functional on collection cards, PDP, and header
✓
✓
Releasit COD Fee
Payments (COD)
Adds a handling fee to Cash on Delivery orders — script loads on cart/checkout pages
✓
✓
Bob the Bundle Builder
Upsell & Bundles
App bundle ships a free-shipping-bar module and a shadow cart-drawer module, but neither rendered during this audit — the live cart is a plain full page with no shipping progress bar, suggesting the app is installed but not actively configured on this store's templates
⚠
✓
Copilot.live Chat Widget
Live Chat & Support
Floating chat bubble visible in the bottom-right corner across homepage, collection, PDP, and cart
✓
✓
Google Tag Manager + Google Analytics 4
Analytics
Multiple GTM containers and GA4 property IDs firing on page load
✓
✓
Google Ads Conversion Tracking
Analytics & Ads
AW- conversion ID script present
✓
✓
Meta Pixel + Conversions API
Analytics & Ads
fbevents.js plus a hashed server-side (CAPI) signals config present
✓

Missing (3)

✗
Reviews & UGC App (Judge.me / Loox / Stamped) Critical
Reviews & Social Proof
📈 First-time buyer trust +; directly closes the PDP-01 no-ratings gap
Anti-pattern flagged HIGH impact — no customer reviews on PDP is a critical trust gap in 3/5 India fashion stores benchmarked
✗
Email/SMS Marketing Platform (Klaviyo / Omnisend) Recommended
Retention & Marketing
🔄 Abandoned-cart and post-purchase flows typically recover 5-15% of otherwise-lost revenue
No Klaviyo/Omnisend script detected in the current script stack
✗
Loyalty / Rewards Program (Smile.io) Recommended
Customer Retention
🔄 Repeat-purchase incentive for a wardrobe-replenishment category like ethnic wear
Differentiator — 4/10 fashion stores in our benchmark run a loyalty/rewards program

App Stack Assessment

Jaipur Kurti's app stack is analytics-heavy (GTM, GA4, Google Ads, Meta Pixel/CAPI all firing) and covers wishlist and COD-fee handling, but is missing the reviews/UGC layer entirely — a gap that shows up directly in the UX audit as no star ratings anywhere on the PDP. A 'Bob the Bundle Builder' app is installed with free-shipping-bar and cart-drawer modules bundled in, but neither feature is visibly active on the templates checked, suggesting partial/inactive configuration worth a quick admin-side review before assuming those features are unavailable.

1 / 1