"Where Should I Start If I Want to Improve My Conversion Rate?"
Search this question and you will get a list. Better photos. Trust badges. Faster load times. Simplify checkout. Add reviews. Exit-intent popups.
Every item on that list works somewhere. The problem is that it is a list of everything, given to everyone, with no way to tell which two or three items apply to you.
So founders do four things at once, see no clear change, and conclude that conversion work does not do much.
Here is a different starting point.
Step Zero: Make Sure the Number Is Real
Before improving a conversion rate, confirm it is the conversion rate.
Pull your GA4 purchase event count and your Shopify order count for the same 30 days.
Gap | What it means |
|---|---|
Within 5–10% | Your number is real. Continue. |
GA4 20%+ below Shopify | You are converting better than you think |
GA4 above Shopify | Duplicate events. Your number is inflated. |
This takes ten minutes and it is not optional. A meaningful share of stores with a "low" conversion rate are converting fine and recording it badly. Our guide to why GA4 and Shopify numbers don't match covers the causes.
Step One: Find Out Which Problem You Have
There are essentially four places to lose a buyer. Your job is to work out which one is costing you most.
Build a funnel in GA4 with these steps and compare each transition against normal ranges:
Transition | Healthy | Investigate below |
|---|---|---|
Product view → add to cart | ~6% | 4% |
Add to cart → checkout started | 50–70% | 40% |
Checkout → payment info | 65–80% | 55% |
Payment info → purchase | 70–85% | 60% |
Write down the actual numbers. You will need them in a moment.
Two things to check while you are here:
Split by device. Mobile runs around 2% against desktop's 3.7%, and mobile is roughly 70% of your traffic. If one step is dramatically worse on mobile, that narrows the problem considerably.
Watch for any step above 95%. That usually means the event only fires for people who complete the step, so everyone who abandoned was never counted. It is a tracking signal, not good news.
Step Two: Size Each Leak Properly
This is the step that changes where most founders start, so it is worth doing carefully.
The biggest percentage drop-off is almost never the best place to begin.
Your product view to add-to-cart step will always look catastrophic. Something like 94% of product page visitors do not add to cart. That sounds like the obvious priority. It usually is not, because most of those people were never going to buy anything. They were browsing.
The payment step looks small by comparison. Maybe you lose 20% of people there. But every one of those people entered their payment details. They were buying. Something stopped them.
Two numbers matter for each step:
How many people you lose. Absolute count, not percentage.
How many of them you could realistically recover. This varies enormously by step:
Step | Realistically recoverable |
|---|---|
Product view → cart | 3–8% of those lost |
Cart → checkout | 10–20% |
Checkout → payment | 15–25% |
Payment → purchase | 20–35% |
Multiply the people lost by the recoverable percentage by your average order value. That gives you a rough monthly value for each leak.
Do this for all four steps. The ranking usually surprises people, the step that looked twenty times worse often turns out to be worth roughly the same as one that looked minor, and far harder to fix.
Our guide to quantifying revenue loss from funnel drop-offs covers the full calculation.
Step Three: Fix in This Order
Once you have the value ranking, work from the bottom of the funnel upward. Three reasons: the fixes are usually simpler, the recovery rates are higher, and the people you recover were already committed.
If payment to purchase is your weak step
Usually a technical problem rather than a design one. Check before assuming it is UX:
Payment gateway failure rates in your Razorpay, Cashfree, or PayU dashboard
Whether a failed UPI transaction returns the user to an empty cart with no retry path
COD availability at the pincodes your traffic actually comes from
Whether the payment page renders correctly on mid-range Android devices
This is the cheapest step to fix and the highest recovery rate on the list. Start here if the numbers point at it.
If checkout to payment is your weak step
Form friction. Count your fields, the workable range is around 12 to 14, and most stores are above it. Then check:
Is guest checkout available, or is account creation forced?
Does the form validate clearly, or throw unhelpful errors?
Does it render properly on a phone?
An interesting finding from checkout usability research: a longer form split across logical steps often outperforms a shorter one crammed onto a single page. Perceived length matters more than actual field count.
If cart to checkout is your weak step
Almost always cost shock. Unexpected costs are the single largest documented reason for abandonment across ecommerce.
Are shipping charges visible before the cart?
Is the return policy findable without leaving the page?
Is delivery timing clear?
The fix here is usually moving information earlier rather than changing anything about the cart itself.
If product view to cart is your weak step
The hardest to move, and the one most founders start with.
First split it by traffic source before touching the page. Cold paid social traffic converting poorly on a product page written for people who already know your brand is a traffic-page mismatch, not a page problem. Our post on landing pages versus product pages for paid traffic covers that comparison.
If it is genuinely the page, the usual culprits are photo count, missing reviews, unclear sizing, and the add-to-cart button sitting below the fold on mobile.
What Not to Start With
A redesign. It changes everything at once, so you learn nothing about what worked, and it destroys the baseline you would need to measure improvement.
Button colours and microcopy. These occupy time that could go to a checkout fix worth far more. At typical D2C traffic volumes you get a handful of meaningful changes per quarter, spend them well.
Whatever a competitor just launched. Their traffic mix, price point, and audience are not yours.
Five things simultaneously. You will not know which one worked, so you cannot repeat it.
A Realistic Timeline
Week one: validate the tracking, build the funnel, size the leaks.
Weeks two and three: fix the highest-value item. If it is a technical payment issue, this may be a few days of developer time rather than a testing project.
Week four: measure. Compare against the same period before the change, on the same traffic mix.
Then repeat.
If you have enough traffic to A/B test properly, test the changes rather than shipping them. If you do not and plenty of growing stores do not ship the obvious fixes directly and measure before and after. Testing whether removing friction reduces friction is not a good use of limited traffic.
The Short Answer
Start by confirming your conversion rate is real. Then find which of the four steps is furthest from normal. Then size each leak by what you could actually recover, not by how large the percentage looks. Then fix the highest-value one, on its own, and measure.
That is one decision instead of a list of twenty, and it is based on your store rather than someone else's.
If you are not sure your funnel data is reliable enough to run this, that is the thing to resolve first. Our pre-CRO data audit guide covers what to check.
Want someone to run this properly and hand you a ranked list? Talk to FunnelFreaks, we validate the data first, then tell you where the money actually is.