Conversion Rate Optimization
I used to chase 50% lift on button colours until I found my conversion tracking was firing twice on every click – my tests were measuring noise.
What I’d do first
- Fix your conversion tracking in Google Analytics before any test – broken data makes every result suspect.
- Start with high-traffic or clearly underperforming pages; they give the fastest signal and biggest upside.
- Use heatmaps and session recordings to form hypotheses instead of guessing what might work.
- Test one variable per experiment so you know exactly what caused a change.
- Define a stopping rule before you start – never call a winner based on two days of data.
The path I'd take
Before anything else, I make sure tracking is solid. If your analytics are broken, every test you run is built on sand. I've seen teams spend weeks on a test only to realise the conversion event wasn't firing correctly. Painful. Set up goals in [Google Analytics](/google-analytics/) or key events in GA4. Check they're recording. Run a few test conversions yourself to confirm. Use [Google Tag Manager](/gtm/) if you need to deploy complex tags without a developer. Once tracking is verified, I move to analysis. I fire up a heatmap and session recording tool – Hotjar or Microsoft Clarity are free to start. I look for where people drop off. Do they hesitate on the form? Click a broken link? Leave after seeing the price? I write down every friction point. This is where [SEO Analysis](/seo-analysis/) methods overlap – you're looking for user behaviour signals that indicate why a page doesn't convert. After collecting observations, I form a hypothesis. For example: "If I move the CTA above the fold on this product page, more visitors will see it and click through to checkout." Then I design an A/B test that changes only that one element. I let it run until it reaches statistical significance, usually at least a week to capture day-of-week patterns. I avoid checking results daily. Finally, I assess the business impact. A 10% lift on a page with 500 monthly visits is worth less than a 5% lift on a page with 5,000 visits. I prioritise pages that compound the most value. Once a test settles, I either implement the winner or document the learnings and move to the next hypothesis. I repeat this cycle, but I don't test every page. I stop when the effort-to-return ratio drops – if squeezing another 1% takes three weeks, I'd rather optimise a different page or channel.
Watch-outs
A few traps I've fallen into myself. Testing too many things at once. If you change the headline, button colour, and image all in one test, you won't know what caused the lift. Test one element at a time. Stopping a test too early. I once called a winner after two days because the variant was up 20%. By day five, it was flat. Let tests run to significance. Ignoring mobile traffic. Your desktop conversion rate might look fine, but mobile could be half that because of a missing tap target or slow load. Segment your results by device. Focusing only on the conversion rate itself can mislead. A higher conversion rate can come with lower average order value or higher bounce on later pages. Look at downstream [SEO Metrics](/seo-metrics/) like revenue per visitor or lead quality. Another trap: testing on a page with low traffic. You might need months to reach significance. Instead, use qualitative methods like user surveys on low-traffic pages, and save A/B testing for pages with sufficient volume. Don't trust a small sample. If you only have 100 visitors a week, a 5% conversion change could just be noise. Use a calculator to determine required sample size before starting. Also, changing the baseline while running a test – if you launch a campaign or your site gets a redesign mid-test, your results become useless. Freeze the environment. Finally, check your tracking again after making changes. A new button might break the conversion event. Always verify the test is recording correctly before you analyse the results.
What I got wrong
I have a list of blunders. The biggest: I once ran an A/B test on a page that got 300 visits a month. After two weeks, the variant had 12 conversions versus the control's 8. I called it a winner. Statistically, it was meaningless. I learned to use sample size calculators and set a threshold upfront. Another mistake: I optimised for click-through on a CTA without caring what happened after. The new button increased clicks by 30%, but the subsequent page had a terrible drop-off because I hadn't tested the flow end-to-end. The conversion rate actually dropped. Now I always map the entire conversion path. I also got wrong the idea that CRO is a separate discipline from SEO. Improving page speed, removing intrusive interstitials, writing clearer copy – all of these are CRO actions that also help organic performance. I used to think I could hand off CRO to a specialist and ignore it. Now I consider it part of [SEO Results](/seo-results/) management. Another admission: I ignored the impact of seasonality. I ran a test in December on an e-commerce site and saw a huge lift, implemented it, then in January the conversion rate tanked. The test had been confounded by holiday buying intent. I now run tests for at least one full business cycle. Finally, I underestimated the value of simple fixes. I spent weeks on a complex multivariate test when just fixing a broken link on the checkout page would have gained a 5% lift. Always start with the obvious bugs.
Next step
Quick answers
When should I stop an A/B test?
Stop when you reach statistical significance (usually 95% confidence) and you have run for at least one full business cycle to account for day-of-week effects. If after two weeks the result is not significant, the effect size is likely too small to be worth implementing. Never stop because the variant is temporarily ahead – that's a common trap.
What is a good conversion rate?
There is no universal benchmark – it depends on industry, traffic source, and conversion definition. For e-commerce, 2-3% is typical. For B2B demo requests, 1-2% is common. The best benchmark is your own historical baseline. I compare against the same period last year to account for seasonality. Focus on improving from your own starting point.
Do I need Google Analytics for CRO?
You need a tool that can reliably track conversion events, segment traffic, and export data. Google Analytics is free and widely used, but alternatives like Mixpanel or Heap work too. The key is accurate, consistent tracking before you start testing. I use GA4 because it integrates with most testing platforms. Without a proper analytics setup, test results become unreliable.
Sources
Primary documentation is linked directly. Anything commercial is marked nofollow.
- Google Analytics documentation — Explains how to set up conversion goals and key events, which is the foundation of any CRO programme.
- Google Search Central — Provides authoritative guidance on page quality and usability – both critical for reducing friction that hurts conversions.
- Optimizely CRO glossary — Gives a clear definition of CRO and outlines the standard workflow from analysis to testing to iteration.
- VWO CRO guide — Details A/B testing methods, behavioural analysis tools like heatmaps, and UX improvements that I reference in the playbook.
Notes from Callum Bennett.