Concept redesign by Kaarigar Labs. Not affiliated with Banarasee.

Back to the concept

Banarasee · concept redesign

Banarasee: 5.9 s to 3.3 s.

Main content on screen on a phone (largest Contentful Paint (LCP), simulated slow 4G phone), measured the same way on today's site and on this concept.

Drag to compare

Screen
Screenshot of the concept for Banarasee on a phone Screenshot of Banarasee's site today on a phone TodayThis concept
On a phone, top of the home page. Left: today's site. Right: this concept.
Screenshot of the concept for Banarasee on a desktop screen Screenshot of Banarasee's site today on a desktop screen TodayThis concept
On a desktop screen, top of the home page. Left: today's site. Right: this concept.
01 / The numbersMeasured, not estimated

Same test, both sites.

Main content on screenLargest Contentful Paint (LCP), simulated slow 4G phone

−44%
Today5.9 s This concept3.3 s

Performance scoreLighthouse, out of 100

+28 pts
Today63 / 100 This concept91 / 100

Page weightEverything the phone downloads

−96%
Today9.1 MB This concept412 KB

RequestsFiles the page asks for

−95%
Today420 This concept21

Until fully usable (simulated)Time to Interactive, Lighthouse's strictest number

−85%
Today21.2 s This concept3.3 s

On a desktop screen

Main content on screen
1.2 stoday, this concept0.7 s
Performance score
74 / 100today, this concept99 / 100
Page weight
5.9 MBtoday, this concept462 KB
Requests
416today, this concept21
Until fully usable (simulated)
1.2 stoday, this concept0.7 s

Both columns were measured the same way (Lighthouse, simulated slow mobile network and CPU): the live site on 2026-11-20, and this concept on its hosting at banarasee.kaarigarlabs.com on 2026-11-20.

A static concept loads faster than a live store with real apps and a real checkout, so read the concept column as a ceiling, not a promise. Realistic target for the real build: about 2.5-3 s mobile LCP on the same slow-4G Lighthouse test (from 5.9 s today), on Shopify with Judge.me and the PayU checkout kept.

02 / What changed4 found

What we found, and what we did.

  1. 1 of 4 running ads ("Your perfect Banarasee saree is still here") sends paid clicks to a 404 Not Found page

    A shopper who taps the ad and gets "Page not found" leaves; the click was already paid for.

    Evidence

    Seen at landing of ad 3649912368497073: HTTP 404, "Page not found" (checked 2026-11-20)

    first phone screen of that landing page: 404 Page not found
    first phone screen of that landing page: 404 Page not found

    In this concept: The concept adds the page that ad should have opened (landing.html, "Still here for you"): the saree the shopper looked at, big, with its price (₹2,199), the store rating and one Add to bag button on the first phone screen, then COD, delivery and returns facts, a sticky Add to bag bar and four more sarees from the store. In a real build, the link of a product that has been removed could lead to a page like this instead of "Page not found".

  2. On the product page one of the ads opens, the first phone screen shows no Add to cart button (only the photo, name, rating and a clipped price), and no sticky buy bar appears after scrolling two screens down the 4,858 px page

    A shopper arriving from a paid ad decides in the first screen; with no way to buy in sight they have to scroll a long page to find the button.

    Evidence

    Seen at no buy button (add to cart / buy now / shop) in the first screen at 390x844 (read 148 characters and 1 image on it); audit.json landing.buyButton = absent

    first phone screen of that product page: photo, name, 1 review, price cut off at the bottom, no Add to cart
    first phone screen of that product page: photo, name, 1 review, price cut off at the bottom, no Add to cart

    In this concept: The first phone screen of the concept's landing page shows the saree photo, its name and colour, the price (₹2,199), the store rating (4.93 from 6,908 reviews) and a full-width Add to bag button; the BANARASEE5 code sits in the bar above the header. A sticky Add to bag bar slides up once the page is scrolled past that button.

  3. On a slow-4G phone test (Lighthouse) the main content takes 5.9 s to appear (mobile LCP, median of 3 runs); the page weighs 9.1 MB

    Shoppers arrive from a paid ad on a phone; every second before the product appears is a paid click that can leave.

    Evidence
    • LCP 5.9 s (slow-4G phone test)
    • Page weight 9.1 MB
    Screenshot
    Screenshot

    In this concept: Each page loads one compressed photo first (the home hero is a 53 KB AVIF on phones, the landing page's first photo 27 KB), with no third-party scripts and under 3 KB of script of our own. Honest caveat: this is a static concept; the real Shopify build with reviews and the checkout will be heavier (target in the numbers above).

  4. No GST number anywhere on the site (home, collection, product, policy and contact pages checked)

    A printed GSTIN is one of the few ways a first-time buyer from an ad can tell a registered business from a fly-by-night store; it is a small trust signal, not a big one.

    In this concept: The footer of both pages carries a labelled GSTIN line ("printed here in the real build") next to Banarasee's published address and contact details; the number itself is for Banarasee to fill in (we never invent one).

Want this live on your domain?

Kaarigar Labs designs and builds fast websites for D2C brands, as a custom build or on the store platform that suits you. It starts with a WhatsApp message.