Web & Conversion

Conversion rate optimization

Conversion rate optimization is not a checklist of best practices. It is finding out where people actually give up, which requires watching them do it, and then fixing that. Most sites have two or three obvious problems worth more than any test they could run.

  • Recordings before opinions
  • Obvious fixes first
  • Honest about sample size

Sound familiar

How CRO usually goes wrong

We tested a button colour for six weeks and learned nothing.

Traffic is up and enquiries are flat.

Everyone has an opinion about the homepage and no data.

Start by watching people fail

Conversion work goes wrong when it starts with opinions. Someone read an article about button colours, someone else thinks the hero image is wrong, and six weeks later a test has produced a result nobody can interpret.

Start with evidence instead. Session recordings of people who did not convert, filtered to the pages that matter. An hour of watching real attempts will tell you more than a month of best-practice discussion, and it is uncomfortable in a useful way. You see people miss the button entirely, hesitate at a field, scroll past the thing you thought was obvious, and abandon at a step nobody suspected.

Then the funnel arithmetic

Alongside recordings, the numbers: how many people reach each step, and what proportion continue. The biggest drop is not always where attention has been focused. Frequently the homepage is fine and the leak is on a step two clicks deeper that nobody looks at.

Segment it. Mobile and desktop often behave completely differently, and an aggregate number hides a mobile experience that is quietly failing. New and returning visitors differ. Traffic from one channel may convert at a fraction of another because of a message mismatch upstream.

Fix the obvious before testing anything

Most sites have several problems severe enough that testing them would be absurd. A form that fails validation without saying why. A phone number that is not a link on mobile. A required field asking for something people do not have to hand. Content that loads late and shifts the page while someone is reaching for a button. A checkout step that breaks on one browser.

You do not test whether to fix these. You fix them, then measure the before and after. Testing is for genuine uncertainty, not for defects.

Honesty about sample size

This is where most conversion programmes quietly waste money. Reaching a trustworthy conclusion requires a certain number of conversions, and most sites do not have them. Below a few hundred conversions a month, tests take so long that the result is contaminated by seasonality and by everything else that changed meanwhile.

If that is your situation, the honest advice is to stop testing and start improving: fix the defects, make the obvious improvements, and measure period over period accepting that attribution will be imperfect. That is less satisfying than a significance figure and considerably more useful.

What usually moves the number

In practice, the same few things recur.

Clarity above the fold: what this is, who it is for, what happens next. Sites consistently overestimate how much context a visitor arrives with.

Form friction: fewer fields, correct input types, errors shown next to the field, never clearing what someone typed.

Speed, especially on mobile. It is not a conversion tactic in the usual sense but it moves the number more reliably than most things that are.

Answering objections on the page. Price, timeline, what happens if it goes wrong, who you are. Unanswered objections do not produce questions, they produce silent departures.

Specific rather than generic reassurance. A named person, a real response time, an actual number.

What I report

Conversion rate by segment, the drop at each funnel step, what was changed and when, and the before-and-after on each change. Where a test was genuinely powered, the result and the confidence. Where it was not, I will say so rather than presenting a number that cannot bear weight.

What you get

Included in every CRO engagement

  • Session recordings of real failures

    Filtered to non-converting sessions on the pages that matter. An hour of this beats a month of best-practice discussion.

  • Segmented funnel arithmetic

    Drop-off at each step, split by device and channel, because aggregates routinely hide a mobile experience that is quietly failing.

  • Defects fixed, not tested

    Broken validation, unlinked phone numbers, layout shift under a button. These get fixed and measured, not put into an experiment.

  • An honest read on sample size

    Whether your traffic can support testing at all. If it cannot, I will say so and we improve and measure period over period instead.

The process

Watch, fix, then test

  1. Watch and count

    Recordings of failed sessions plus segmented funnel data. Evidence before anyone offers an opinion.

  2. Fix the defects

    The things that are simply broken, fixed and measured before and after. No testing of whether broken is bad.

  3. Test where it is readable

    Genuine uncertainty, tested only where the traffic supports a conclusion. Otherwise improve and measure period over period.

Questions

Conversion optimisation questions

How much traffic do we need for this to work?

For A/B testing, enough conversions that a result is readable in a reasonable window, which for most businesses means a few hundred a month at minimum. Below that, testing is theatre. But conversion work itself still applies: watching recordings, fixing defects and removing friction works at any volume, and it is usually where the money is anyway.

Do you use heat maps?

Sparingly. Aggregate heat maps flatten several different behaviours into one colourful image that supports whatever you already believed. Individual session recordings are far more informative because you see the sequence: the hesitation, the scroll back, the second attempt at a field.

What if the problem is our offer, not our site?

Then I will tell you, and it happens. No amount of layout work fixes a proposition people do not want at the price you are asking. Recordings and exit behaviour usually make that visible quickly, and it is better to hear it in week two than after six months of testing.

How long before we see a change?

Defect fixes can move the number within days because you are recovering conversions you were already losing. Structural improvements take a measurement period to confirm. Anyone quoting a percentage uplift before looking at your funnel is guessing.

Next step

Watch ten recordings this week

Filter to sessions that did not convert on your most important page. It is uncomfortable and it is the fastest way to find out what is actually wrong.

  • Reply within 24h
  • Evidence-led
  • Honest about sample size
Get a Quote