Conversion Rate Optimisation: Practical Wins for UK Sites
Table of Contents
Conversion rate optimisation is the work of getting more enquiries, calls or sales out of the visitors a website already has. For most small and medium businesses in the UK and Ireland, that work is not split testing. It is a short list of fixes to clarity, forms, proof and page speed, applied in a sensible order and then checked against the enquiries that actually land in the inbox. This page covers what the work involves, which changes are available inside a month, why formal testing rarely suits a site under a few thousand monthly visits, what to do instead, and where conversion sits inside a wider site review.
AI Summary
Conversion rate optimisation is the practice of raising the share of website visitors who complete a defined action, such as submitting an enquiry form, calling, or buying. On a small business website the useful work is rarely A/B testing, because reliable testing needs thousands of visitors per variant on the page being tested. The four changes that pay back fastest are clarity about what the business does and what happens next, shorter forms that ask only for what is needed to reply, specific named proof placed beside the call to action, and a mobile page that loads quickly.
Progress is judged by counting real enquiries against a written log of what changed and when, not by watching a percentage move week to week. Conversion is also the fourth layer of a full website audit, which is why a site with traffic and no enquiries is usually a diagnosis problem before it is a design problem.
What Does Conversion Rate Optimisation Actually Involve?
Four things, in this order: decide what counts as a conversion, measure it honestly, find where visitors stop, then change the page and check what happened. Skip the first two and everything after becomes decoration.
A conversion is whatever action matters commercially. For a professional services firm that is usually an enquiry form or a phone call. For a shop it is a completed order. Smaller steps, such as reaching the pricing section or starting a form, are worth tracking as diagnostic markers, but they are not the number the business runs on. This work goes wrong most often at this first step, where a site tracks page views enthusiastically and enquiries not at all.
The second common failure is treating this as cosmetic. Button colours and hero image swaps get all the attention because they are easy to change. The gains sit somewhere less exciting: whether a visitor can tell within a few seconds what the business does, whether the page states what happens after they get in touch, and whether the form asks for three things or eleven. Much of that is decided when a site is designed and built rather than afterwards, which is why a page that resists every improvement is sometimes telling you the template is the problem.
ProfileTree is a web design and digital marketing agency based in Belfast, and its web design work for businesses across Northern Ireland and Ireland starts from what a page is meant to achieve rather than from a layout.
The third thing worth naming early: conversion rate optimisation does not manufacture demand. If the traffic arriving is looking for something the business does not sell, no amount of page work will fix that. Sorting the traffic question comes first, and it is a different job.
Which Conversion Rate Optimisation Wins Are Available This Month?
Four, and none of them requires a testing tool or a redesign. Clarity, forms, proof and speed account for most of the improvement available on a typical SME site, and all four can be done inside a month by a small team.
| Quick win | What the change looks like | Who does it | Typical effort |
|---|---|---|---|
| Clarity | Rewrite the H1 and the first two lines to state what the business does, who for, and what happens after contact | Whoever writes the copy | An afternoon per page |
| Forms | Cut fields to what is needed to reply, add inline error messages, set the right mobile keyboard | Developer, with the owner deciding what to drop | Half a day |
| Proof | Move named, specific reviews and accreditations next to the call to action instead of a separate page | Marketing, plus a design tweak | A day, once the material is gathered |
| Speed | Compress and correctly size images loading above the fold on mobile, defer what is not needed immediately | Developer | Half a day to two days |
Clarity: say what you do and what happens next
Most service pages describe the service and never describe the transaction. A visitor who is close to enquiring wants to know three things: is this for a business like mine, roughly what does it cost, and what happens if I fill this in. The third is the one almost nobody answers. A single line near the form saying that enquiries get a reply within one working day, and that the first conversation is a short call rather than a sales meeting, removes a real hesitation at no cost.
Pricing belongs here too. Where search queries for a service are dominated by cost phrasing and the page carries no number, visitors leave to find one elsewhere. A published range with the variables named beats silence, and it filters out enquiries nobody wanted.
Forms: ask for less
Every field is a small reason to stop. The test is simple: does the business genuinely need this information to send a useful reply? Company size, budget bands, a referral source question and a mandatory phone number rarely pass it. Those questions can be asked in the reply, when the person has already decided to talk.
Three technical details matter more than they sound. Inline validation catches an error while someone is still looking at the field rather than after they press send. Correct input types bring up the numeric keypad for a phone number and the address keyboard for an email on mobile. Postcode lookup saves four fields on any form that needs an address. These are development jobs, not copy edits, and they hold up better than generic advice to shorten the form.
Proof: name the source
Unattributed praise reads as decoration. A quote with a full name, a company and a specific outcome reads as evidence. Google reviews carry weight partly because they sit outside the company’s control, and a rating with a review count beside the call to action does more than the same rating buried on a testimonials page.
For business buyers, specificity beats warmth. “Delighted with the service” is worth less than a line naming what was delivered, in what timeframe, and what changed as a result. Professional body memberships, accreditations and local association listings do similar work for buyers who are trying to establish that a supplier is accountable to somebody.
Speed: fix the mobile hero first
Slow pages lose visitors before the message loads, and the damage concentrates on mobile. Google’s Core Web Vitals documentation sets the thresholds worth measuring against, and Largest Contentful Paint is the one that usually fails on a business site. The cause is almost always the same: uncompressed hero images at desktop dimensions being served to a phone.
Fixing that one thing is frequently the largest single improvement available on an older site, and it is measurable before any visitor behaviour is considered. Speed work also has the advantage of being uncontroversial internally, since nobody argues in favour of a slower page.
Can a Small Website Run A/B Tests Properly?
Usually not, and the honest arithmetic is the reason. A/B testing needs enough conversions per variant to separate a real difference from random variation, and on a site taking a few hundred visits a month there is no honest way to get there inside a useful timeframe.
The standard sample size calculation makes this concrete. Assuming 95% confidence, 80% power and a two-sided test, detecting a 20% relative improvement takes roughly the following number of visitors per variant, on the specific page being tested:
| Current conversion rate | Visitors needed per variant | What that means on a site with 1,000 monthly visits to that page |
|---|---|---|
| 1% | About 39,600 | Roughly six and a half years for one test |
| 2% | About 19,600 | Roughly three years for one test |
| 3% | About 12,900 | Roughly two years for one test |
| 5% | About 7,600 | Roughly fifteen months for one test |
Those figures come from the usual approximation for comparing two proportions and can be reproduced in any sample size calculator. They soften if the change is dramatic: chasing a 50% relative lift from a 2% baseline needs closer to 3,100 visitors per variant rather than 19,600. That is the honest case for testing on a small site. Test only changes big enough to move the number substantially, and accept that subtle refinements are beyond reach.
Two related traps deserve naming. Stopping a test the moment it looks significant produces false winners reliably, which is why a fixed run of at least two full business weeks is the standard discipline. And in the UK, analytics and testing cookies need active consent before they are set, so the sample being measured is already a subset of real visitors. The Information Commissioner’s Office guidance on cookies is explicit that a banner offering only “accept” does not meet the standard. A test result drawn from the people who accepted tracking is not automatically a result about everyone.
How Do You Tell Whether a Change Worked Without a Test?
You count enquiries, you keep a written log of what changed and when, and you judge direction over three months rather than significance over three weeks. This is weaker evidence than a controlled test and it is the right method for most SME sites, because the alternative is not a better method but no method.
The log is the part people skip and the part that makes everything else work. One line per change: the date, the page, what was altered, and the number of enquiries in the four weeks before. Without it, three changes land in the same fortnight and nobody can say afterwards which one mattered. With it, a year produces a genuine record of what this particular audience responds to.
Watch for the obvious confounders. Traffic mix moves, seasons move, a supplier runs a campaign, a competitor closes. If enquiries rise while sessions rise by the same proportion, the page did nothing and the traffic did the work. Checking the enquiry count against sessions from the same channel is enough to catch most of this, and ProfileTree’s guide to the five website numbers worth checking every week covers where those figures sit in Google Analytics 4.
The other half of the answer is qualitative, and it scales down far better than testing does. Watching four or five people attempt an enquiry on your own site surfaces friction that no dashboard reports. Session recordings show where visitors hesitate and where they tap things that are not clickable. The enquiries and phone calls you already receive are research material: the questions people ask before committing are, almost always, the questions the page failed to answer.
“Businesses often assume they understand their customers, but proper research reveals surprising gaps. Someone might visit your site with a completely different intent to the one you’re designing for, and understanding that changes your whole approach to it,” says Ciaran Connolly, founder of ProfileTree.
How Does Conversion Rate Optimisation Fit With a Website Audit?
Conversion is the fourth layer of a structured site review, after technical health, content and search visibility, and user experience. The audit finds the leak and ranks it; conversion rate optimisation is the work that follows. Running the second without the first is how businesses end up rewriting a page that search engines cannot reach.
The order matters because faults in one layer masquerade as faults in another. A service page with a poor enquiry rate might have a copy problem, or it might be ranking for queries the business does not serve, or it might take eight seconds to load on a phone. Those three have nothing in common except the symptom. A website review across technical, content, experience and conversion layers separates them before any money is spent on a fix, and it publishes a starting price rather than quoting on how the client looks.
The video below walks through the mechanics of reviewing a site, which is useful background before deciding where conversion work belongs in the queue.
There is a sequencing rule worth holding to. Fix anything that stops a page working at all, then fix clarity, then measure, then optimise. Businesses that reverse this spend months refining a call to action on a page that was never being seen.
What Should You Do First?
Pick one page. Not the homepage, and not all of them: the page that already brings people in and should be producing enquiries. Confirm the enquiry is being tracked at all, because a surprising share of sites have twelve months of traffic data with no record of which pages produced business. Then work through clarity, forms, proof and speed in that order, changing one thing at a time and writing down what you did.
Review after a month, and expect the first cycle to teach you more about your own measurement than about your visitors. That is normal. The second cycle is where the useful answers start, and by the fourth you have something most competitors do not: a record of what works on your site rather than a collection of opinions about what works generally.
ProfileTree works with businesses across Northern Ireland, Ireland and the wider UK on exactly this, combining design and development with the measurement needed to tell whether a change did anything. If a site is attracting visitors and producing very few enquiries, talk to the ProfileTree team in Belfast about a scoped review of where the drop-off sits.
FAQs About Conversion Rate Optimisation
These are the questions business owners ask most often when a site is producing traffic and not much else.
Why does my website get visitors but no enquiries?
Three causes account for most cases, and they are separable. The first is that the visitors are the wrong ones: they arrive on a page ranking for a query the business does not actually serve, read one line, and leave. The second is that nothing on the page tells them what to do or what happens next, so the visit ends without a decision. The third is that enquiries are happening and nobody is recording them, which is more common than it sounds on sites where the form has no tracked event. Check the third first, because it costs nothing and it changes how you read everything else.
What is a good conversion rate for a UK business?
There is no benchmark worth chasing, and figures quoted as one are usually averages across wildly different businesses. A local trade taking twelve enquiries a month from 400 visits is doing better than a firm taking three from 40,000, and the two are not comparable on rate alone. The only meaningful comparison is your own page against itself over time, with the enquiry count as the headline figure and the percentage as context.
I have changed my homepage three times this year and nothing has improved. What am I doing wrong?
Most likely two things. The homepage is rarely where enquiries are won on a service site, because visitors from search usually land deeper, so changes there affect a smaller share of traffic than expected. And changing several elements at once removes any chance of learning which of them mattered. Pick the page that receives the most relevant traffic, alter one element, write down the date, and give it four weeks before judging. If three cycles of that produce nothing, the problem is probably not on the page at all, and it is worth checking what queries are bringing people in.
Do I need an A/B testing tool?
Only if the page being tested receives thousands of visits a month. Below that, a testing platform produces results that look authoritative and are driven by noise, which is worse than having no result. Session recording and heatmap tools are the better purchase at small scale, and Microsoft Clarity offers unlimited session recordings free, with a Google Analytics 4 integration.
How long does conversion rate optimisation take to show results?
Technical fixes such as page speed show up immediately in measurement, though the commercial effect takes a few weeks to read. Copy and form changes need four weeks minimum before the enquiry count means anything, and longer on low-traffic pages. Anyone promising a measurable uplift in a fortnight on a site taking a few hundred visits is describing a coincidence.
What is the difference between conversion rate optimisation and a website audit?
An audit is a diagnosis across the whole site; conversion rate optimisation is a treatment applied to specific pages. The audit tells you whether the enquiry problem sits in technical health, search visibility, user experience or the page itself. Conversion work assumes that question is already answered, which is why it is usually the second purchase rather than the first.
Does conversion rate optimisation help or hurt SEO?
It generally helps, with one technical caveat. Clearer pages, faster loading and content that answers the question being asked all support search performance rather than working against it. The caveat is that badly implemented testing scripts can cause visible layout shift while a page loads, and layout shift is measured directly by Core Web Vitals. If a testing tool is being added, that is the thing to check.
Can I do this on a Wix or Squarespace site?
Yes for most of it. Copy, form length, proof placement and calls to action are all editable on hosted builders, and those four cover the majority of the available gain. What is harder is deep technical work: image delivery, script control and custom tracking are more limited than on a self-hosted platform, so speed improvements tend to hit a ceiling sooner.
How much does conversion rate optimisation cost?
It depends entirely on whether the work is a one-off pass over a handful of pages or an ongoing programme, and on how much development the fixes need. A useful way to scope it is to start with a review that ranks the problems by commercial impact, then price only the top three items. Paying for a testing programme before that ranking exists is how budgets get spent on the wrong page.