Navshtri · concept redesign
Navshtri: 8.2 s to 1.8 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.
TodayThis concept
TodayThis concept
Same test, both sites.
Main content on screenLargest Contentful Paint (LCP), simulated slow 4G phone
−78%Performance scoreLighthouse, out of 100
+31 ptsPage weightEverything the phone downloads
−90%RequestsFiles the page asks for
−81%Until fully usable (simulated)Time to Interactive, Lighthouse's strictest number
−81%On a desktop screen
- Main content on screen
- 2.6 stoday, this concept0.6 s
- Performance score
- 82 / 100today, this concept100 / 100
- Page weight
- 4.7 MBtoday, this concept271 KB
- Requests
- 121today, this concept20
- Until fully usable (simulated)
- 2.9 stoday, this concept0.6 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 navshtri.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 to 3.5 s mobile LCP on the same slow-4G Lighthouse test for the real WooCommerce build (today 8.2 s); this static concept loads faster because it has no plugins, cart or checkout.
What we found, and what we did.
-
On the product page the 'Buy any 2 & get 1 free' ad opens, the first phone screen shows no price and no Add to cart button (only the offer bar, a 4.8 rating pill, the product photo and its name); a buy bar appears only after scrolling about two screens
A shopper from a paid ad decides in the first screen: with no price and no way to buy in sight they have to scroll to find out what the saree costs.
EvidenceSeen at no price in the first screen at 390x844 (read 206 characters and 6 images on it); audit.json landing.price = absent, no buy button (add to cart / buy now / shop) in the first screen at 390x844; audit.json landing.buyButton = absent (a fixed buy bar shows only after scrolling 1688 px)

first phone screen of the page the ad opens: offer bar, rating pill, product photo and name; no price, no Add to cart In this concept: The first phone screen of the concept's home page shows the saree, its price (₹1,599, with the ₹3,599 struck through), the Buy-any-2-get-1-free offer, Navshtri's store-wide rating (4.8 from 25,000+, labelled as store-wide) and a "Shop the ₹1,599 trio" button. The first screen of the product page shows the saree photo and name, the same price with "Save ₹2,000", the rating, the offer, and a bar fixed at the bottom with the price and Add to bag, in view from the moment the page opens.
-
The home page links to the 'Divine Silk' category, which answers 404 (1 broken of 40 links checked)
A shopper who taps a category from the home page and gets an error page is one step from leaving.
In this concept: The menu, the category chips and the footer list only categories that exist on navshtri.com (Ready to Wear, Premium Collection, New Trends, Organza, Cotton Silk, Linen, Stitched Blouse). The dead Divine Silk link is gone: every link in the concept opens a page or section of the concept, or WhatsApp, the phone or email.
-
On a slow-4G phone test (Lighthouse) the main content takes 8.2 s to appear (mobile LCP, median of 3 runs)
Shoppers arrive from a paid ad on a phone; every second before the product appears is a paid click that can leave.
Evidence- LCP 8.2 s (slow-4G phone test)

Screenshot In this concept: Each page's main photo is one phone-sized AVIF of the real saree, loaded first and preloaded (15 KB on the home page, 28 KB on the product page); the home hero adds two small side photos (13 KB each) and every image further down loads lazily. No page builder, carousel library, chat widget or app scripts: one small TypeScript file and one self-hosted font family (Lora, their heading font). Honest caveat: this is a static concept with no plugins, cart or checkout; the real WooCommerce build will be heavier (target in the numbers above).
-
On the same slow-4G phone test, Mimosa (same Banarasi saree price band, Rs 999-1,799) shows its main content in 5.2 s; Navshtri takes 8.2 s
Shoppers comparing sarees from ads open several stores; the one that shows its sarees first gets the attention.
Evidence- mimosa.in | Mobile load speed (LCP): 5245
In this concept: Same light pages as in the speed item, measured with the same Lighthouse phone test as Navshtri and Mimosa, so the numbers above can be set directly against Mimosa's 5.2 s. Honest caveat: this is a static concept; the real WooCommerce build will be heavier.
-
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.
EvidenceIn this concept: The footer has a "Business details" block with a labelled GSTIN line. The concept prints the label and says the number goes there in the real build: we do not invent a GSTIN. Their 4.8 rating from 25,000+ reviews (labelled as store-wide), 10-day returns and COD stay next to the buy button; contact details are in the footer.
What stronger competitors do, now here too.
mimosa.in · Mobile load speed (LCP)
mimosa.in shows its main content in 5.2 s on a slow-4G phone test (Lighthouse); the brand takes 8.2 s
In this concept: The first thing painted is one small photo of the saree, with no plugins or third-party scripts in front of it. Measured with the same phone test; see the numbers above.
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.