01  ·  TrooPerformance  ·  Where things stand today

A product page that loads before the shopper leaves

Slow pages cost conversions, and they usually get slower with every app and tag a team adds. Troopod pairs its TrooPerformance agent with a team of performance engineers. The agent tracks the speed impact of every change on the site and flags a slowdown the moment it ships. Our engineers fix the underlying issues and work with app vendors on the fixes that need them.

Page auditedTennis Girlie Square Front Back Earrings
Domainisharya.com
ThemeImpulse 7.4.0
Date29 Sep 2026
ToolLighthouse 13.5.0, mobile
33Mobile performance score, out of 100
24.1sLargest Contentful Paint: time until the main product photo shows
2,000msTotal Blocking Time: how long the page ignores taps while loading
5.8 MBDownloaded to show one product page on a phone
REAL SHOPPERS · LAST 28 DAYS · ALL OF ISHARYA.COM ON MOBILE

Core Web Vitals assessment: Failed

This is Google's own data from real Chrome users, not a test. It's one of the signals Google uses to rank pages.

LCP · main image shows3.7sGood is under 2.5s
INP · response to a tap231msGood is under 200ms
CLS · layout jumping0.01Good is under 0.1
FCP · first thing on screen2.2sGood is under 1.8s
TTFB · server response0.8sGood is 0.8s or less
MOBILE33
Speed Index8.5s
Largest Contentful Paint24.1s
Total Blocking Time2,000ms
First Contentful Paint3.4s
Cumulative Layout Shift0.007
DESKTOP47
Speed Index1.7s
Largest Contentful Paint4.4s
Total Blocking Time950ms
First Contentful Paint0.8s
Cumulative Layout Shift0.034

Lab scores move from run to run with device, network and time of day. We treat results within ±15% as the same.

02  ·  Diagnosis

What's slowing the page down

We inspected the live PDP in Chrome and read the full Lighthouse report. The phone spends 7.4 seconds of main-thread work on this one page, 4.9 seconds of it running JavaScript. Most of that JavaScript comes from apps and tags, not from Isharya's theme.

Script evaluation 4.4s Parsing and compiling scripts 1.3s Everything else, including layout and paint 1.7s
FINDING 01  ·  CHECKOUT APP LOADED ON THE PRODUCT PAGE
App-side · Track 2

Shiprocket's checkout downloads 1.1 MB before anyone taps Buy

Shiprocket's one-click checkout (served from pickrr.com) loads its full checkout app on every product page visit. The shopper hasn't reached checkout, so almost none of it is used.

HIGHEST IMPACT

2.0 MB of unused JavaScript, and a script that blocks the first paint

Lighthouse finds 2,026 KiB of Pickrr JavaScript unused on this page, the largest single saving in the report. Its marketing script and stylesheet block rendering for up to 1.9 seconds. Shiprocket's tracking script uc.js is also loaded three times, and its iframe alone takes 840ms of main-thread time.

FINDING 02  ·  TRACKING
Theme + app · Track 1 & 2

The Google tag loads five times, alongside four other trackers

Google's tag script (gtag.js) is added four separate times, plus a Google Tag Manager container, adding up to 784 KiB and over 1 second of main-thread time. Lighthouse lists five of the page's 20 long tasks as Google tags.

OVERLAP

Five analytics tools measuring the same visit

Google's tags, the retired Universal Analytics script (analytics.js), Meta Pixel (252 KiB), Microsoft Clarity and Plausible all run on the same page. Most of these can be consolidated into one Tag Manager container and loaded after the page is usable.

FINDING 03  ·  DUPLICATE APPS
App-side · Track 2

Two WhatsApp widgets, and an app that loads itself twice

Two different WhatsApp chat widgets are installed: one from Shiprocket Engage and one from LimeChat. The LimeChat button is a 111 KiB animated GIF. A single chat widget would do the same job.

LEGACY CODE

A sticky add-to-cart app loads jQuery 1.9.1 twice

The add-to-cart app from goldendev.win adds its script twice, and each copy pulls in its own copy of jQuery 1.9.1, a 2013 release. The page also loads Wigzo push and engagement scripts, a Hextom promotion bar, an Instafeed feed, a ReelUp video widget, a SpiceGems country redirect and OTPless login, all on first load.

FINDING 04  ·  THE MAIN PRODUCT PHOTO
Theme-side · Track 1

The product photo is downloaded quickly, then waits 4.4 seconds to appear

Lighthouse's breakdown of the main image shows the server and download take under 0.3 seconds. The remaining 4,420ms is render delay: the photo is ready, but the phone is busy running scripts and waiting on blocking stylesheets, so it can't paint it.

RENDER-BLOCKING

Four stylesheets hold up the first paint

