Shipping first appears at the cart, and it is six times the sticker.
Fix this firstPut the cost on the line that already carries the date.
your page, today — unretouched
https://www.redbubble.com/cart agent · shot 1
Cart — shipping revealed, destination India
What we saw
The product page tells a visitor exactly when the sticker arrives — “Express by 11 August · Standard between 24 – 26 August” — and never what shipping costs. A cost appears 0 times on that page. It appears for the first time in the cart: a $2.51 item, $15.92 standard shipping, $18.43 to pay. Shipping is 634% of the item price.
In your store’s own words
Delivery Express by 11 August Standard between 24 - 26 Augustproduct page — dates, and no cost anywhere on the page
Delivery to Indiacart — the destination this order was priced against
Standard shipping $15.92cart, Order Summary — the first sight of a cost
Total $18.43cart, Order Summary
Quoted character for character from the capture — check any line against your own page.
Why it matters
Every visitor who reaches the cart has already been paid for — the ad click, the browse, the product decision. The obvious objection is that shipping is computed per fulfiller and per destination and cannot be shown early. That objection fails on their own page: the delivery date is already destination-specific. If the date can be worked out when the product page loads, the cost can be too.
Where this claim stops. This is an India-detected session and the cart says so: “Delivery to India”. A US session sees $1.96 standard shipping and a $4.65 subtotal on the same sticker — the audit tested both destinations on 30 Jul 2026. Say the destination out loud. The international segment is where this concentrates; the US number is smaller and still 73% of the item price.
Evidence and how this was measured
measured · 352 × 26 at y = 502 · measured on the desktop capture, at 1440 px wide
Who this touches
every buyer
How much it costs them
high
How sure we are
high — observed at two destinations
What the fix takes
low
Finding 1 in our written audit of 30 July 2026 — ask us and we will send it.
proposed — our drawing, not your page
Delivery to India
Standard — arrives 24–26 August$15.92
Express — arrives by 11 August+$45.41
Put the cost on the line that already carries the date.
Disclosure only. This is not a recommendation to change shipping rates, subsidise international shipping, or introduce a free-shipping threshold — that is pricing strategy and it is Redbubble’s call, not an auditor’s. It will likely reduce add-to-cart while raising checkout completion, so measure revenue-per-session or the test reads as a loss. The $45.41 express figure is from the audit’s 30 Jul cart, not from this capture.
Adding the sticker opens a drawer. At the top: “It’s in the cart!”, a discount nudge, the line item, the subtotal. Then “Similar designs”, a grid of other products, halfway down. “View cart”, the only forward path, sits at the bottom, underneath all of it. The word “checkout” appears 0 times in the drawer — counted in the page itself, not by eye.
In your store’s own words
Similar designsthe cross-sell heading, halfway down the drawer
View cartthe only forward path, at the bottom — below the cross-sell grid
checkoutappears 0 times in the drawer
Quoted character for character from the capture — check any line against your own page.
Why it matters
This is the highest-intent moment in the session, and the drawer spends its most valuable real estate on alternatives to the thing the visitor just chose. G-134 is one of the fully sourced rows and it is explicit: cross-sells in the drawer that opens after Add to cart belong below the buttons that carry a visitor forward, and should be styled less prominently, because prominent ones make people misread the drawer and mistake the cross-sell for the way on. 94 documented desktop failures, 60 mobile.
Where this claim stops. On 30 Jul the audit found “View cart” off the bottom of a shorter screen — reachable only by scrolling past the grid. On a laptop on this capture it is on screen without scrolling. The ordering is the finding and it reproduces; having to scroll to reach it did not, on this screen, and is not claimed here.
Evidence and how this was measured
measured · 432 × 26 at y = 440 · measured on the desktop capture, at 1440 px wide
drawer 544 × 900
“It’s in the cart!” at y=24
“Similar designs” at y=440
“View cart” at y=840
audit, 30 Jul: “View cart” at y=1176 in an 819px viewport
Who this touches
every add-to-cart
How much it costs them
medium-high
How sure we are
high on desktop
What the fix takes
low — reordering inside an existing component
Finding 5 in our written audit of 30 July 2026 — ask us and we will send it.
proposed — our drawing, not your page
CheckoutView cart
Similar designs
Primary path first, cross-sell after it.
The reorder is a fix. The direct Checkout button is a genuine test — some buyers do want the cart review step — and the guardrail is AOV, since the cross-sell block was presumably installed to lift it. Frame it as a trade being measured, not a defect being corrected.
“pikchu” — one character off Pikachu — returns 3 items, under a heading that reads “Pikchu”. No spelling correction, no “did you mean”: 0 corrections anywhere on the page. And because the count is three rather than zero, the well-built zero-result page — the one that offers a way out — never appears.
In your store’s own words
Pikchuthe results heading — the query, uncorrected
3 itemsthe result count, on a franchise the site carries in volume
Quoted character for character from the capture — check any line against your own page.
Why it matters
The near-miss is far more common than the total miss, and it lands on high-intent traffic — someone typing a character name has already decided what they want. On a marketplace whose demand is overwhelmingly fandom, character and meme names, this is a structural exposure rather than an edge case.
Where this claim stops. Two queries is an illustration, not a measurement. The zero-result page — which is good, and is the one this recommendation re-uses — was verified by the audit on 30 Jul with a made-up search, not on this capture. Ask them for their own top queries returning fewer than five results over 30 days; that converts this from our judgement into their data.
Evidence and how this was measured
measured · 53 × 18 at y = 217 · measured on the desktop capture, at 1440 px wide
Who this touches
search users
How much it costs them
medium-high
How sure we are
high for the queries tested
What the fix takes
medium
Finding 4 in our written audit of 30 July 2026 — ask us and we will send it.
proposed — our drawing, not your page
Showing results for Pikachu.
Search instead for “pikchu”.
Correct it, and say that you did.
Two parts, and the cheap one is second: show the existing zero-result page when the result count is low, not only when it is exactly zero. That page already exists; only the rule that decides when to show it changes. The spelling correction itself is a relevance change and should be tested on search-to-product click-through, not on purchase rate.
the other end of this finding
https://www.redbubble.com/shop?query=pikchu
the query, echoed back uncorrected · on a laptop
How we measured this
What we opened, exactly
A real browser opened redbubble.com on 31 July 2026, photographed every screen it reached, and measured where each element sits. Every figure on this page is either measured in that session or quoted from our written audit, with its source named.
Why the list is this length
The audit behind this page argues more findings than are shown. A finding appears here only when this capture can carry it — a measured box, a verbatim quote, a named limit. The rest stayed in the written audit; ask us for it.
What we could not see
An audit that hides its blind spots is guessing. These are ours, named.
The mobile funnel.The audit session could not be forced below 1456px, so every finding in it is desktop-observed. The mobile boards here show the same screens exist at 390px; they are not a mobile audit.
The payment step.It sits behind full delivery-address entry, and we do not submit personal data to a live system.
Cart-to-checkout drop-off by shipping destination.Their analytics. Finding 1 predicts a specific, testable pattern — abandonment rising with the shipping-cost-to-item-value ratio. One query settles it either way.
Whether any of this is already a live experiment.Redbubble has in-house capability. Confirm before recommending, or the audit reads as a scan.
The screens we walked
Captured on a laptop and on a phone. The audit is desktop-observed and names mobile as its largest gap, so the mobile boards here are evidence that the same screens exist at 390px — not a mobile audit. Nothing below is claimed about the mobile funnel.
The exact pages we opened, at 1440 px and 390 px, and how tall each one was
Screen
Page
Width
Height
Sticker product pageNothing on this screen is claimed as a finding. It is here as evidence that the same screens exist at this width.
Cart — shipping revealed, destination IndiaNothing on this screen is claimed as a finding. It is here as evidence that the same screens exist at this width.
/cart
mobile 390
3,435 px
Cart — shipping revealed, destination India
/cart
desktop 1440
1,734 px
Search: pikchuNothing on this screen is claimed as a finding. It is here as evidence that the same screens exist at this width.
/shop
mobile 390
3,754 px
Search: pikchu
/shop
desktop 1440
2,220 px
How to check any claim on this page
Open the page named under any figure, at the width in its caption — 390 px is a phone, 1440 px is a laptop. In Chrome: DevTools, then the device toolbar, then set the width.
Select any quoted text on this page and search your own page for it. It should match character for character.
Coordinates are CSS pixels from the top-left of that page at that width, so “y = 142” means 142 px from the top.
If the store has changed since we captured it, a claim may no longer reproduce. That is worth knowing — and it does not un-measure the capture: every figure here comes from the dated screenshots on this page.
No lift number, anywhere
Not a percentage, not a range, not an “up to”. We can tell you the leaks and their direction with confidence; we cannot size them without your analytics, and anyone who says otherwise is selling you a spreadsheet. Every figure on this page is either measured on the capture or quoted from the audit with its source named.
Captured 1 Aug 2026 from redbubble.com on a laptop and on a phone · India-detected session, logged out, prices in USD · replayed from that capture · Captured 31 July 2026 from redbubble.com.
Want us to look at the rest of your store?
We walk the whole buying path, not just the screens above, and send you what we find.
