Home/Case Studies/Karomi Crafts
CRO · 7 weeks

Karomi Crafts moved the loom time beside the price and lifted sales 30%.

Karomi Crafts turn handwoven jamdani into contemporary womenswear from Kolkata. The store already existed and the traffic was healthy. The project rebuilt the path from admiring the cloth to buying it.

Karomi Crafts homepage on desktop and mobile
ClientKaromi Crafts
SectorHandloom fashion
MarketIndia, shipping internationally
Timeline7 weeks
ServicesShopify Development, CRO, UI/UX
+30%Sales
<1.2sPage load

01The challenge

Karomi Crafts turn handwoven jamdani into contemporary womenswear, made in Kolkata and worn now rather than kept for occasions. The label is careful about what it claims. Sustainability is described by who wove the cloth and how long it took, not by a badge in the footer. The photography was good and the range was coherent.

People arrived, looked for a long time and left. Read quickly, that is a conversion problem, and the usual answer is a discount code and a louder button. Neither would have worked here. The visitor was not undecided about the garment. They had no way to judge what they were being asked to pay for.

A single jamdani piece can take weeks on the loom. That fact was on the site, in an about page nobody opens before checking a price. The product page carried a photograph, a size chart and a number. Set against a mill-woven copy in another tab, it lost every time, because nothing on it explained the difference.

02Our approach

UX

The decision was to treat making as product information rather than brand story. A buyer in this category reads the label before the price. So loom time, weave and the reason two pieces of one design differ had to sit on the product page itself. An about link is where a shopper puts what they have already decided not to read.

Technical

Handloom sells on texture, so the photography had to stay large and plentiful. That is usually where a fashion store loses its speed, and speed decides whether an Indian mobile visitor sees the collection at all. So the theme was planned without a page builder, with image weight treated as a design constraint rather than a later fix.

Conversion

Urgency was ruled out before anything was designed. A label that refuses to overstate its sustainability cannot invent scarcity on the way to checkout, because the buyer it wants is the one who checks. The scarcity in handloom is real, so the plan was to report it plainly and let the number do its own work.

03Design & UX

The product page ranks by what the buyer still does not know. Image first, then the making, then the price. Loom time and weaver credit sit above the fold, where a headline usually goes. The countdown, the low-stock badge on everything and the popup code were all left out. A page that shouts undermines the one claim this brand makes carefully.

On a phone the making has to survive the scroll. It is set as short lines a thumb passes rather than a paragraph, so a visitor picks up the weave and the weeks without stopping. Photographs run full width because texture is the argument. The size chart and care notes sit lower down, where a buyer looks for them only after deciding.

Loom time beside the price

A buyer comparing a handloom piece to a mill-woven copy needs the difference stated where the cost is stated, not in an about section.

Real counts, no countdown

The page reports the actual number of pieces left in a weave and says nothing more, because invented urgency is the one thing this label cannot afford.

Weaver credit above the fold

We argued for a clean first screen and lost. The founder was right, and the session recordings settled it inside a week.

No page builder

Large photography is the product, so the theme was written directly to keep the images full size and the pages quick on a mobile connection.

04Development & technical implementation

The making lives in metafields rather than in typed copy. Weave, loom time and the count of pieces in a run are structured fields the team fills in. Liquid renders them on the product page and on the collection card. That means the detail arrives with every new piece instead of depending on somebody remembering to write it.

Speed was earned in the theme rather than by cropping the archive. Every image is served as WebP and sized for the device asking for it, so a phone never downloads a desktop file. Nothing below the fold loads until it is needed. No page builder was installed, which keeps the markup close to what the page actually renders.

GA4 and Hotjar were installed before the redesign, not after it. Session recordings settled an internal disagreement inside a week, which is faster than any meeting would have. Klaviyo picks up the visitor who leaves a piece in the basket and sends the loom detail rather than a code. The email repeats the argument the page makes.

05

Key solutions.

The parts of the build a visitor would point at.

01

Making beside the price

Weave, loom time and the reason two pieces differ sit on the product page, where the buyer is deciding what the garment is worth.

02

Structured weave fields

Every piece carries the same set of craft details, so nothing depends on a description being written from memory each time.

03

Full-size photography, quick pages

Images are served as WebP and sized per device, so texture survives at full resolution without costing a mobile visitor the page.

04

Honest stock counts

The page reports how many pieces remain in a weave and adds no countdown, because the buyer this label wants is the one who checks.

05

Basket emails that explain

A visitor who leaves a piece behind receives the loom detail rather than a discount, which keeps the brand argument consistent after the visit.

06

The result.

What the work changed, in the numbers the client reports.

+30%Sales
<1.2sPage load

Sales are up 30%, on the same catalogue and the same photography. Nothing was reshot and no line was added to the range. The gain came from visitors who were already close and were missing one fact at the moment they needed it. Weeks on a loom explains a garment better than any adjective can.

Pages load in under 1.2 seconds with the photography at full size and nothing cropped to get there. On an Indian mobile connection a slow collection page is a closed tab, and a closed tab is a visitor the brand paid for twice. Speed here is not a technical score. It is the cost of being seen.

The team now writes the loom detail themselves, for every new piece, because it turned out to be the part that sells. That is the change that outlasts the project. A store can be redesigned once. A team that knows which fact closes the sale keeps applying it to everything that follows.

07

The finished site.

Live, and running the business it was built for.

Karomi Crafts homepage on desktop and mobile

The Karomi Crafts store is live and selling the same range it always had. Each piece now carries its weave, its loom time and an honest count of what is left. The making reads before the price, and the photography stays full size on a phone.

Visit the live site

We were never short of compliments. The site now turns some of them into orders, which is a different thing entirely.

— Founder, Karomi Crafts
09

Tech stack.

What it is built on, and what it talks to.

ShopifyLiquidGA4HotjarKlaviyo
10

More case studies.

Other projects where we named the number before we started.

Attackletics homepage on desktop and mobileeCommerce

Attackletics doubled sales with a neon storefront that opens like a plain one.

A smart batting tee and a finished coaching app, sold from a stock theme. Rebuilt in neon and scanlines, without making the phone pay for it.

2×Sales
+35%Order value
View case study
Applied Vision Baseball homepage on desktop and mobileeCommerce

Applied Vision Baseball left a coaching site for a store that shows gear working.

Vision and swing trainers that make no sense in a photograph. Moved out of a coaching site and onto a storefront built around the demonstration.

+46%Conversion
+56%Organic traffic
View case study
MindPanda homepage on desktop and mobileeCommerce

MindPanda built its own channel and pushed Amazon into second place.

An established Amazon seller with no channel of its own. Catalogue ported across, two markets configured, and a storefront designed to convert rather than list.

7 figuresDirect revenue
No.1Channel, ahead of Amazon
View case study
03

Let us look at your numbers.

Send the metric that is stuck and we will tell you honestly whether we agree.

Free consultation — 30 minutes, no obligation, senior lead on the call
1
Within 1 business dayWe read it properly and reply with real questions — not a templated brochure.
2
A 30-minute scoping callFree, no obligation. We tell you honestly if we are the wrong fit.
3
A written proposalScope, timeline, deliverables and the success metric — all on one page.
SAR+
You'll hear back from Sayan or a senior lead — never a bot.

    Your details
    What do you need?
    eCommerce buildCRO & testingWebsite designApp / SaaSDesign & brandingSomething else
    NDA on request · Details never shared
    Question about your project? Tell us in 30 seconds — a senior lead replies.