Conversion rate optimization: more enquiries from the traffic you already pay for
CRO for sites that already have visitors — where people drop off, what gets tested first, and how long an A/B test must run before the result means anything.
The problem
A site gets three thousand visitors a month and produces twenty enquiries — under one percent — and the response is to increase the advertising budget so that more people arrive at the same page. It is the most common wrong reaction in digital marketing: instead of asking why the existing three thousand did not convert, money goes into new traffic that will leak away at exactly the same rate. Cost per visitor stays flat while cost per enquiry doubles, because the top of the funnel is being inflated while the hole in it is left alone. And the hole is almost always in identifiable places that show up in the data if anyone looks: a form with so many fields that people abandon it halfway, a headline that describes the company instead of answering what the visitor gets and why they should choose you, an action button sitting below content nobody scrolls past on a phone. Without measurement at each step, a business sees only the final enquiry number and guesses at the cause — changing things at random and never learning whether a change helped or simply coincided with a better month.
What we build
There is a diagnosis phase before a single word on the page is touched. Heatmaps show how far down people actually scroll, session recordings show where they hesitate, and funnel analysis shows which field of the form is the one they stop at. Out of that comes a ranked list of hypotheses, ordered by how many visitors each one affects rather than by how easy it is to change — the button seen by everyone outranks the paragraph seen by four percent. Typical early tests include cutting form fields down to what is genuinely required, rewriting the headline to state the outcome the customer gets rather than describing the company, and lifting the call to action high enough to be visible without scrolling on a phone. Each change runs as an A/B test with half the traffic on the old version and half on the new, and the test ends when it has collected enough data for a safe conclusion, not when enough time has passed: a few hundred visitors a month can mean four to six weeks, several thousand can mean two. Stopping a test early because the first few days look encouraging is the single most common mistake in this discipline, and it produces confident conclusions built on random variation.
What you get
- Visitor journey analysis identifying the drop-off point at each step
- Heatmaps and session recordings across your main landing pages
- Hypothesis list ranked by the share of visitors each change affects
- A/B tests run to a statistically valid sample size before any conclusion
- Per-test report comparing conversion rate of the old and new version
- Recommendation to ship the winning version, plus the next hypothesis to test
Stack
Timeline
There is no fixed end date here — the work runs in cycles gated by data rather than by calendar. Collecting enough behavioural data for a clear picture of the leaks takes two to three weeks. Each test then runs until its sample is large enough, which is four to six weeks on moderate traffic and less on higher volume. A full cycle from analysis to shipping a winner is typically two to three months.
Indicative cost
Two ways to buy it. The initial journey analysis and leak diagnosis is a standalone project from €500 and delivers a prioritized list you can act on with or without us. After that, tests are billed individually from €300 each, or as a continuous improvement retainer of €600 to €1,200 a month if you want a standing programme. No advertising budget is required, since the work uses traffic you already have.
Frequently asked questions
Is CRO worth it if my traffic is low?
At low volume A/B tests need many more weeks to reach a safe conclusion, but the heatmap analysis and form redesign help immediately without needing a test at all. Below a certain volume it is usually better to grow traffic and fix the obvious page-level obstacles in parallel.
How long should a test run before I stop it?
Until the sample is statistically valid, not until the number looks good — typically four to six weeks on moderate traffic. Ending a test early because the first results are encouraging is the most frequent error in CRO and reliably produces false conclusions that get shipped as facts.
What if none of the tests show an improvement?
A test with no winner is still information: it means the thing you tested was not the real obstacle, and you move to the next hypothesis on the list. No individual test is guaranteed to win, but each cycle eliminates explanations and narrows the search.
Do you need to change the site itself, and who does that work?
Winning variants have to be shipped into the real site to count. We can implement them ourselves if we built the site, or hand your developer a precise specification of the change. Either way nothing goes live permanently until the test that justified it has closed.
Who has access to the analytics and test data?
You do, fully. The measurement tools connect to your own Analytics property and the testing tool runs on your domain. We keep no copy of your visitor data, and when the engagement ends the entire measurement history stays with you.
Related services
Want to talk it through?
Tell us what you are trying to solve and we reply with a concrete proposal.
Get in touch