R for Rabbit
Audit Overview
Your store's untapped revenue potential — and how to unlock it
Why We Created This Audit
We analyzed rforrabbit.com the same way we've audited 350+ e-commerce stores — looking for the specific gaps between your current experience and what top-performing Toys & Hobbies stores deliver. Every finding in this report is a revenue opportunity backed by industry data and competitive benchmarks.
What We Analyzed
- UX & Conversion Design15 findings
- Performance & Speedvs 4 competitors
- Technology & App StackPlatform + 5 apps
- Industry BenchmarksToys & Hobbies
Pages Analyzed
- Homepage5 findings
- Collection Pages3 findings
- Product Pages (PDP)4 findings
- Cart & Checkout3 findings
This audit was prepared by Growisto — a CRO-led Website development team behind 167% conversion growth for Atomberg, 46% CR lift for TyresNmore, and 350+ e-commerce projects.
Performance & Technology
Speed benchmarks, Core Web Vitals, and technology assessment for R for Rabbit
Mobile PageSpeed Score
Mobile lab score of 28/100 with main-thread blocking time the dominant constraint — 2,602ms of Total Blocking Time against a 200ms target.
Competitive Comparison
Benchmarked against 4 leading Toys & Hobbies stores in your market
| Store | Mobile Score | Desktop Score | Mobile LCP | Mobile CLS | Mobile TBT |
|---|---|---|---|---|---|
| R for Rabbit (Client) | 28 | 35 | 4.3s | 0.135 | 2,602ms |
| Babyhug | 73 | 78 | 6.2s | 0 | 72ms |
| LuvLap | 42 | 38 | 25.3s | 0.000 | 485ms |
Core Web Vitals — Google's UX Quality Signals
Sites failing Core Web Vitals may rank lower in Google mobile search results
LCP How fast content appears
FCP First visual response
TBT Main thread blocking
CLS Visual stability
INP Tap/click responsiveness
What This Means for Revenue
R for Rabbit scores 28/100 on mobile and 35/100 on desktop in Lighthouse's lab test — genuinely weak numbers, and worth naming plainly. But the shape of the problem matters more than the score, because it points to something specific and fixable rather than a rebuild. The silver lining is in the field data. Real Chrome users visiting the live site see excellent layout stability (CLS 0.01, comfortably in the "Fast" band) and a healthy server response (TTFB 743ms on mobile, 445ms on desktop). Infrastructure and hosting are not the bottleneck. The bottleneck is JavaScript execution on the main thread. Total Blocking Time is 2,602ms against a 200ms target — roughly thirteen times over. That single metric is doing most of the damage to the score, and it is the classic signature of a Shopify storefront carrying a heavy accumulated app and script stack rather than a fundamental architecture problem. The competitive set makes the opportunity concrete. Babyhug scores 73 on mobile despite having a *worse* Largest Contentful Paint than R for Rabbit (6.2s versus 4.3s) — it wins purely because its main thread stays clear, with just 72ms of blocking time. That is a 36x gap on the one metric that matters most here, and it is the clearest possible proof that this is a script-weight problem rather than a content or hosting problem. LuvLap sits in between at 42, held back by a 25.3s LCP. So the path from 28 to the front of this set runs through script auditing and deferral — removing or lazy-loading unused third-party apps, deferring non-critical JavaScript, and trimming main-thread work. That is a well-understood, bounded piece of work, and Babyhug demonstrates the ceiling is real rather than theoretical.
Technology Stack
Platform
Shopify
Native Shopify storefront on rforrabbit1.myshopify.com — auto-scaling, PCI-compliant checkout, and Shopify CDN for assets and images.
Theme
Biomimc - New Navigation
- Type: Custom-named Shopify theme (OS 2.0 storefront)
- Custom-built/customised theme, not a stock Shopify theme name
- Bottom mobile tab bar (Home/Categories/Age/Spotlight) doubles as the primary category navigation
Checkout & Payments
Native Shopify Checkout (OTP-gated) via Razorpay-class gateway (UPI/Cards/Netbanking icons shown in footer)
- Guest checkout: Not available — clicking Checkout Now redirects to a mandatory 'Login/Sign-up with OTP' screen with no guest option visible on that screen.
- Express checkout: No Shop Pay, Google Pay, or Apple Pay express buttons detected in cart.
- Visa, Mastercard, RuPay, UPI, Google Pay, Internet Banking icons shown in footer; ICICI Bank card-EMI offer surfaced on PDP/cart
Technology Assessment
R for Rabbit runs on a custom-named Shopify theme ('Biomimc - New Navigation') with a mobile bottom tab bar as its primary navigation pattern. Payments are broad (cards, UPI, netbanking, COD, card EMI) but the funnel's biggest technical friction is checkout itself: clicking Checkout Now routes every shopper — new or returning — through a mandatory OTP login/signup screen before they ever reach the native Shopify checkout, with no guest-checkout path visible on that screen.
UX & Conversion Findings
Page-by-page analysis with visual comparisons against top Toys & Hobbies stores
- The header scrolls away completely — once a shopper moves down the page, the search bar and cart icon are gone.
- To search for anything they must scroll all the way back to the top, and every extra scroll is a chance to give up.
- The cart count disappears too, so shoppers lose sight of what they have added and how close they are to checking out.
- Only the category pills and a bottom tab bar stay on screen, and neither offers search or the cart.
- Pin a slim header carrying search and the cart icon so both stay one tap away at any scroll depth.
- Keep the live cart count on the icon — a visible basket nudges shoppers back to checkout.
- Baybee already does this: its search and cart stay fixed at the top throughout the page, which is the category norm.
- The homepage has no email or phone capture anywhere — no newsletter box, no sign-up prompt, no offer in exchange for contact details.
- First-time visitors who are not ready to buy leave with no way for the brand to reach them again.
- Baby gear is a considered purchase researched over days, so losing that contact costs the whole follow-up window.
- Paid traffic that does not convert on the first visit is paid for twice, because there is no owned channel to bring it back.
- Add a simple email or WhatsApp capture with a clear reason to subscribe, such as new-parent guides or early access to sales.
- Trigger it on exit intent or after real engagement rather than instantly, so it does not interrupt a shopper who is already browsing.
- Competitors in this category run capture as standard practice, which is what lets them retarget the same visitor at no extra media cost.
- The homepage trust strip talks only about product formulation — talc-free, dermatologically tested, no parabens.
- Nothing on the homepage states that the gear range is safety certified, even though the certifications exist.
- Parents buying prams, car seats and cots screen for safety before anything else, so silence on it reads as absence.
- Shoppers who cannot confirm safety on the brand's own site often leave to check a marketplace listing instead, and buy there.
- Add a short, plain safety-certification line to the homepage trust strip, alongside the existing formulation claims.
- Keep the wording specific to the standards the range actually meets, so it reads as fact rather than marketing.
- Baybee states 'Certified & Safety Tested Products' directly in its homepage trust row, which is why safety is settled there before a shopper reaches a product page.
- There is no wishlist or save-for-later anywhere on the site — not on product cards, not on product pages, and not in the account area.
- Parents comparing prams across several days have no way to keep a shortlist, so every visit starts the search again.
- With nothing saved there is no record of interest to follow up on, so warm demand goes unworked.
- Shoppers who cannot save often use the cart as a holding pen instead, which makes cart data unreliable as a buying signal.
- Add a save-for-later capability, reachable from product cards and product pages without forcing an account first.
- Keep saved items visible in the account area and use them for gentle reminders when a saved product goes on offer.
- Baybee runs a wishlist on its storefront, which is why a shopper there can park a decision and come back to it instead of starting over.
- Bestseller and Deal of the Day tiles carry no stock or demand signal — no low-stock note, no indication of how fast an item is moving.
- Nothing distinguishes a product selling quickly from one sitting still, so there is no reason to decide today.
- Deal tiles show a discount but no scarcity, which makes the offer feel permanent and easy to postpone.
- Postponed decisions in this category usually restart on a marketplace rather than back on the brand's own site.
- Show a low-stock note on the product card once inventory falls below a threshold, driven by real stock data.
- Add a light demand cue such as recent purchases on genuine fast movers, so bestseller badges carry evidence.
- Scarcity and demand cues are a well-established practice among category competitors precisely because they shorten the decision.
- Product cards offer no quick preview — the only way to see details is to open the full product page.
- Comparing similar strollers means opening, going back, and opening again, and the grid position is lost each time.
- The catalogue repeats the same product across several colourways, so shoppers compare inside the grid constantly.
- Each round trip is an exit point, and the deeper the shopper was in the grid, the more likely they abandon rather than scroll back.
- Add a quick-view control on each card that opens price, colours and Add to Cart in place.
- Prioritise the variant-heavy categories such as strollers and car seats, where side-by-side comparison is the norm.
- Quick view is a recognised best practice for variant-dense catalogues because it keeps comparison inside a single browsing session.
- The category page never states how many products it contains, so a shopper cannot tell whether they are facing ten items or two hundred.
- Applying a filter gives no updated count either, so there is no feedback that the filter did anything useful.
- Without a total, shoppers cannot judge how much scrolling remains and tend to stop early rather than reach the end.
- It also hides the depth of the range, so a genuinely broad catalogue reads as a short one.
- Show a result count at the top of the category and update it live as filters are applied.
- Display the count on the filter button too, so the effect of each choice is obvious before the drawer closes.
- Chicco India states its result count directly above the grid, which is why a shopper there knows how big the range is before deciding whether to keep scrolling.
- Category and product pages show no breadcrumb trail — a shopper has no visible indication of where the page sits in the range.
- Without it there is no one-tap way back to a parent category — the only route back is the browser button.
- Shoppers arriving from search or an ad land with no sense of where the page sits in the range.
- That missing context makes it harder to browse sideways into related categories, which shortens sessions.
- Add a breadcrumb trail to category and product pages, showing the path from home through to the current page.
- Keep each level tappable so shoppers can move up or sideways without losing their session.
- Visible breadcrumbs are standard practice among competitors because they turn a single landing page into a browsable path.
- The first screen of the product page is taken up by a promo banner and the product photo.
- The product name, the price and the star rating all sit below the fold, so none of them is visible when the page opens.
- A shopper arriving from an ad sees no price until they scroll, which delays the decision and invites a bounce.
- The opening screen reads like a homepage rather than a product page, weakening the link between the ad clicked and the page reached.
- Remove or shrink the promo banner on product pages so the buy box moves up into the opening view.
- Keep the product name and price together on the first screen, so the two core decision inputs arrive at once.
- Chicco India already leads its product page with the name, the star rating with its review count and the price together in the opening view, so matching that norm puts both decision inputs in front of the shopper before the first scroll.
- The buy box has no quantity control — the only option is to add a single unit.
- Anyone buying for twins or stocking up on consumables must add the item, open the cart and change the number there.
- Each additional step is a chance to lose the order, and the shopper may simply settle for one.
- The quantity control already exists inside the cart, so the component is built but not offered at the point of decision.
- Add the existing quantity stepper to the buy box, defaulting to one.
- Prioritise categories where multi-unit orders are common, such as twin strollers and multi-pack personal care.
- LuvLap places the same stepper directly above Add to Cart, which is the standard pattern in this category.
- The buy box offers only Add to Cart — there is no Buy Now or express purchase option anywhere on the product page.
- A shopper who has already decided must add the item, open the cart, and start checkout as three separate steps.
- Every extra step between decision and payment is a place to lose the order, and on mobile that cost is highest.
- Returning buyers who know exactly what they want get no faster route than a first-time visitor.
- Add a Buy Now button directly beside Add to Cart that takes the shopper straight into checkout.
- Keep Add to Cart as the primary action for shoppers still building a basket, so neither journey is penalised.
- Baybee places Buy Now directly above Add to Cart on its product pages, giving decided shoppers a one-tap route to payment.
- The Add Free Customization prompt renders twice, one directly after the other, inside the buy box.
- Repeating the same offer looks like a bug rather than a feature, and it takes up space next to the CTA.
- Visible defects beside the price undermine confidence at exactly the wrong moment on a high-value item.
- For a first-time visitor weighing a several-thousand-rupee purchase, small signs of carelessness carry disproportionate weight.
- Remove the duplicate so the customisation offer appears once, clearly, in the buy box.
- Add a check to the theme so repeated blocks cannot render twice on other templates.
- A clean, single-purpose buy box is standard across competitors because every element beside the CTA either helps the decision or hurts it.
- With the cart empty, the page offers no worded button, link or category shortcut back into the catalogue.
- The only control beside the cart title is an unlabelled ‹ arrow, which reads as browser-back rather than a route into the range.
- The cart drawer shows the same gap — its empty state invites the shopper to start shopping, then offers only an × to close the panel.
- Shoppers who empty a cart are still in a buying mindset, so ending that visit with no next step wastes live intent.
- Add a clear Continue Shopping button to the empty-cart state, on both the cart page and the cart drawer.
- Point it at a merchandised destination such as bestsellers or shop by age, rather than the homepage.
- Chicco India pairs the same empty state with a worded Return to Shop button, so the invitation and the action sit together.
- The cart offers a single checkout path — there is no express or wallet option beside the main button.
- Every shopper, including returning customers, is pushed through the full address and login sequence.
- On mobile, that typing is the heaviest part of the purchase and the most common point of abandonment.
- Shoppers who have paid before get no benefit from having done so, which makes repeat buying feel slower than it should.
- Add express checkout options beside the main button so returning shoppers can pay in one or two taps.
- Keep the standard checkout as the default path so first-time buyers are not disrupted.
- Express checkout is standard among competitors because it removes the typing that costs the most orders on mobile.
- The cart offers a Check Pin Code control, but nowhere does it state an expected delivery date or window.
- Confirming a pincode is serviceable is not the same as knowing when the item arrives, which is the question a shopper actually has.
- Anyone buying for a due date, a birthday or a baby shower cannot confirm the timing before paying.
- Unanswered delivery timing at the payment step is a common reason gifted and time-sensitive orders get abandoned.
- Show an expected delivery date against each cart line once a pincode is entered, not just a serviceability confirmation.
- Flag anything slower than the usual window up front, so timing surprises do not surface after payment.
- Competitors state delivery expectations before payment as standard practice, because certainty about arrival removes the last reason to hesitate.
App Ecosystem
What's installed vs what's missing from best-in-class Toys & Hobbies stores
Detected
Missing
Present (5)
Missing (3)
App Stack Assessment
R for Rabbit's app stack covers the fundamentals well: Judge.me drives visible review counts, Wiser powers cross-sell on cart and PDP, and a Nector loyalty widget is already installed — a differentiator most competitors in this category lack. The gaps are on the support and payments side: no live chat/helpdesk tool was found beyond a hidden WhatsApp link, no dedicated BNPL app exists alongside card EMI, and the cart has no app-driven free-shipping incentive bar. Running both Clarity and Hotjar simultaneously is also worth a quick cleanup — it's redundant analytics weight rather than a functional gap.
Confidential — Prepared for R for Rabbit by Growisto | August 2026