November 2026 · Strictly confidential
We looked at why men arrive ready to buy a suit, find one they like, and leave without buying it.
- What the five audits were, in plain words.
- The one thing all five of them found.
- The scale of the work behind the findings.
- Where to start reading.
The commercial offer is strong. Suits run from 10,999 to 31,999 rupees, delivery is three days against a real date, and there are more than 400 stores. What is missing is confidence at the moment of deciding, and it fails in three places: fit, price and proof.
Every one of the five shoppers found a product they wanted within three clicks. Not one of them finished a purchase without stopping over something the page failed to tell them.
Five audits, run independently, then read together.
- What each of the five audits actually did.
- The scope and the method behind each one.
- What each audit can see, and what it cannot.
- What was deliberately out of scope.
Five audits, four days, one store.
Each one looked at the same shop from a different angle. They were run independently, then read together.
Shopper simulation
11 November 2026Five buyer types, each walked through the store in a live browser session on a desktop screen, six steps from landing to the payment screen.
AI Shopper Audit
What it cannot see. It models how a buyer behaves. It is a careful model, not a customer, and it ran on desktop only, so nothing here describes the phone journey.
Page review
November 2026Every page type checked element by element against a standard list, on a phone, with the working parts recorded as well as the broken ones.
UI and UX Heuristics and CRO Audit
What it cannot see. It sees what is on the page. It cannot see how many people struggled with it, because no behaviour data was available.
Speed test
13 November 2026Core Web Vitals measured from real visitors over 28 days, on mobile and desktop, across the whole site and three page types.
Web Performance Audit
What it cannot see. It is real visitor data, so it is what Google uses. It reads a moment in time and will move as the site changes.
Store connection
13 November 2026Eight capabilities tested live on the site, the locator and the payment screen, with three competitors tested the same way on six of them.
Omnichannel Capability Audit
What it cannot see. It tests what a shopper can actually do. It cannot see the stock systems behind the shop front, so some causes stay unconfirmed.
Being found
13 November 2026The full catalogue crawled, plus a fixed panel of 20 questions put to five AI engines under identical conditions.
AEO, GEO, SEO and Agentic Visibility Audit
What it cannot see. The crawl is complete. The AI answers are a single pass on one day, so treat the rates as a reading rather than an average.
Nothing in this report uses data from inside the business. No sales figures, no visitor numbers, no session recordings and no search console data were available, so every behavioural statement here is something we watched happen rather than something we counted. Where that matters, we say so on the finding itself. Section 09 lists the access that would turn these observations into measurements.
People arrive ready to buy a suit. The product page will not tell them what size it is.
- Why discovery is not the problem here.
- Why fit is where every shopper stops.
- What the 400 stores could be doing and are not.
- Why none of it needs a redesign.
- What we still cannot measure.
The shop works. Five men proved it in an afternoon.
We sent five different buyers through the store: a man looking for a wedding suit, a graduate buying his first interview suit, a manager restocking office shirts, a wife buying a gift, and a man who wears a 48. All five found something they wanted within three clicks.
That is not normal. The menu leads with what Indian men actually shop for. There is a Wedding Store and a Winter Store at the top level, a non iron shirt collection, and a Plus Size Store with a plus size model in the banner. Suits run from 10,999 to 31,999 rupees, EMI starts at 1,625 a month, and the delivery check returns a real date rather than a vague promise.
Discovery is not this brand's problem. Every one of the five got to a product they liked. Then every one of them stopped.
On every suit and every shirt we opened, the product details name one fit and the size chart that opens names a different one. A regular fit suit opens a slim fit chart. An India Fit shirt opens an India Slim Fit chart. The one tool on the page whose entire job is to settle the size question contradicts the garment it belongs to.
Fit is the whole category, and the page will not commit to it.
Tailoring is sold by chest measurement. A man buying a 25,999 rupee suit he cannot try on has exactly one question, and the site answers it three different ways.
The chart contradicts the product. The chart also lists sizes 34 to 50 when the suit is only sold from 38 to 46. And when a size is genuinely out of stock it is not greyed out, it is deleted from the page, so a man who wears a 34 sees a complete looking size row and concludes the brand does not make his size at all.
Then there is the safety net, or rather the absence of one. The returns policy gives 14 days. It appears on no product page, in no cart and on no payment screen. The same policy states that exchanges are not offered at all, and that something bought online cannot be exchanged in a store. For a garment sold by chest measurement, that is the single most expensive sentence on the website.
The brand already knows which store has his size. It just never says so.
Blackberrys has more than 400 exclusive stores and over 1,250 retail touchpoints. Its own store locator publishes, per store, which sizes are in stock, with prices.
Nothing on blackberrys.com reads that feed. A man looking at a suit is shown no store, no stock and no phone number, while a page three clicks away knows the garment is on a rail two kilometres from him. The locator itself sits behind a single footer link, on a different subdomain, behind a search that returns nothing for Connaught Place while holding a Connaught Place store in its own data.
The competitor doing this well is Louis Philippe, which names the nearest store on the product page, lists the sizes that store holds, prints its phone number and offers delivery in four hours. Raymond, with the largest store estate in the category, carries no locator on its website at all. This is not a race everyone else has already won.
Any basket with two or more items earns an automatic five percent. It applies in the cart and is lost at the payment screen, while the cart total is still visible behind the panel. The shopper who sees this is the most valuable one in the set: a repeat customer with a 10,000 rupee basket, one tap from paying.
Every one of these is a setting, a field or a line of copy.
None of the four problems above needs a redesign. The size chart needs to read the product's own fit field. The returns line needs to be printed where people are shopping. The store stock already exists and needs to be displayed. The discount needs to survive one hand off between two systems.
That is the encouraging part of this report and the frustrating part at once. The brand has already paid for all of it: the stores, the stock feed, the returns policy, the discount, the 3,700 referring domains, the first position on Google for blazer. Almost none of it reaches the shopper at the moment he decides.
One warning about everything you have just read.
No analytics, search console, store platform or session recording data was available to any of the five audits. Every statement in this report is something we watched happen on the live site, not something we counted across thousands of visitors.
That makes the findings credible and the sizes unknown. We can tell you the cart loses 520 rupees at the payment screen. We cannot yet tell you how many baskets that costs per week, because the payment screen reports nothing back. The first recommendation in this report is therefore not a design change. It is turning the measurement on, so that everything after it can be proved.
The range is right and the brand is known. The information around the product is not, and nothing currently proves what fixing it is worth.
A 35 year old menswear brand with 400 stores, selling online as though it had none.
- Where the brand sits on price and position.
- Six assets it already owns.
- The three brands it is measured against.
- What the comparison says about the gap.
Mass premium menswear, crossing into premium at the suiting end.
Blackberrys was founded in 1991 and trades under Mohan Clothing Co. Pvt. Ltd. It sells formal and wedding suits, blazers, shirts, trousers, khakis, jeans, footwear and winterwear, with tailored occasion wear as the hero category across the home page, the Wedding Store and the Winter Store.
| What it sells | Where the prices sit |
|---|---|
| Shirts | 1,999 to 3,599 rupees |
| Trousers and khakis | 1,995 to 3,685 rupees |
| Blazers | from 6,999 rupees |
| Two piece suits | 13,999 to 17,999 rupees |
| Three piece suits | up to 25,999 rupees |
Across the full catalogue the middle price is 3,159 rupees, with a range from 299 to 40,555. That band sets the expectation: at these prices an Indian shopper expects to see store stock, to be able to collect or reserve, and to be able to swap a size.
Six assets the brand already owns and pays for.
These matter because most of this report is about surfacing them rather than building anything new.
Three brands a man actually cross shops when buying a formal shirt or a wedding suit.
| Brand | Why it is in the set | How it compares |
|---|---|---|
| Louis Philippe | The closest substitute: premium Indian formalwear, a similar store estate, the brand most often weighed against Blackberrys. | Shows store stock on the product page, delivers in four hours, advertises a 15 day free exchange. |
| Raymond | The default cross shop for wedding and formal suiting, with the largest tailoring heritage in the category. | No pincode check and no store locator on its website, but states its return window and payment terms on the product page. |
| Arrow | Premium formal menswear at an overlapping price band with a national store estate. | Store locator and loyalty in the header, a chat channel on the page, and a 15 day return or exchange. |
At this price band, in this category, the shopper is comparing. Louis Philippe answers the fit and availability question on the product page. Raymond answers the policy question there. Blackberrys answers neither, while holding better store data than either of them.
Five men found a suit they wanted. Four reached the payment screen. None of them bought.
- How likely each of the five was to buy.
- What they said while they shopped.
- Where on the journey each one stopped.
- The full step by step walk for each shopper.
- All thirteen findings that came out of it.
Five shoppers, five different reasons to stop.
Each one was given a budget, a reason to shop and a set of worries, then walked through the live store.
| Shopper | Who they are | Chance of buying | Where they stopped | What drew them in | What stopped them |
|---|---|---|---|---|---|
| Arjun | Wedding season suit seeker | 45% | Stopped at payment | Wedding Store in the top menu, a three piece suit at 25,999, delivery by Saturday, EMI at 3,250 a month | A regular fit suit that opens a slim fit size chart, no reviews, no exchange shown |
| Rohan | First job formal builder | 55% | Stopped at payment | The interview suit article, a 12,999 Must Haves suit, and a welcome code that takes 1,299 off in the cart | The same review sentences under different names on a 4.9 star suit |
| Vikram | Corporate wardrobe replenisher | 50% | Stopped at payment | Non iron shirts in one click, filters that work, and an automatic five percent off for buying three | The cart said 9,877 and the payment screen opened at 10,397 |
| Meera | Thoughtful gift buyer | 40% | Stopped at the product page | Affordable knitwear at 2,199, free shipping, and a 14 day return policy once she found it | Every photo shows a sleeveless vest. The title says sweater. |
| Sanjay | Plus size fit seeker | 35% | Bought one of three items | A dedicated Plus Size Store in the menu with a plus size model, and size 48 in stock on core shirts | The store's first product is a pair of trousers that stops at waist 38 |
| Average | 45% | Across all five, after the full six step walk |
The details say Regular Fit. The chart says Slim Fit. So am I a 40 or a 42?Arjun, the wedding suit seeker, 45 percent
I read the same review twice, under two different names. What is the 4.9 worth now?Rohan, the first job builder, 55 percent
The cart said 9,877. This screen says 10,397. Where did my 520 rupees go?Vikram, the wardrobe replenisher, 50 percent
Every photo shows a vest. The title says sweater. He hates vests.Meera, the gift buyer, 40 percent
It says Plus Size Store. The first trousers stop at waist 38.Sanjay, the plus size seeker, 35 percent
A straight answer about size at the moment of choosing. Four of the five named it themselves. The fifth, the gift buyer, could not tell from the page whether she was buying a sweater or a sleeveless vest.
All five found a suit. Four reached the payment screen. None finished.
What each shopper did, saw and felt, step by step.
The line above makes the argument. These carry the evidence behind it. Open one shopper at a time.
29, solution aware. Considered and visual. Medium price sensitivity.
One statement wedding suit or achkan, plus shoes. Budget 15,999 to 25,999.
The Wedding Store as a first level menu item, fabric composition on the page, a real delivery date by pincode, free alteration in stores.
Fit off the rack. Whether a 26,000 rupee suit can be exchanged. Whether it arrives before the wedding. Zero reviews.
The hero is knitwear, not weddings, but WEDDING STORE in the menu says he is in the right place.
Wedding Store then Suits opens a 640px banner with no suits in view. The tab title promises up to 40 percent off. The suits are full price.
Scrolls three piece suits from 10,999 to 31,999. Picks the navy Xenius at 25,999.
Delivery by Saturday is reassuring. Then the details say Regular Fit, the size chart says Slim Fit, the specification says one piece, and there are no reviews.
Adds size 40. The drawer shows free shipping and suggests a code he had not seen. One code warns the item becomes non returnable.
Buy Now asks for a mobile number first. He still does not know if 40 is right, or whether he can exchange it.
Next, Rohan at 55 percent. First job formal builder, and he stops for a different reason.
23, problem aware. Guidance seeking. High price sensitivity.
A first navy or grey suit plus two or three formal shirts. Around 12,999 for the suit.
The job interview suit article, the Must Haves range, a 4.9 star rating, and a welcome code that worked immediately.
Buying the wrong size or fit. Overspending. Not knowing what to pair. Whether the reviews are real.
No office or first suit cue in the menu. He scrolls and spots a blog card on interview suits.
A phone number popup opens and takes the click meant for that article. The article gives good advice but links products only as inline text.
Reaches navy suits and picks the Jerret at 12,999, rated 4.9 from 15 reviews.
The price and the EMI fit his budget. Then on review page three he finds the same sentences he read on page one, under different names.
Adds size 38 and types the welcome code. 1,299 comes off. The cart suggests another suit and belts, but no shirt or tie.
The total holds at 11,699, then the screen asks for his phone number. The price is fine. His trust in the reviews is not.
Next, Vikram at 50 percent. Corporate wardrobe replenisher, and he stops for a different reason.
38, most aware and a repeat buyer. Fast and transactional. Low to medium price sensitivity.
Three or four non iron office shirts in one quick session. Basket around 10,000 to 15,000.
A one click path to non iron shirts, filters with removable chips, a visible offer ladder, express delivery.
Wasting time on filters. His size being out of stock. The price changing at the last step.
Ignores the hero, closes the popup, goes straight to the collections menu.
Non iron shirts in one click. The filters list khakis and trousers inside a shirt collection, and fits are named by code.
Filters to formal shirts in size 42 and gets 39 clean results. Picks three shirts at 3,199 each.
The offer ladder pushes him to spend more. The India Fit shirt opens an India Slim Fit chart.
The cart page shows a discount tag on every line and a total of 9,877. Nothing says what the discount is, and the checkout button label is cut off.
The payment screen opens at 10,397 with the discount gone, while the cart total is still visible behind it.
Next, Meera at 40 percent. Thoughtful gift buyer, and he stops for a different reason.
34, product aware. Emotional and visual. Medium price sensitivity.
A premium looking gift for her husband that can be exchanged. Budget 2,500 to 7,000.
Bestsellers and ratings, easy exchange, a delivery date, gift options.
Buying the wrong size for someone else. Exchange hassle. The gift arriving late. The product not matching the photos.
Wedding season hero, then the popup. She closes it and loses the code.
Searches gift for husband and gift card. Both return no results. Searches sale and gets a mixed grid. Finds no sale link in either menu.
Falls back to the Winter Store and browses 82 sweaters from 1,833 to 4,845.
Every photo shows a sleeveless vest. The title, the highlights and the description never say sleeveless. The sizing tool asks for weight in pounds.
Adds a large. The drawer has no gift wrap, no message and no way to hide the price. The offer ladder starts at 6,999, so her 2,199 basket gets nothing.
She finds the 14 day return only by digging into the footer. She still does not know whether she is buying a vest or a sweater.
Next, Sanjay at 35 percent. Plus size fit seeker, and he stops for a different reason.
46, solution aware. Considered and evidence seeking. Medium to low price sensitivity.
Formal shirts, trousers and a blazer that fit at 46 to 48, waist 42 and above.
A Plus Size Store link in the main menu, a plus size model in the banner, size filters that default to in stock, size 48 on core shirts.
That the range is only basics. Sizes listed but sold out. Slim cuts. Return hassle.
Slim models only on the homepage. He closes the popup and looks for a big and tall link.
Finds the Plus Size Store under collections, with a plus size model in the banner. Finally, a brand that caters to him.
The first product is black khakis whose sizes stop at waist 38. Plus sizes are hidden rather than shown as sold out.
Filters to formal shirts in 48 and finds about 15. Size 48 is available on the Sailor shirt, but the chart says India Slim Fit and two reviews are word for word identical.
Adds one shirt in size 48. Gives up on the trousers and the blazer.
Checks out at 2,725 instead of the 12,000 wardrobe he came for.
That is all five. Four of them stopped at the payment screen, each over something the page could have told them earlier.
Thirteen findings from the five journeys.
A shopper choosing a 25,999 rupee suit cannot work out his size.
The product details say Regular Fit. The size chart that opens is titled Slim Fit. The same mismatch appears on a second suit and on two India Fit shirts, and the chart lists sizes 34 to 50 when only 38 to 46 is sold.
Four of the five shoppers stalled here. The brand's own size recommendation tool reads from this same chart, so it inherits the error.
The same review appears twice, under two different names.
On the bestselling 12,999 rupee suit, four sentence pairs repeat word for word across review pages one and three. Only one of the fifteen reviews is marked as a verified buyer.
Shoppers who spot one copied review start doubting the store rating too, which is the one piece of proof on this site that is genuinely strong.
The basket total rises by 520 rupees at the last step.
A cart holding three non iron shirts shows 9,877 with an automatic five percent discount applied. The payment screen then opens at 10,397 with the discount gone, while the cart total is still visible behind it.
The shopper who hit this was the most valuable of the five: a repeat customer with a ten thousand rupee basket, one tap from paying.
The Plus Size Store opens with trousers that stop at waist 38.
Across the store, size 46 is in stock on 42 of 225 items, size 48 on 15 of 136, and size 50 on none of 21. Sold out sizes are removed from the page rather than shown.
He bought one shirt instead of the shirts, trousers and blazer he came for, and concluded the store is the regular range relabelled.
The 14 day return promise never appears while anyone is shopping.
The policy exists on a footer page. No product page, cart drawer, cart page or payment screen opened in two audits carried a returns or exchange line.
Every one of the five shoppers named this as their biggest worry. The answer already exists. It is just filed where nobody shopping will find it.
Two complete shopping funnels cannot be reached from the menu.
A sale collection holding more than 250 products and a My First Suit page are both built, but render at zero width on desktop and appear in neither menu.
We recommend adding Sale as a top level menu item and My First Suit under Collections, and pointing the search term sale at the sale collection.
Searching for a gift returns nothing at all.
Gift for husband and gift card both return no results. There is no gift edit, no gift card and no gift guide by price anywhere on the site.
We recommend mapping gift queries to bestsellers, correcting the stray quote mark in the no results message, and adding a gifts page banded by price.
Three piece suits say they contain one piece.
Three of the four three piece suits checked, including the 25,999 rupee Xenius, list the number of pieces as one.
We recommend correcting the field across every suit and writing it in words: three pieces, jacket, waistcoat and trousers.
A sleeveless vest is sold as a sweater.
All eight photographs on the 2,199 rupee Less product show a sleeveless knit vest. The title, the highlights and the description never use the word sleeveless, and the styling tip suggests pairing it with a tee.
We recommend adding sleeveless to the name and highlights of every vest, and giving vests their own filter value under sweaters.
The discount codes change between the product page and the cart.
The product page offers three codes. The cart offers a different set, and the small print on one of them makes the item non returnable.
We recommend one coupon set across the product page, the cart and the payment screen, with return eligibility stated on every code.
A popup opens mid visit and takes the shopper's click.
A phone number popup offering ten percent off appears between seven and twelve seconds into a first visit. Twice it opened as our shopper was clicking something else, and the click was lost.
We recommend showing it on exit intent or after thirty seconds, and showing the code again in the cart for anyone who closed it.
Collection titles promise discounts the page does not carry.
The wedding suits tab title promises up to 40 percent off. One of the 130 suits on the page carries a markdown.
We recommend removing the discount claim from the titles of collections that are not on sale.
The main button on the cart page has its label cut off.
The checkout button is a 45px box whose label wraps onto two lines, and the second line is clipped. Each line in the cart carries a discount tag with nothing explaining what triggered it.
We recommend widening the button so the label fits on one line, and adding a line above the total explaining the five percent multi buy.
Every page type checked piece by piece, including the parts that already work.
- Every element examined, page type by page type.
- What the screenshots corrected in the written audit.
- All fifteen findings, and two rebuilt blocks showing what the fix looks like.
What each page type actually carries, including the parts that work.
Open any page type. Every row is a real observation, and the clean rows are there on purpose: showing what works is what makes the criticism worth reading.
Home page3 of 7 clean
| Element examined | What is actually there | Verdict |
|---|---|---|
| Announcement bar | There is no bar above the header. The first screen carries the logo, search, wishlist and bag, then the hero. | Missing |
| Hero | A full width wedding season image with a Buy Now button and carousel dots. It loads cleanly and reads well on a phone. | Clean |
| Category entry | No category strip under the logo. The range is only reachable by opening the menu. | Missing |
| Bestsellers | A Bestseller and This Is New tab pair sits directly under the hero, with product cards beneath. | Clean |
| Proof | The 4.4 star rating from 5,864 reviews, summarised by AI, sits near the footer, roughly 8,000px down. | Buried |
| Mobile bottom bar | A persistent bar carries Home, New, Orders, Account and Chat. It overlaps content at the foot of the screen. | Mixed |
| Footer | Quick links cover Track My Order, Return, Support, Our Policy, FAQs and Bulk Orders. Blackberrys Club appears under Information. | Clean |
Collection page2 of 7 clean
| Element examined | What is actually there | Verdict |
|---|---|---|
| Banner | A banner fills roughly the first third of the screen before any product appears. | Heavy |
| Breadcrumbs | No trail anywhere on the page. Nothing shows where the shopper is in the catalogue. | Missing |
| Product count | No count of how many products the collection holds. | Missing |
| Filter and sort | A Filter and Sort By bar sits above the grid, with a two up and four up view toggle. | Clean |
| Quick filters | No size, colour or price chips outside the filter panel, so narrowing always costs a panel open. | Missing |
| Product cards | Cards carry a New Arrival flag, a wishlist heart, a price and a star rating with a review count. | Clean |
| Add to bag | No add to bag control on any card. Every add costs a page load. | Missing |
Product page3 of 8 clean
| Element examined | What is actually there | Verdict |
|---|---|---|
| Breadcrumbs | A home icon and the product name sit directly under the header. | Clean |
| Gallery | Six thumbnails with a zoom control, showing front, back, side, worn and folded views. | Clean |
| Share | A share control sits on the gallery. | Clean |
| Size chart | The chart opens on a different fit from the one the product details name. | Broken |
| Reviews | Review text repeats word for word under different names on bestselling items. | Broken |
| Returns | No returns or exchange line anywhere near the price, the buttons or the delivery check. | Missing |
| Delivery check | A pincode check returns a real date, but sits below the add to cart button and below the coupon block. | Buried |
| Sticky add to cart | The sticky price and button appear only after three or four screens of scrolling. | Late |
Cart2 of 6 clean
| Element examined | What is actually there | Verdict |
|---|---|---|
| Shipping message | Free Shipping and Express Delivery Available run across the top of the bag drawer. | Clean |
| Coupon entry | The drawer carries a coupon field and a five offers available link. | Clean |
| Cross sell | You May Also Like offers another shirt. The Finishing Touch offers belts. | Mixed |
| Security | A continue to safe checkout line appears above the button, but no payment or security badges. | Mixed |
| Returns | No returns or exchange line in the drawer or on the cart page. | Missing |
| Empty state | An empty bag shows an illustration, one line of text and a Shop Now button. No products, no recently viewed. | Missing |
Search1 of 3 clean
| Element examined | What is actually there | Verdict |
|---|---|---|
| Empty state | Opening search shows Popular Choices chips and a Recommended For You grid with four suits and prices. | Clean |
| Recent searches | No record of what the shopper looked for before. | Missing |
| Gift queries | Gift for husband and gift card both return no results. | Broken |
404 page0 of 1 clean
| Element examined | What is actually there | Verdict |
|---|---|---|
| Recovery | A plain 404 message with a single Continue Shopping button. No products, no search, no popular links. | Missing |
The written audit recorded a missing live chat, a missing bestsellers list, and a mispositioned announcement bar. The captures show a Chat entry in the mobile bottom bar, a Bestseller and This Is New tab pair directly under the hero, and no announcement bar at all rather than a misplaced one. Where the evidence and the write up disagreed, we went with the evidence.
Fifteen findings from the page review.
Nothing on the first screen says why to trust the store.
There is no bar above the header. Free shipping is first mentioned in the cart drawer, and the 4.4 star rating from 5,864 reviews sits near the footer, roughly 8,000px down.
The brand has the proof: two million customers, a 4.4 rating from real reviews, three day delivery and a 14 day returns window. None of it is on the first screen.
There is no trail showing where the shopper is.
No breadcrumbs appear anywhere on the collection page, so there is no way back up to a parent category except the menu.
No page says how many products it holds.
Collection pages show a grid with no count, and the wedding suits page runs roughly 21,700px of continuous scroll.
We recommend showing the product count beside the filter bar, so a shopper knows the size of what he is browsing.
Narrowing a collection always costs a panel open.
A Filter and Sort By bar sits above the grid, but there are no size, colour or price chips outside it.
We recommend surfacing the three filters shoppers use most as chips on the page itself.
Nothing can be added to the bag from a collection page.
Cards carry a flag, a wishlist heart, a price and a star rating, but no add to bag control. Every add costs a page load.
We recommend an add to bag control on the card, with a size step for products that need one.
The sticky buy bar only appears after three or four screens.
The sticky price and button are present, but do not appear until well down the page, so the shopper who decides early has to scroll back.
We recommend showing the sticky bar as soon as the main add to cart button leaves the screen.
The range is only visible once a menu is opened.
There is no category strip beneath the logo on the home page.
We recommend a row of top category tiles directly under the header.
The cart says safe checkout but shows nothing that proves it.
A continue to safe checkout line sits above the button. There are no payment method marks or security badges in the drawer or on the cart page.
We recommend showing accepted payment methods and a security mark next to the checkout button.
An empty bag offers nothing to buy.
The empty state shows an illustration, one line of text and a Shop Now button. No bestsellers, no recently viewed, no recommendations.
Search does not remember what the shopper looked for.
The search panel opens with popular choices and a recommended grid, which works well, but carries no record of previous searches.
A wrong address ends the visit.
The 404 page carries a short message and a single Continue Shopping button. No products, no search box and no popular links.
The visible description does little selling.
The page carries the specification but little writing about the garment itself, so the shopper weighing two similar shirts has nothing to choose between them on.
We recommend two or three plain lines above the specification: the fabric, how it wears, and who it suits.
A brand founded in 1991 never tells its story.
There is no About Us or Our Story section reachable from the home page.
We recommend a short brand story linked from the home page and the footer, covering the heritage and the tailoring.
The cart suggests more of what is already in it.
Alongside a shirt the cart offers another shirt under You May Also Like, and belts under The Finishing Touch.
We recommend complete the look recommendations that finish the outfit, and guided bundles such as a suit with a shirt and a tie.
There is no way to see a whole outfit.
No shop by look section exists, so a shopper who likes a styled photograph cannot buy what is in it.
We recommend a shop by look section built from the photography the brand already shoots.
Nothing here is slow to load. The pages are slow to react when somebody taps them.
- What was measured, and on whom.
- The full set of numbers, with what each one means.
- Why every failure is the same kind of failure.
- All four findings from the speed test.
Real visitors, 28 days, mobile and desktop.
This is field data from the Chrome User Experience Report, which is what Google uses. A laboratory test on a throttled phone was also run, and is reported at the foot of this section.
Loading is fine. Responding to a tap is not.
| Scope | Device | Main content | First paint | Movement | Tap response | Server |
|---|---|---|---|---|---|---|
| Whole site | Mobile | 2.2spasses | 1.8spasses | 0.01passes | 262msfails | 986msfails |
| Whole site | Desktop | 1.2spasses | 869mspasses | 0passes | 110mspasses | 406mspasses |
| Home page | Mobile | 2.2spasses | 1.6spasses | 0.01passes | 261msfails | 870msfails |
| Home page | Desktop | 1.7spasses | 1.1spasses | 0passes | 146mspasses | 370mspasses |
| Collection | Mobile | 1.4spasses | 1.3spasses | 0.04passes | 197mspasses | 1.0sfails |
| Collection | Desktop | 906mspasses | 713mspasses | 0.14fails | 106mspasses | 150mspasses |
| Product | Mobile | 1.4spasses | 1.2spasses | 0passes | 230msfails | 465mspasses |
What the columns mean. Main content is how long until the biggest thing on screen has loaded, and should be under 2.5 seconds. First paint is how long before anything appears, under 1.8 seconds. Movement is how much the page jumps while it settles, under 0.1. Tap response is how quickly the page reacts to a tap, under 200 milliseconds. Server is how long before the first byte arrives, under 0.8 seconds. The product page has no desktop field data, because not enough desktop visitors reached it in the window.
Nothing on this site is slow to appear. Main content loads in 2.2 seconds on mobile and movement is almost zero. Every failure is the page being slow to react once a shopper taps something, and on mobile that lands on the size selector and the add to cart button.
Four findings from the speed test.
The home page is slow to react when it is tapped.
Real visitor data records a tap response of 261 milliseconds on the home page and 262 across the site, against a 200 millisecond pass mark. Desktop passes everywhere.
The cause is long running third party scripts rather than anything the site itself draws. Loading and stability are genuinely sound: main content at 2.2 seconds on mobile, movement at 0.01.
The product page lags at the moment of choosing a size.
Tap response on the product page is 230 milliseconds against the same 200 millisecond mark. Collection pages pass at 197.
We recommend the same script work on the product template, since this is where size selection and add to cart happen.
The server is slower to answer phones than desktops.
Server response runs between 0.87 and 1.0 seconds on mobile across the site, the home page and collection pages, against a 0.8 second mark. Desktop answers in 0.37 to 0.41.
We recommend finding what the mobile path asks for that desktop does not, and caching what does not change.
Collection pages shift while they settle on desktop.
Layout movement measures 0.14 on desktop collection pages against a 0.1 mark. Mobile is fine at 0.04.
We recommend reserving space for the banner and the grid so the page does not move under the cursor.
More than 400 stores, and the website sells as though none of them existed.
- The eight things a shopper should be able to do.
- How the brand scores against three rivals.
- The stock feed that already exists and is never shown.
- All seventeen findings, and the one that pays back fastest.
Eight things a shopper should be able to do when a brand has 400 stores.
Each one was tested live on the site, the locator and the payment screen, at four different order values. Three competitors were tested the same way.
Scored 0 to 3, where 3 means it works and the shopper can find it.
| Can a shopper do this | State | Score | What we found |
|---|---|---|---|
| Can a shopper see if his size is in a store near him | Buried | 1 of 3 | The locator publishes size and stock per store. Nothing on the website reads it. |
| Can he pick it up, reserve it, or get it today | Absent | 0 of 3 | One delivery option at checkout. No pickup, no reserve, no ship from store. |
| Can he return or exchange across channels | Refused | 1 of 3 | The policy states an online order cannot be returned or exchanged in a store, and that no exchange is offered. |
| Is the store estate a selling channel | Buried | 1 of 3 | The locator sits behind one footer link, and its search fails on major localities. |
| Is he one customer online and in store | Fragmented | 1 of 3 | Three identity systems. Loyalty points cannot be seen or spent online. |
| Can anyone see a store order online | Online only | 1 of 3 | Tracking accepts an order or AWB number. A store invoice cannot be looked up. |
| Can he pay the way he wants | Works, with a gap | 2 of 3 | A broad tender set, but cash on delivery disappears above roughly 2,000 rupees. |
| Is the brand present beyond its own site | Partial | 1 of 3 | Strong on marketplaces. No own app, no conversational channel. |
One brand has pulled clear. The rest leave their stores idle.
Louis Philippe names the nearest store on the product page, lists the sizes it holds, prints its phone number and offers delivery in four hours. Raymond, with the largest store estate in the category, carries no locator on its website at all. This is not a category where everyone else is already ahead. It is one where a single brand has pulled clear.
It sits on a different subdomain, behind a single footer link, behind a search that returns nothing for Connaught Place while holding a Connaught Place store in its own data. The infrastructure problem is already solved. The surfacing problem is not.
Seventeen findings from the store connection audit.
The brand knows which store has your size, and never says so.
The store locator publishes size and stock per outlet, with price. Nothing on blackberrys.com reads that feed, so the product page shows no store, no stock and no phone number.
He is deciding between buying blind and driving somewhere. The site gives him neither the confidence to do the first nor the information to do the second.
Sizes that are out of stock are deleted from the page.
On a 25,999 rupee suit, sizes 34 and 36 are removed from the size row entirely. The shopper sees a complete looking page with no gap.
Every competitor tested shows unavailable sizes rather than hiding them.
A sold out product still offers a live buy button.
On a sold out 13,999 rupee suit the add to cart control is correctly disabled, while the separate buy now button beside it stays active.
We recommend disabling the buy now and sticky controls in the sold out state, and replacing the dead end with a notify me.
The returns page contradicts itself about exchanges.
The page states that exchanges are not offered and that an online order cannot be exchanged in a store, while its own steps tell the customer to pay the difference, and discounted items carry a no return only exchange tag.
Louis Philippe and Arrow both advertise a 15 day free exchange on the product page. A refund returns the cash. An exchange keeps the revenue and usually adds a store visit.
Cash on delivery quietly disappears on the expensive products.
It is offered at 599 and 1,999 rupees and absent at 6,649 and 25,999. No threshold is stated on the product page, in the cart, in the FAQ or at the payment step.
A shopper who intends to pay cash finds out at the last screen, across the entire blazer and suit range, which is the highest value part of the catalogue.
The delivery check hangs with no answer and no error.
On one pincode the check span indefinitely across two attempts. Pressed before a size is chosen it returns an error below the fold, where the shopper will not see it.
We recommend an explicit message when an address cannot be served, removing the size requirement, and moving the check above the add to cart button.
A 400 store estate is one footer link away from the shopper.
The locator is reachable only from a footer link reading Visit Our Store, and opens on a different subdomain with a different design.
We recommend a Stores entry in the site header, and a find this in a store near you link on every product page.
The store finder cannot find one of Delhi's main retail districts.
Searching the locator for Connaught Place returns no results, while the same locator holds a Connaught Place store in its own data.
We recommend fixing the locality search for the top 50 retail localities, starting with the ones that already hold a store.
There is no way to get a suit this week.
No pickup, no reserve in store, no ship from store, no same day. The payment screen offers one line: standard delivery.
Louis Philippe fulfils in four hours from a named nearby store. This is the most urgent and highest value demand in the category, and Blackberrys currently has no answer to it.
Demand for a sold out size is thrown away in silence.
There is no back in stock alert anywhere on the site, on sold out products or on missing sizes.
We recommend a notify me capture on every unavailable size and every sold out product. It is the cheapest way to hold demand the brand has already paid for.
Loyalty points cannot be seen or spent online.
No balance, no tier and no redemption field anywhere on the site. The programme's own terms make store redemption subject to retailer discretion, and it goes by three different names across the brand's own pages.
A loyalty currency that cannot be seen online and may be refused at the counter is worse than none, because the customer finds out at the till.
A store purchase has no digital existence.
Order tracking accepts an order number or a courier number, both of which only exist for a website order. There is no invoice or mobile lookup.
We recommend lookup by invoice and mobile number, so the free alteration entitlement does not depend on the customer keeping a piece of paper.
Taking the free alteration quietly ends the right to return.
The product page promotes free alteration within 180 days. The returns policy states that altered garments cannot be returned or refunded. The product page does not say so.
We recommend adding the caveat where the service is promoted, so the customer learns it before the scissors rather than after.
Nothing a store does can be booked.
No store page lists its services, and all five service page addresses tested on the main site return a 404. Free alteration, fit consultation and wedding appointments are all real reasons to visit.
We recommend listing services on each store page and making them bookable, with a chat channel the shopper can open.
An order cannot be marked as a gift.
The cart offers coupons and recommendations, but no wrap, no message and no way to hide the price on the invoice.
We recommend a gift toggle in the cart covering wrap, a message and a price free invoice, plus a digital gift card.
A coupon from the website may be refused at the counter.
Product pages present codes without qualification, while the FAQ states that online and offline offers vary because they are different business channels.
We recommend saying on the product page which codes work in stores, or bringing the two sets into line.
The payment screen asks for a phone number before answering anything.
The only field on the first screen is a mobile number. There is no final total, no delivery date and no returns line, and the marketing consent box is already ticked.
We recommend showing the total, the delivery date and the returns line before the phone step, and leaving consent unticked.
Ask an assistant which brands make good suits and Blackberrys is named. Ask it what to wear and it is not.
- How often the brand is named, by type of question.
- What the engines actually answered, reproduced.
- Why half the catalogue is invisible to a shopping assistant.
- All eleven findings, and the one that gates the rest.
Named in 27 of 30 brand questions, and 2 of 19 advice questions.
| What the shopper asked | Named in |
|---|---|
| Asked for a list of brands | 27 of 30 |
| Asked about the brand directly | 12 of 12 |
| Asked where to buy | 8 of 15 |
| Asked to compare brands | 6 of 14 |
| Asked for advice | 2 of 19 |
Twenty questions were put to five engines under identical conditions on one day, which is 90 answers. The brand wins the question a shopper asks when he already thinks in brands. It loses the question that comes before it.
Six answers, reproduced.
These are the actual responses, not a count of them.
| The question | Engine | Was the brand named | What happened |
|---|---|---|---|
| Best men's suit brands in India | Google AI Overview | Named fourth, after Raymond, Louis Philippe and Van Heusen. | The two citation cards went to Louis Philippe's own store and a Reddit thread. Neither sends the shopper to blackberrys.com. |
| What should an Indian groom wear for a wedding reception | Google AI Mode | Not named. | The answer recommends a tuxedo, a bandhgala, an Indo Western sherwani and a velvet blazer set. Blackberrys sells all four. |
| Which men's shirt fabric is best for Indian summers | Perplexity | Not named. | The answer recommends linen and cites three other brands. Blackberrys has a linen shirts collection. |
| Where to buy men's formal suits online in India | Perplexity | Not named. | The shopping table lists Myntra, Amazon India, Nykaa Fashion, Pantaloons and three more. The brand store is absent. |
| Is Blackberrys a good brand | ChatGPT | Named and positive. | Describes it as a good, fairly established Indian menswear brand, and mid premium rather than luxury. |
| What is Blackberrys return policy | Gemini | Named, and wrong. | States a 15 day return and exchange window. The policy page states 14 days and no exchange. |
Asked about the returns policy, one assistant states a 15 day return and exchange window. The policy page states 14 days and no exchange. A page that contradicts itself produces a wrong answer, and that answer is now circulating where the brand cannot correct it.
Asked for the best men's suit brands in India, Google writes the answer above the results and names Blackberrys fourth. The two citation cards beside it go to Louis Philippe's own store and to a Reddit thread. Being named in the text earns nothing. The citation is the click.
Eleven findings from the visibility audit.
More than half the catalogue cannot be bought.
2,852 of the 5,416 products the catalogue returns have no buyable size, which is 52.7 percent. The sitemaps carry 5,417 addresses, so effectively the whole catalogue is submitted to search engines.
An assistant asked to buy a three piece suit has a better than even chance of landing on something it cannot add to a cart, and will move to a marketplace that can.
The brand is missing from the question shoppers ask first.
Across five AI engines the brand was named in 27 of 30 answers that asked for a list of brands, and in 2 of 19 that asked for advice.
Asked what an Indian groom should wear to a reception, one engine recommends a tuxedo, a bandhgala, an Indo Western sherwani and a velvet blazer set. Blackberrys sells all four.
The brand is absent from almost every source these engines read.
It is strong on 10 of 33,150 source domains cited in this category and missing from 32,188. YouTube cites it 80 times against 1,045 for the nearest group of rivals.
Two of the five engines build their answers from live sources. If the brand is not on the page the engine reads, it cannot be in the answer, however good the product is.
The site's authority sits on the one page that does not sell.
The home page holds 2,600 referring domains. The suits collection holds four, trousers one, and the combined suits and blazers page none.
We recommend linking inward from the home page and the blog, and building one link worthy asset for each priority collection.
Two collection pages account for most of the traffic that was lost.
Organic visits fell about 15 percent while the number of ranking keywords barely moved. The trousers page lost 20,400 monthly visits and the suits page 6,200.
We recommend rebuilding those two pages first, with answer led copy and internal links, since rankings holding while clicks fall points at answers being given above the results.
Shoppers see a star rating that machines cannot read.
Ratings display on collection listings, but the rating is written into the page data on only 2 of the 19 product templates checked. No product carries colour, material or size as structured data.
We recommend publishing the rating and review count on every product page that has them, and adding colour, material and size.
The brand answers to four names and three descriptions.
It appears as BLACKBERRYS, Blackberrys, Blackberrys Menswear and Blackberrys Clothing India. Its own site calls it premium, Wikipedia calls it luxury, and every AI assistant calls it mid premium.
We recommend agreeing one name and one description, then applying both to the site data, the About page and every marketplace listing.
Asked where to buy, assistants send shoppers to marketplaces.
One assistant's shopping table named seven places to buy and did not include the brand's own store. The brand's marketplace page carries a public rating that the brand store does not.
We recommend confirming the shopping feed covers the full in stock catalogue, and publishing the on site reviews so the brand store carries a rating too.
Test products and duplicate names are live in the catalogue.
Three products with test in the name are published, including a 29,489 rupee suit whose title says navy and whose garment is wine. 281 product titles are duplicated.
We recommend removing the test products and correcting the duplicated titles, because these are exactly the fields a shopping assistant matches on.
Search engines are pointed at products that cannot be bought.
All 5,417 product addresses are submitted, including the 2,852 with no buyable size.
We recommend excluding unbuyable products from the sitemap until stock returns, as a holding step while the merchandising decision is made.
A range the brand merchandises cannot be found by its own name.
The non iron shirts collection is live and browsable with 171 products, but no collection address matches that name, and there is no cargo pants collection at all.
We recommend correcting the collection address so the range is findable, and building the missing one.
All 66 recommendations, in one table you can sort and filter.
- Where the recommendations sit, by part of the store.
- The three we would do first, and why those three.
- The full table of all 66, sortable and filterable.
- What we would measure next, with access.
Ten parts of the business, ranked by how many of the 66 recommendations each one carries.
The product page carries the most, which is where the money is decided. Tap any row to filter the table below to that part of the store.
Three recommendations unlock most of the others.
These three come first because everything else compounds on top of them. The first makes the rest measurable. The second and third are the two places where a shopper who had already decided to buy changed his mind.
All 66 recommendations in one table.
All 66, sortable by severity and filterable by part of the store. 13 are critical, 24 are high and 29 are medium. Severity describes what the problem costs, not how much work it is.
| ID | Severity | Page | The finding | What we observed | What we recommend |
|---|---|---|---|---|---|
| 04.1 | Critical | Product page | A shopper choosing a 25,999 rupee suit cannot work out his size. | The product details say Regular Fit. The size chart that opens is titled Slim Fit. The same mismatch appears on a second suit and on two India Fit shirts, and the chart lists sizes 34 to 50 when only 38 to 46 is sold. | We recommend linking every size chart to the product's own fit field, and trimming each chart to the sizes actually sold. This belongs before any size recommendation tool, because that tool reads the same chart. |
| 04.2 | Critical | Product page | The same review appears twice, under two different names. | On the bestselling 12,999 rupee suit, four sentence pairs repeat word for word across review pages one and three. Only one of the fifteen reviews is marked as a verified buyer. | We recommend removing the duplicated text, showing the share of reviews from verified buyers, and asking recent buyers for photo reviews. This is a brand trust question, not a design one. |
| 04.3 | Critical | Checkout | The basket total rises by 520 rupees at the last step. | A cart holding three non iron shirts shows 9,877 with an automatic five percent discount applied. The payment screen then opens at 10,397 with the discount gone, while the cart total is still visible behind it. | We recommend carrying the automatic discount into the payment screen, or showing the discounted total before the mobile number step. |
| 07.1 | Critical | Product page | The brand knows which store has your size, and never says so. | The store locator publishes size and stock per outlet, with price. Nothing on blackberrys.com reads that feed, so the product page shows no store, no stock and no phone number. | We recommend reading the existing feed onto the product page: available at three stores near you, with the sizes each holds and the store's number. |
| 07.2 | Critical | Product page | Sizes that are out of stock are deleted from the page. | On a 25,999 rupee suit, sizes 34 and 36 are removed from the size row entirely. The shopper sees a complete looking page with no gap. | We recommend showing unavailable sizes greyed out, each with a notify me option and a find in store link. |
| 07.3 | Critical | Product page | A sold out product still offers a live buy button. | On a sold out 13,999 rupee suit the add to cart control is correctly disabled, while the separate buy now button beside it stays active. | We recommend disabling the buy now and sticky controls in the sold out state, and replacing the dead end with a notify me. |
| 07.4 | Critical | Site wide | The returns page contradicts itself about exchanges. | The page states that exchanges are not offered and that an online order cannot be exchanged in a store, while its own steps tell the customer to pay the difference, and discounted items carry a no return only exchange tag. | We recommend rewriting the page as one table by channel, then introducing a size exchange on online orders. In tailoring the fear of being stuck with the wrong size is the largest single reason a purchase is not made. |
| 07.5 | Critical | Checkout | Cash on delivery quietly disappears on the expensive products. | It is offered at 599 and 1,999 rupees and absent at 6,649 and 25,999. No threshold is stated on the product page, in the cart, in the FAQ or at the payment step. | We recommend stating the limit on the product page and in the cart, then testing whether it can be raised on suits. |
| 08.1 | Critical | Product page | More than half the catalogue cannot be bought. | 2,852 of the 5,416 products the catalogue returns have no buyable size, which is 52.7 percent. The sitemaps carry 5,417 addresses, so effectively the whole catalogue is submitted to search engines. | We recommend one rule for those products: unpublish them, redirect them to the parent collection, or keep them live with a working back in stock signup. |
| 09.1 | Critical | Measurement | None of this can currently be proved to have worked. | No analytics, search console, store platform or session recording data was available to any of the five audits. | We recommend read access to all four, and a four week baseline recorded before any change below is made. |
| 09.2 | Critical | Product page | The delivery check's worst outcome is invisible. | When the check hangs it records nothing, so nobody knows how many shoppers give up there. | We recommend four events on that control: check started, date returned, no result, and blocked because no size was chosen. |
| 09.3 | Critical | Checkout | The two clearest money leaks produce no data. | The 520 rupee price rise and the silent loss of cash on delivery both happen inside a checkout that reports nothing back. | We recommend step level tracking through the payment flow, including when a discount is applied or dropped and which tenders were shown. |
| 09.4 | Critical | Site wide | Nothing connects a website visit to a store purchase. | There is no shared identifier, so revenue the website sends into 400 stores measures as zero. | We recommend capturing the loyalty identifier or mobile number at the till, and tagging clicks on any store module on the site. |
| 04.4 | High | Collection page | The Plus Size Store opens with trousers that stop at waist 38. | Across the store, size 46 is in stock on 42 of 225 items, size 48 on 15 of 136, and size 50 on none of 21. Sold out sizes are removed from the page rather than shown. | We recommend limiting the store to products that have at least one plus size in stock, and sorting by that stock. |
| 04.5 | High | Product page | The 14 day return promise never appears while anyone is shopping. | The policy exists on a footer page. No product page, cart drawer, cart page or payment screen opened in two audits carried a returns or exchange line. | We recommend one line under the delivery check and above the cart button: 14 day easy returns, free alteration at Blackberrys stores. |
| 04.6 | High | Navigation | Two complete shopping funnels cannot be reached from the menu. | A sale collection holding more than 250 products and a My First Suit page are both built, but render at zero width on desktop and appear in neither menu. | We recommend adding Sale as a top level menu item and My First Suit under Collections, and pointing the search term sale at the sale collection. |
| 04.7 | High | Search | Searching for a gift returns nothing at all. | Gift for husband and gift card both return no results. There is no gift edit, no gift card and no gift guide by price anywhere on the site. | We recommend mapping gift queries to bestsellers, correcting the stray quote mark in the no results message, and adding a gifts page banded by price. |
| 05.1 | High | Home page | Nothing on the first screen says why to trust the store. | There is no bar above the header. Free shipping is first mentioned in the cart drawer, and the 4.4 star rating from 5,864 reviews sits near the footer, roughly 8,000px down. | We recommend a slim bar across the top carrying free shipping, the delivery promise, the returns window and the rating. |
| 05.2 | High | Collection page | There is no trail showing where the shopper is. | No breadcrumbs appear anywhere on the collection page, so there is no way back up to a parent category except the menu. | We recommend a breadcrumb trail on every collection page, matching the one the product page already carries. |
| 05.3 | High | Collection page | No page says how many products it holds. | Collection pages show a grid with no count, and the wedding suits page runs roughly 21,700px of continuous scroll. | We recommend showing the product count beside the filter bar, so a shopper knows the size of what he is browsing. |
| 05.4 | High | Collection page | Narrowing a collection always costs a panel open. | A Filter and Sort By bar sits above the grid, but there are no size, colour or price chips outside it. | We recommend surfacing the three filters shoppers use most as chips on the page itself. |
| 05.5 | High | Collection page | Nothing can be added to the bag from a collection page. | Cards carry a flag, a wishlist heart, a price and a star rating, but no add to bag control. Every add costs a page load. | We recommend an add to bag control on the card, with a size step for products that need one. |
| 05.6 | High | Product page | The sticky buy bar only appears after three or four screens. | The sticky price and button are present, but do not appear until well down the page, so the shopper who decides early has to scroll back. | We recommend showing the sticky bar as soon as the main add to cart button leaves the screen. |
| 06.1 | High | Home page | The home page is slow to react when it is tapped. | Real visitor data records a tap response of 261 milliseconds on the home page and 262 across the site, against a 200 millisecond pass mark. Desktop passes everywhere. | We recommend profiling the long running scripts on the home template and deferring or removing the third party apps behind them. |
| 06.2 | High | Product page | The product page lags at the moment of choosing a size. | Tap response on the product page is 230 milliseconds against the same 200 millisecond mark. Collection pages pass at 197. | We recommend the same script work on the product template, since this is where size selection and add to cart happen. |
| 07.10 | High | Product page | Demand for a sold out size is thrown away in silence. | There is no back in stock alert anywhere on the site, on sold out products or on missing sizes. | We recommend a notify me capture on every unavailable size and every sold out product. It is the cheapest way to hold demand the brand has already paid for. |
| 07.11 | High | Site wide | Loyalty points cannot be seen or spent online. | No balance, no tier and no redemption field anywhere on the site. The programme's own terms make store redemption subject to retailer discretion, and it goes by three different names across the brand's own pages. | We recommend showing the balance in the account area, enabling redemption at checkout, removing the discretion clause and settling on one name. |
| 07.6 | High | Product page | The delivery check hangs with no answer and no error. | On one pincode the check span indefinitely across two attempts. Pressed before a size is chosen it returns an error below the fold, where the shopper will not see it. | We recommend an explicit message when an address cannot be served, removing the size requirement, and moving the check above the add to cart button. |
| 07.7 | High | Navigation | A 400 store estate is one footer link away from the shopper. | The locator is reachable only from a footer link reading Visit Our Store, and opens on a different subdomain with a different design. | We recommend a Stores entry in the site header, and a find this in a store near you link on every product page. |
| 07.8 | High | Navigation | The store finder cannot find one of Delhi's main retail districts. | Searching the locator for Connaught Place returns no results, while the same locator holds a Connaught Place store in its own data. | We recommend fixing the locality search for the top 50 retail localities, starting with the ones that already hold a store. |
| 07.9 | High | Site wide | There is no way to get a suit this week. | No pickup, no reserve in store, no ship from store, no same day. The payment screen offers one line: standard delivery. | We recommend reserve and collect at the top 50 company owned stores, starting with suits and blazers, which is the most time pressured demand in the category. |
| 08.2 | High | Site wide | The brand is missing from the question shoppers ask first. | Across five AI engines the brand was named in 27 of 30 answers that asked for a list of brands, and in 2 of 19 that asked for advice. | We recommend occasion and need guides, and question led copy on the 19 of 30 priority collections that carry none. |
| 08.3 | High | Site wide | The brand is absent from almost every source these engines read. | It is strong on 10 of 33,150 source domains cited in this category and missing from 32,188. YouTube cites it 80 times against 1,045 for the nearest group of rivals. | We recommend a named target list of twenty sources and a programme to earn placement on them. |
| 08.4 | High | Site wide | The site's authority sits on the one page that does not sell. | The home page holds 2,600 referring domains. The suits collection holds four, trousers one, and the combined suits and blazers page none. | We recommend linking inward from the home page and the blog, and building one link worthy asset for each priority collection. |
| 08.5 | High | Collection page | Two collection pages account for most of the traffic that was lost. | Organic visits fell about 15 percent while the number of ranking keywords barely moved. The trousers page lost 20,400 monthly visits and the suits page 6,200. | We recommend rebuilding those two pages first, with answer led copy and internal links, since rankings holding while clicks fall points at answers being given above the results. |
| 09.5 | High | Site wide | The traffic fall cannot be explained without search console. | Organic visits fell about 15 percent while ranking keywords moved about one percent. Only search console separates lost impressions from lost clicks. | We recommend read access, and a re reading of the same period, because that distinction decides whether the answer is content or technical. |
| 09.6 | High | Site wide | A session recording tool is installed and nobody is reading it. | Microsoft Clarity loads on the storefront, but no heatmap, recording or rage click data reached any of the five audits. | We recommend pulling it for the product page, the cart and the size selector. It is already paid for, and it would confirm or kill the biggest assumption in this report within a week. |
| 04.10 | Medium | Cart | The discount codes change between the product page and the cart. | The product page offers three codes. The cart offers a different set, and the small print on one of them makes the item non returnable. | We recommend one coupon set across the product page, the cart and the payment screen, with return eligibility stated on every code. |
| 04.11 | Medium | Home page | A popup opens mid visit and takes the shopper's click. | A phone number popup offering ten percent off appears between seven and twelve seconds into a first visit. Twice it opened as our shopper was clicking something else, and the click was lost. | We recommend showing it on exit intent or after thirty seconds, and showing the code again in the cart for anyone who closed it. |
| 04.12 | Medium | Collection page | Collection titles promise discounts the page does not carry. | The wedding suits tab title promises up to 40 percent off. One of the 130 suits on the page carries a markdown. | We recommend removing the discount claim from the titles of collections that are not on sale. |
| 04.13 | Medium | Cart | The main button on the cart page has its label cut off. | The checkout button is a 45px box whose label wraps onto two lines, and the second line is clipped. Each line in the cart carries a discount tag with nothing explaining what triggered it. | We recommend widening the button so the label fits on one line, and adding a line above the total explaining the five percent multi buy. |
| 04.8 | Medium | Product page | Three piece suits say they contain one piece. | Three of the four three piece suits checked, including the 25,999 rupee Xenius, list the number of pieces as one. | We recommend correcting the field across every suit and writing it in words: three pieces, jacket, waistcoat and trousers. |
| 04.9 | Medium | Product page | A sleeveless vest is sold as a sweater. | All eight photographs on the 2,199 rupee Less product show a sleeveless knit vest. The title, the highlights and the description never use the word sleeveless, and the styling tip suggests pairing it with a tee. | We recommend adding sleeveless to the name and highlights of every vest, and giving vests their own filter value under sweaters. |
| 05.10 | Medium | Search | Search does not remember what the shopper looked for. | The search panel opens with popular choices and a recommended grid, which works well, but carries no record of previous searches. | We recommend adding recent searches above the popular choices for anyone who has searched before. |
| 05.11 | Medium | Home page | A wrong address ends the visit. | The 404 page carries a short message and a single Continue Shopping button. No products, no search box and no popular links. | We recommend featured products and a search box on the 404 page. |
| 05.12 | Medium | Product page | The visible description does little selling. | The page carries the specification but little writing about the garment itself, so the shopper weighing two similar shirts has nothing to choose between them on. | We recommend two or three plain lines above the specification: the fabric, how it wears, and who it suits. |
| 05.13 | Medium | Home page | A brand founded in 1991 never tells its story. | There is no About Us or Our Story section reachable from the home page. | We recommend a short brand story linked from the home page and the footer, covering the heritage and the tailoring. |
| 05.14 | Medium | Cart | The cart suggests more of what is already in it. | Alongside a shirt the cart offers another shirt under You May Also Like, and belts under The Finishing Touch. | We recommend complete the look recommendations that finish the outfit, and guided bundles such as a suit with a shirt and a tie. |
| 05.15 | Medium | Product page | There is no way to see a whole outfit. | No shop by look section exists, so a shopper who likes a styled photograph cannot buy what is in it. | We recommend a shop by look section built from the photography the brand already shoots. |
| 05.7 | Medium | Home page | The range is only visible once a menu is opened. | There is no category strip beneath the logo on the home page. | We recommend a row of top category tiles directly under the header. |
| 05.8 | Medium | Cart | The cart says safe checkout but shows nothing that proves it. | A continue to safe checkout line sits above the button. There are no payment method marks or security badges in the drawer or on the cart page. | We recommend showing accepted payment methods and a security mark next to the checkout button. |
| 05.9 | Medium | Cart | An empty bag offers nothing to buy. | The empty state shows an illustration, one line of text and a Shop Now button. No bestsellers, no recently viewed, no recommendations. | We recommend showing recently viewed products and a short bestsellers row in the empty bag. |
| 06.3 | Medium | Home page | The server is slower to answer phones than desktops. | Server response runs between 0.87 and 1.0 seconds on mobile across the site, the home page and collection pages, against a 0.8 second mark. Desktop answers in 0.37 to 0.41. | We recommend finding what the mobile path asks for that desktop does not, and caching what does not change. |
| 06.4 | Medium | Collection page | Collection pages shift while they settle on desktop. | Layout movement measures 0.14 on desktop collection pages against a 0.1 mark. Mobile is fine at 0.04. | We recommend reserving space for the banner and the grid so the page does not move under the cursor. |
| 07.12 | Medium | Site wide | A store purchase has no digital existence. | Order tracking accepts an order number or a courier number, both of which only exist for a website order. There is no invoice or mobile lookup. | We recommend lookup by invoice and mobile number, so the free alteration entitlement does not depend on the customer keeping a piece of paper. |
| 07.13 | Medium | Product page | Taking the free alteration quietly ends the right to return. | The product page promotes free alteration within 180 days. The returns policy states that altered garments cannot be returned or refunded. The product page does not say so. | We recommend adding the caveat where the service is promoted, so the customer learns it before the scissors rather than after. |
| 07.14 | Medium | Site wide | Nothing a store does can be booked. | No store page lists its services, and all five service page addresses tested on the main site return a 404. Free alteration, fit consultation and wedding appointments are all real reasons to visit. | We recommend listing services on each store page and making them bookable, with a chat channel the shopper can open. |
| 07.15 | Medium | Cart | An order cannot be marked as a gift. | The cart offers coupons and recommendations, but no wrap, no message and no way to hide the price on the invoice. | We recommend a gift toggle in the cart covering wrap, a message and a price free invoice, plus a digital gift card. |
| 07.16 | Medium | Site wide | A coupon from the website may be refused at the counter. | Product pages present codes without qualification, while the FAQ states that online and offline offers vary because they are different business channels. | We recommend saying on the product page which codes work in stores, or bringing the two sets into line. |
| 07.17 | Medium | Checkout | The payment screen asks for a phone number before answering anything. | The only field on the first screen is a mobile number. There is no final total, no delivery date and no returns line, and the marketing consent box is already ticked. | We recommend showing the total, the delivery date and the returns line before the phone step, and leaving consent unticked. |
| 08.10 | Medium | Site wide | Search engines are pointed at products that cannot be bought. | All 5,417 product addresses are submitted, including the 2,852 with no buyable size. | We recommend excluding unbuyable products from the sitemap until stock returns, as a holding step while the merchandising decision is made. |
| 08.11 | Medium | Collection page | A range the brand merchandises cannot be found by its own name. | The non iron shirts collection is live and browsable with 171 products, but no collection address matches that name, and there is no cargo pants collection at all. | We recommend correcting the collection address so the range is findable, and building the missing one. |
| 08.6 | Medium | Product page | Shoppers see a star rating that machines cannot read. | Ratings display on collection listings, but the rating is written into the page data on only 2 of the 19 product templates checked. No product carries colour, material or size as structured data. | We recommend publishing the rating and review count on every product page that has them, and adding colour, material and size. |
| 08.7 | Medium | Site wide | The brand answers to four names and three descriptions. | It appears as BLACKBERRYS, Blackberrys, Blackberrys Menswear and Blackberrys Clothing India. Its own site calls it premium, Wikipedia calls it luxury, and every AI assistant calls it mid premium. | We recommend agreeing one name and one description, then applying both to the site data, the About page and every marketplace listing. |
| 08.8 | Medium | Site wide | Asked where to buy, assistants send shoppers to marketplaces. | One assistant's shopping table named seven places to buy and did not include the brand's own store. The brand's marketplace page carries a public rating that the brand store does not. | We recommend confirming the shopping feed covers the full in stock catalogue, and publishing the on site reviews so the brand store carries a rating too. |
| 08.9 | Medium | Product page | Test products and duplicate names are live in the catalogue. | Three products with test in the name are published, including a 29,489 rupee suit whose title says navy and whose garment is wine. 281 product titles are duplicated. | We recommend removing the test products and correcting the duplicated titles, because these are exactly the fields a shopping assistant matches on. |
Six findings about measurement itself.
None of this can currently be proved to have worked.
No analytics, search console, store platform or session recording data was available to any of the five audits.
That makes the findings credible and the sizes unknown. We can tell you the cart loses 520 rupees at the payment screen. We cannot yet tell you how many baskets that costs per week.
The delivery check's worst outcome is invisible.
When the check hangs it records nothing, so nobody knows how many shoppers give up there.
We recommend four events on that control: check started, date returned, no result, and blocked because no size was chosen.
The two clearest money leaks produce no data.
The 520 rupee price rise and the silent loss of cash on delivery both happen inside a checkout that reports nothing back.
We recommend step level tracking through the payment flow, including when a discount is applied or dropped and which tenders were shown.
Nothing connects a website visit to a store purchase.
There is no shared identifier, so revenue the website sends into 400 stores measures as zero.
We recommend capturing the loyalty identifier or mobile number at the till, and tagging clicks on any store module on the site.
The traffic fall cannot be explained without search console.
Organic visits fell about 15 percent while ranking keywords moved about one percent. Only search console separates lost impressions from lost clicks.
We recommend read access, and a re reading of the same period, because that distinction decides whether the answer is content or technical.
A session recording tool is installed and nobody is reading it.
Microsoft Clarity loads on the storefront, but no heatmap, recording or rage click data reached any of the five audits.
We recommend pulling it for the product page, the cart and the size selector. It is already paid for, and it would confirm or kill the biggest assumption in this report within a week.
Everything here was observed from outside. These four need access.
Everything in this report was observed from outside the business. These four need access, and together they turn the whole report from a set of observations into a set of measurements.
Every figure in this report traces back to one of the five audits run between 11 and 14 November 2026. The source documents carry the full detail behind each section.