15 Website Conversion Elements That Get Visitors to Contact You
15 website conversion elements that turn visitors into inquiries, from your headline and contact form to response times, pricing and mobile speed.

Freelance full-stack developer
- Published
- Reading time
- 13 min
In this post8
The website conversion elements that matter most for a service business are the ones that turn a visitor into an inquiry: a clear headline, one obvious next step, proof that others trust you, and a contact form that's quick to fill in and gets a reply on time. Below are the 15 I check first on any site, from the top of the homepage to mobile speed. Most of them cost more thought than money.
I use my own site, simonij.com, as an example along the way. It's built to win projects for a freelance developer in Denmark, so treat it as one working example rather than the rulebook.
The short answer
Here are the 15 elements, the question each one answers for the visitor, and roughly how much work it takes.
| Answers the question | Effort | |
|---|---|---|
| 1. A headline that says what you do | Is this for me? | Low |
| 2. One primary action per page | What do I do now? | Low |
| 3. Social proof next to the button | Can I trust them? | Medium |
| 4. A real face, name and location | Who am I writing to? | Low |
| 5. One page per service | Do they do exactly what I need? | Medium |
| 6. A price level | Can I afford this? | Low |
| 7. The process in a few steps | What happens after I write? | Low |
| 8. An FAQ that handles objections | The things I won't ask | Low |
| 9. A short contact form | Can I be bothered? | Low |
| 10. A response-time promise | Will anyone read this? | Low |
| 11. Booking or form, chosen on purpose | What's the first step? | Medium |
| 12. A confirmation page and email | Did my message get through? | Low |
| 13. Fast pages on mobile | Is this worth the wait? | Medium to high |
| 14. Mobile-first details | Can I do this on my phone? | Medium |
| 15. Tracking where inquiries come from | What works? (your question, not theirs) | Low |
My rule of thumb: fix 1, 2, 9 and 10 first. They often take an afternoon, and they're the ones I most often find missing. Speed and mobile take longer, and that's where a developer actually earns their fee.
If you're still deciding how the site should be built in the first place, start with my guide to building it yourself, using no-code or hiring a developer. This post is about what goes on the page, whichever tool you end up using.
Above the fold: message and trust
In a 2018 eye-tracking study by the Nielsen Norman Group, participants spent 57% of their viewing time above the fold (the part you see without scrolling) and 74% in the first two screenfuls. People do scroll. But the top of the page decides whether they bother.
1. A headline that says what you do and who it's for
"We craft digital experiences" could sit on a thousand websites. A useful headline names the service and the audience, and the subheading says what makes you different. "Bookkeeping for construction firms in Hamburg" tells a visitor more in two seconds than "Clarity in every detail" ever will.
Try the five-second test on someone who doesn't know you. If they can't repeat what you sell, rewrite the headline before you touch anything else.
2. One primary action per page
Every page needs one thing you most want the visitor to do, with the same button text repeated wherever it appears. Secondary actions, like "see our work", can stay, but they should look visibly weaker.
Make the button describe what happens next. "Submit" and "Contact" say nothing. On my own site the buttons say "Tell me about your project", because it sounds like the start of a conversation rather than a purchase.
3. Social proof right where people decide
Social proof means evidence from other people: client logos, testimonials and case studies. It works hardest next to the call to action and the form, where doubt peaks, not on a separate references page nobody opens.
A testimonial with a full name, job title and company persuades. "J.S., happy client" does the opposite. My rule is simple: no testimonials beats anonymous or invented ones. Ask your best clients for two or three sentences with a concrete outcome, and get their written approval to publish.
4. A real face, a name and a location
When you buy a service from a small company or a consultant, you're buying from a person. Show a real photo of whoever replies, and say who they are. Stock photos of handshakes make a site feel more anonymous, not more professional.
For buyers in another country, add where you're based and what time zone you work in. "Based in Denmark, working CET hours" answers a question many international visitors have but rarely send. On simonij.com the point is that I'm the one who replies and the one who writes the code, so that has to be visible.
Answer the questions people won't ask
Most visitors don't write in to ask questions. They close the tab when they can't find the answer. These four elements answer in advance.
5. One page per service
A homepage with six services in six boxes answers nothing. Give each service its own page: who it's for, what's included, a price level and a few common questions. Visitors from search and ads then land on a page that matches what they looked for, and Google gets one clear page per topic.
6. A price level, even if every project is different
"It depends" is true and useless. Give a range, a starting price or a plain list of what pushes the cost up or down. Most buyers would rather rule you out on price than sit through a call to find out.
My pricing page explains how I price work, including a paid, fixed-price discovery phase before larger builds. A visible price level also filters out inquiries that were never going to go anywhere. That's conversion too: fewer messages, better ones.
7. The process in three or four steps
"What happens after I write?" is a question almost nobody asks out loud. Answer it with three or four short steps, for example: the client writes, you reply within a set time, you have a short call, and the client gets a written proposal with a price before anything is agreed.
Keep the steps true. Don't promise a free workshop or a fixed price if that's not how you work.
8. An FAQ that handles real objections
A good FAQ doesn't explain what a website is. It handles the objections people have but don't type: What will it cost? How long does it take? Can I edit it myself? Who owns the result? What if we disagree halfway through?
Pull the questions from your own inbox and sales calls. Those are the ones clients actually ask, and they belong on the service page, close to the button.
The contact step itself
This is where interest becomes an inquiry, or doesn't. Small mistakes cost the most here.
9. A short form with labels above the fields
The Nielsen Norman Group's web form recommendations still hold up: keep the form short, use a single column, put labels above the fields, avoid placeholder text inside them, mark optional fields clearly and write specific error messages.
Ask only for what you need to send a useful first reply. My own form asks for name, email, company (optional), project type, budget, timeline and a short message. There's no phone field. The budget options are in euros, and "Not sure yet" is one of them, so nobody gets stuck on a number. If something goes wrong on submit, the text you typed stays in the form.
10. A response-time promise next to the button
The silent doubt behind every contact form is whether anyone reads it. One line under the button removes it: "I reply within 1 business day." Make the promise specific enough that a visitor can plan around it. If your buyers are spread across time zones, say which one your business day runs on.
I reply within 1 business day myself, so that line sits next to my buttons. Only promise what you can keep. A broken response-time promise does more damage than no promise at all.
11. Booking or form: choose on purpose
A booking calendar, such as Calendly or Cal.com, works when the first meeting is the same every time: a consultation, a demo, an advisory session. A form works better when you need to understand the job before you can say anything useful, because projects vary a lot. You can also combine them: form first, booking link in your reply.
On simonij.com I went with the form. A call where I don't know the project type or budget spends most of its time on questions a form asks in two minutes. If booking is the core of the business itself, say treatments or rentals, it's a software decision more than a conversion element. I've compared the options in custom booking system vs off-the-shelf.
12. A confirmation page that says what happens next
After someone hits send, they should see that the message arrived, get the response time repeated and know the next step. Send an automatic confirmation email as well. It proves the address was right, and it gives the client something to reply to if they remember a detail later.
The confirmation is also the natural point to record an inquiry, so you can see which pages produce them. More on that in number 15.
Speed, mobile and measurement
Visitors never see the last three elements directly. They just feel them.
13. Pages that load fast on a phone
Google measures speed and stability with three metrics called Core Web Vitals. According to Google's documentation, the largest element on the page should appear within 2.5 seconds, the page should respond to a tap within 200 milliseconds, and content should barely shift while it loads. Those targets should hold for at least 75% of visits, so slower phones count.
The usual culprits are oversized images and third-party scripts: chat widgets, tag managers, popups and embedded maps on every page. My own site has no cookie banner, no chat widget and no tag manager, which explains a lot of its speed. I've written up how I built simonij.com if you want the details.
14. Mobile-first details, including the form
Phone numbers and email addresses should be tappable links. Write the number in international format (+45 for Denmark, for example) so it works for visitors calling from abroad. Buttons need to be big enough for a thumb, and the email field should open the keyboard with the @ sign. On iPhones, Safari typically zooms into form fields with text smaller than 16 pixels, which makes a form feel clumsy.
The best test costs nothing: pick up your own phone and try to contact yourself. If it takes more than a minute, or you have to pinch and zoom, you've found something to fix.
15. Tracking where inquiries come from
Without tracking, conversion work is guesswork. At minimum, know how many inquiries you get each month and which pages they came from. That can be as simple as a hidden form field holding the page the visitor came from.
In the EU, analytics cookies generally need consent, and a consent banner is itself an obstacle between the visitor and your button. That's why my own site uses cookieless analytics and shows no banner. If your traffic is low, skip A/B testing (running two versions of a page against each other). It takes too long for the numbers to mean anything. Read your inquiries instead, and ask new clients what made them get in touch.
What I'd skip, and when you don't need a developer
Some of what gets sold as conversion optimization costs more trust than it earns:
- Popups and exit-intent overlays (windows that appear as you try to leave). They interrupt the exact reading that was supposed to convince someone.
- Chat with nobody on the other end. An unanswered chat box is a broken promise, and it slows the page down.
- Fake scarcity. "Only 2 spots left" works until someone notices it's never true. If you really are booked up, say when you're next available.
- Sliders and autoplay video at the top. The message changes before anyone finishes reading it.
- Five buttons with five different labels. One clear action beats several half-hearted ones.
Conversion work also won't fix a traffic problem. If the site gets almost no visitors, getting found comes first, and that's a different job.
And you may not need me, or any developer. If your site runs on Wix, Squarespace or WordPress, you can handle most of these 15 elements yourself: copy, buttons, testimonials, pricing, FAQ and form fields. A developer starts to make sense when the site is slow because of its theme and plugins, when the form has to talk to other systems, or when you want measurement without cookies. If you're unsure, work through the 10 questions on building your own website vs hiring a developer.
Next steps
Go through your own site with the table at the top and mark each element as done, missing or not sure. Start with the easy ones, and change one thing at a time so you can tell what made the difference. If you're relaunching, also run through the website launch checklist so the form and tracking work from day one.
If you'd rather have a site built with these elements in place from the start, here's how I build websites for businesses.
Frequently asked questions
What's a good conversion rate for a B2B website?
There's no single number that fits every site. Conversion rate depends on your industry, where the traffic comes from and what you count as a conversion. Compare your site against itself over time rather than against averages you find online. A B2B site with a handful of well-qualified inquiries a month can be doing far better than one with dozens that never turn into work.
How long before I can tell whether my changes work?
It mostly depends on how much traffic you get. With a few hundred visits a month, it usually takes several months before a change in inquiries is clear rather than noise. So change one thing at a time, note the date you did it, and watch both the number and the quality of the inquiries that follow.
Can I use client logos and testimonials on my website?
Only with the client's permission, ideally in writing. An email where the client approves the quote, the logo and any name or photo is usually enough. Under GDPR, a named testimonial with a photo is personal data, so keep the approval on file and take it down if the person asks. For anything legally unclear, check with an adviser.
Do I need live chat or a chatbot on my website?
Only if someone answers quickly, or the chatbot can genuinely answer the questions your clients ask. Otherwise it's an extra script that slows the page and a promise you don't keep. For most smaller B2B sites, a clear contact form with a response-time promise gets better results for less money.