theme.css (1.75s), a Shopify app stylesheet smi-base.min.css (1.65s), the Google Fonts stylesheet (0.75s) and custom.css all block rendering. Critical styles can be inlined and the rest loaded without blocking.

FINDING 05  ·  IMAGES AND CACHING
Theme-side · Track 1

Small icons shipped as large files, and assets that aren't cached

The four trust badges under the buy button (18K Gold Plated, Certified Skin Safe, Easy 7 Day Returns, Free Shipping) are PNGs totalling 155 KiB, almost all of it wasted at the size they're shown. In total, Lighthouse estimates 339 KiB of image savings, and 43 of the page's 49 images have no set width and height.

REPEAT VISITS

668 KiB is re-downloaded on every visit

Meta Pixel, the LimeChat GIF, Shiprocket's scripts and some Shopify checkout files are sent with short or no cache lifetimes, so a returning shopper downloads them again.

Where the phone's time goes, by vendor Lighthouse mobile, main-thread time and download size
SourceWhat it isMain threadDownloadFixed under
Shiprocket / PickrrOne-click checkout, tracking, WhatsApp1.1s+1.3 MBTrack 2
Google tagsgtag.js ×4 and Tag Manager1,036ms784 KiBTrack 1 & 2
Isharya theme and ShopifyTheme scripts, product page, Shopify storefront838ms208 KiB+Track 1
MetaMeta Pixel—252 KiBTrack 1 & 2
LimeChatSecond WhatsApp widget, animated GIF—112 KiBTrack 2
03  ·  Our Approach

Fix what's in the theme, then work through the apps

Some of the slowdown sits in Isharya's theme and can be fixed directly. The larger part comes from third-party apps, which need the app vendors involved. We split the work the same way.

PHASE 01

Optimise the theme, then hold the gain

Fix everything inside the theme on a duplicate copy, review it with the Isharya team, ship it, then make sure it doesn't slip back as new changes go live.

→
PHASE 02

Reach the target, then maintain it

Work with app vendors on the scripts dragging the score down until real shoppers pass Core Web Vitals, then hold it there.

TRACK 1 · THEME-SIDE · WHAT WE FIX FIRST
  • Show the product photo first. Mark the main image as high priority and remove what delays its paint.
  • Unblock rendering. Inline critical CSS and load theme, app and font stylesheets without blocking.
  • Defer every non-essential script until the page is usable, or until the shopper interacts.
  • Consolidate tracking into one Tag Manager container and remove the duplicate Google tags and retired Universal Analytics.
  • Right-size images: trust badges as SVG, width and height on every image, modern formats throughout.
TRACK 2 · APP-SIDE · WHAT WE TAKE TO VENDORS
  • Shiprocket / Pickrr: load the checkout only when a shopper taps Buy Now or opens the cart, and load uc.js once.
  • WhatsApp: keep one widget, drop the other, and swap the GIF for a static icon.
  • Sticky add-to-cart: load the script once, or replace it with a lightweight theme feature and drop jQuery.
  • Everything else: review Wigzo, Hextom, Instafeed, ReelUp, SpiceGems and OTPless against their use on the product page.
Mobile score today33
Phase 01 goal50+
Ideal targetPass Core Web VitalsReal-user LCP under 2.5s and INP under 200ms

How we'll get there

01

Real-time monitoring with the TrooPerformance agent

The agent measures the page after every change to the site and flags a slowdown when it ships, before it quietly becomes the new normal.

ALWAYS ON
02

Monthly audit

Troopod re-audits every month, reports the change against the last audit, and fixes anything that has slipped.

Monthly
03

Change guidelines

A living guideline document for Isharya's tech team and agencies, so new apps, tags and sections don't erode the speed that's been won.

From month 1
04

App vendor coordination

We work directly with Shiprocket, LimeChat and the other app teams on their scripts. This needs introductions from the Isharya team.

Track 2
04  ·  Why Troopod

Recent work

Similar theme-side performance work, delivered for a brand in the Essor Group's ($1B+) portfolio in 2 weeks.

32 → 62Average performance score across all pages, roughly 2x
35s → 4.5sAverage page load time on a throttled mobile connection
2 weeksTime to deliver the optimisation

Recently working with, among others:

TanishqDurexBombay Shaving CompanyEssor GroupWellbeing Nutrition
Neeraj JoshiCEO, Troopod

Early product at Spinny. Built an internal CRM that lifted team efficiency by 10x.

Rahul BholaCTO, Troopod

Tech at Lenskart. Built a backend retail system scaled to 10 million plus customers.

Vinit SinghBusiness Lead, Troopod

Early growth at Spinny. Now driving growth for 100+ consumer brands at Troopod.