Business meeting around a table discussing growth
Business meeting around a table discussing growth

Traffic that does not turn into calls, bookings or quote requests is an expense, not an asset. Conversion-focused design is the unglamorous discipline of removing every reason a genuinely interested visitor might not act — and it usually costs nothing but attention.

Define the one action first

Almost every underperforming page we are asked to fix has the same defect: it wants several things at once. Call us, follow us, subscribe, download, book, read the blog. Presented with six equal options, most visitors choose the seventh — leaving.

So the first exercise is uncomfortable and short. For each page, write one sentence: "A visitor who reads this page should ___." One verb. Everything else on the page is either supporting that verb or competing with it.

BusinessPrimary actionSecondary
RestaurantBook a table or callSee the menu, get directions
Dental clinicRequest an appointmentCheck prices, read about a treatment
B2B supplierRequest a quoteDownload the price list
Apartment rentalSend a direct enquiryView photos, check availability

Secondary actions are allowed, but they must look secondary. One filled button and one text link, not two identical buttons side by side.

The first screen has one job: be understood

A visitor decides within a few seconds whether they are in the right place. In that time they need three facts: what this is, whether it is for them, and what to do next.

  • A headline that says what you do, not how you feel about it. "Family restaurant in Gràcia, open until midnight" beats "A passion for authentic flavours" every time we have tested it.
  • One supporting sentence answering the obvious follow-up: where, how much, how fast, for whom.
  • One primary button, using a verb the visitor would use: Book a table, not Learn more.
  • A trust signal within the first screen — a rating, a client name, a number of years, a certification.
  • The key practical fact visible without scrolling on mobile: opening hours, price from, or location.

Test: show your homepage to someone unfamiliar with the business for five seconds, then hide it and ask what the company does and what they would click. If they cannot answer both, the hero is decoration.

Proof, placed where doubt occurs

Proof works when it sits next to the specific worry it answers, not collected in a "Testimonials" section at the bottom that nobody scrolls to.

  • Next to the price: a client saying the price was fair and there were no surprise invoices
  • Next to the delivery promise: a client confirming it was delivered on time
  • Next to the form: how quickly you reply, and what happens after submission
  • Next to a technical claim: the number that supports it

Specificity is what makes proof believable. "Great service, highly recommended" persuades nobody. "Live in twelve days, first table booked the same evening" is credible because it is checkable. Always attribute: full name, role, business. Anonymous praise reads as invented, and often is.

Remove friction before adding persuasion

Most conversion problems are not persuasion problems. The visitor already wants to act and something is in the way. Find those things first — they are cheaper to fix and the gains are larger.

  • Hidden prices. If you cannot publish exact figures, publish ranges. "From €45" beats "Contact us for pricing", which most people read as "expensive".
  • A phone number that is not tappable on mobile — still one of the most common and costly bugs we find.
  • Menus and price lists as PDFs. They open slowly, zoom badly and are not searchable. Put them on the page as text.
  • Forms asking for more than you need to reply. Every extra field costs completions.
  • No opening hours, or hours only in an image.
  • Slow loading. Every second before the first paint is a percentage of visitors who never see any of this.
  • No confirmation after submitting, so people either give up or send it three times.

Form design, field by field

The form is where intent becomes an enquiry, and it is usually the least considered part of the page.

  • Ask only what you need to write back. Name, contact, message. Everything else can be asked in the reply.
  • Labels above fields. Placeholder-only labels vanish exactly when they are needed and fail for screen readers.
  • One column. Side-by-side fields cause skipping and are worse on mobile.
  • Mark optional fields, not required ones, if most are required — it makes the form look shorter.
  • Validate on leaving a field, not on every keystroke, and explain how to fix the problem.
  • Never clear the form on error. Retyping everything is where people give up.
  • Set expectations at the button: "Send — we reply within one business day" converts better than "Submit".
  • Confirm visibly, in place, and say what happens next.
  • Offer an alternative next to the form: phone, WhatsApp, e-mail. Some people will never use a form.

Anti-spam without punishing customers

Use a honeypot field and a simple time check rather than a puzzle. Visible challenges cost real conversions, and a hidden field that only bots fill in stops the overwhelming majority of automated submissions.

Buttons and calls to action

Small details in button design have disproportionate effects, because the button is where the decision physically happens.

  • Use the visitor's verb. Book a table, Get a quote, See prices — never Submit or Click here.
  • One primary button per screen. Two competing buttons halve the emphasis of both.
  • Make it visually distinct — the accent colour should belong to actions and to nothing else on the page.
  • Repeat it down long pages, roughly every screen and a half. People decide at different depths.
  • Add a sticky action bar on mobile for call or book. On phone-heavy sites this is consistently among the highest-impact changes we make.
  • Reduce perceived risk beneath it: "free, no obligation", "we reply within a day", "cancel any time".

Measuring on small traffic

Most local businesses do not have the traffic for reliable A/B testing. Twenty conversions a month cannot produce statistical significance in any reasonable timeframe, and pretending otherwise leads to confident decisions based on noise.

What works instead:

  • Track the actions, not just the pageviews. Calls started, forms sent, directions opened, menu viewed, WhatsApp opened. Without these you are guessing.
  • Watch session recordings and scroll depth on the pages that matter. Five recordings usually reveal more than five hundred sessions of aggregate data.
  • Make one substantial change at a time and compare month over month, keeping seasonality in mind.
  • Ask the people who convert. "What almost stopped you from getting in touch?" is the highest-yield research question available, and it costs one sentence in a reply.
  • Test with five strangers rather than five hundred visitors. Usability testing finds the blocking problems; A/B testing only refines what already works.

And keep the arithmetic honest. Going from 2% to 3% conversion is a 50% increase in enquiries with no additional traffic, no additional advertising, and no additional cost. That is almost always cheaper than buying half again as many visitors.

Questions people ask about this

For local service businesses, two to five per cent of visitors taking the primary action is typical, and well-optimised sites reach eight to twelve per cent on high-intent pages. The number matters far less than the trend: measure your own baseline and improve it.

In almost all cases yes, at least as a range or a starting figure. Hiding prices filters out fewer time-wasters than people expect and loses a large number of serious buyers who read 'contact us for pricing' as 'expensive'.

As few as let you reply usefully — commonly name, contact method and message. Each additional field measurably reduces completion, and anything you truly need can be asked in your first reply.

Only if you have enough conversions for the result to mean anything — realistically several hundred per month. Below that, usability testing with five people, session recordings and direct customer questions produce far more reliable improvements.

Only if somebody actually answers it quickly. An unanswered chat widget is worse than none, because it promises immediacy and then breaks the promise. For most small businesses a visible WhatsApp or phone button works better and costs nothing to run.

The short version

  • Write one sentence per page defining the single action it should produce
  • The first screen must say what you do, for whom, and what to do next
  • Place proof next to the specific doubt it answers, with names and numbers
  • Fix friction — hidden prices, PDFs, untappable numbers — before writing new copy
  • Ask only for what you need to reply; confirm visibly and set expectations
  • One primary button per screen, using the visitor's own verb, repeated down long pages
  • On small traffic, use recordings, five-person tests and customer questions, not A/B tests