Conversion rate optimisation grounded in commercial outcomes.

On-site optimisation inside a full engagement — measured in revenue per visitor, not test win rates.

See if we’re a fit

Most CRO programmes optimise for conversion rate in isolation.

The common failure modes: running A/B tests without enough traffic to reach significance. Improving conversion rate at the expense of average order value. Treating optimisation as a design exercise rather than a commercial one. Running tests on a separate brief from the team managing paid, so spend increases to a page that’s actively being changed.

Funnel analysis, structured testing, and page-level commercial optimisation.

Inside a Lumos engagement, optimisation covers the full purchase funnel: landing page performance by traffic source, product page conversion by category, checkout completion rate, and post-purchase flow. We test with a hypothesis and a statistical framework in place before we start — not because a button colour looked interesting.

Paid drives traffic to pages we’re actively optimising. SEO improvements and optimisation improvements are sequenced so they don’t conflict with each other.

Revenue per visitor, average order value, and checkout completion rate.

The commercial outcomes we work towards: revenue per visitor by traffic source, average order value across the funnel, checkout completion rate, and the contribution of product page improvements to overall category revenue. Conversion rate is a component, not the goal.

Do you run CRO as a standalone service?
No. Optimisation is one of four surfaces inside a retained engagement. Running tests in isolation from the team managing paid traffic and content changes produces slower, noisier results.
How much traffic do we need for testing?
Enough to reach statistical significance within a reasonable timeframe. As a rough guide, most product and category page tests require at least 1,000 sessions per variant per week to be meaningful. We assess this at the start of the engagement and adjust the testing programme accordingly.
Do you use specific testing tools?
We work with whatever testing infrastructure is already in place. We have experience with VWO, Optimizely, and Google Optimize (now sunset). We can recommend and set up tooling if needed.
What if our traffic is too low for A/B testing?
We shift focus to heuristic analysis and qualitative research — session recordings, user testing, and funnel analysis. Changes are made based on commercial reasoning rather than statistical tests until traffic supports a structured programme.

See if we’re a fit.

Thirty minutes. No pitch. We’ll both know quickly whether this makes sense.

Book a fit call

Read the full criteria first →

Retainer
From £1,750 + VAT / month
Projects
From £2,500 + VAT
Minimum term
6 months