Link to this article
Found this useful? Add a link to it from your own website.
Choose the wording that fits your article, then copy the link.
Here’s something I’ve been thinking about a lot recently.
Businesses are constantly being told they need more traffic.
More SEO.
More Google Ads.
More social media.
More people visiting the website.
But what if you’ve already got visitors?
What if people are finding you, looking around and reading your content – but your inbox is still suspiciously quiet?
Maybe you don’t need more traffic.
Maybe you need to do more with the traffic you’ve already got.
If 1,000 people visit your website and nobody enquires, getting another 1,000 people to the same website isn’t necessarily going to solve the problem.
A website needs to move the right visitor forward.
And that means looking at what happens between someone finding your website and actually getting in touch.
I’ve spent a lot of time looking at this recently – including our own Ullmatech site, and there are some surprisingly common things that get in the way.
So here are 10 things I’d look at before spending another penny trying to send more people through the door.
It sounds obvious, but getting people to your website isn’t the same as getting the right people to your website.
You could spend months improving your search rankings, increasing your social reach and driving more visitors to your site – and still see very few enquiries if the people arriving aren’t actually looking for what you sell.
Imagine a company that provides specialist industrial automation services ranking highly for a broad search such as “automation”. It might generate plenty of traffic, but some of those visitors could be students, job seekers, people researching the subject or businesses looking for something completely different.
The traffic looks good in the analytics.
The enquiries don’t.
Someone searching for:
what is industrial automation?
has a very different intention from someone searching for:
industrial automation company UK
And someone searching for:
automate invoice processing for manufacturing
is potentially even closer to becoming a customer.
The job of your website isn’t necessarily to attract the largest possible audience.
It’s to attract the audience most likely to need what you offer.
Before worrying about traffic, you need to be clear about who you actually want visiting the site.
That might mean targeting:
That should influence everything from the keywords you target and the content you create to the landing pages you build and the campaigns you run.
There’s nothing wrong with seeing your visitor numbers go up. But pageviews are only useful if they’re moving you towards something.
A website getting 10,000 visitors a month but generating five relevant enquiries may be considerably less valuable than one getting 1,000 visitors and generating 20.
That’s why good SEO isn’t simply about getting your website to rank for as many searches as possible.
It’s about being visible when the right person is looking for the right thing.
There’s another common problem.
Someone clicks on a search result expecting:
Website design for engineering companies
Welcome to our website. We provide innovative digital solutions…
The visitor hasn’t necessarily found the wrong website.
But they haven’t found the answer they were looking for either.
The landing page needs to match the reason they clicked.
The search, the message and the page all need to line up.
This is one of the quickest ways to lose a potential customer.
Someone lands on your homepage and, within a few seconds, they should be able to answer four very simple questions:
They shouldn’t have to hunt around your navigation, decode a clever headline or scroll through three paragraphs of company history to work it out.
There’s a temptation to make website messaging clever.
You might have a beautifully written headline that sounds great in a boardroom but doesn’t actually tell anyone what you sell.
Something like:
Engineering a better tomorrow.
Sounds nice.
But what does the company actually do?
Or:
Solutions that move your business forward.
Great.
Which solutions?
And for which businesses?
There’s nothing wrong with having a distinctive brand voice or an interesting headline. But clarity has to come first.
Your visitor shouldn’t need to figure out what you mean.
Another common problem is putting too much emphasis on the business itself.
That information might be useful later, but it’s rarely the most important thing to someone who has just arrived.
They’re not thinking:
Tell me about your company
They’re thinking:
Can you solve my problem?
The homepage should make that connection obvious.
Here’s a simple test you can run without any analytics tools.
Show your homepage to someone who doesn’t know your business.
Give them five seconds.
Then ask:
If they can’t give you a reasonably accurate answer, you’ve got a messaging problem.
And don’t help them.
Don’t say:
Well, we’re actually a specialist provider of…
If you have to explain what the website means, the website hasn’t done its job.
This doesn’t mean every homepage needs a huge headline saying:
WE SELL INDUSTRIAL PUMPS.
Good website copy can still have personality.
The trick is to make the interesting bit sit alongside the useful bit.
For example:
Once those four things are established, you can be as creative as you like further down the page.
This is one of the easiest mistakes to make.
You know your business inside out. You know when it was founded, how experienced your team is, the products you sell and all the things you’re particularly proud of.
So naturally, that’s what you write about.
There’s nothing necessarily wrong with any of those statements.
The problem is that none of them answer the question that’s going through your visitor’s head:
“Can you solve my problem?”
Imagine someone has arrived at your website because they’re looking for a solution.
They might be thinking:
And then your homepage tells them:
“We’ve been established since 1998 and have a highly experienced team.”
That’s information about you.
It might be useful later.
But it doesn’t necessarily help them decide whether you’re worth talking to.
When writing or reviewing a page, try replacing:
That small change can completely alter the way you structure a website.
Instead of simply listing your services, explain the problems those services solve.
Instead of listing features, explain what those features mean for the customer.
Instead of saying you’re experienced, show why that experience matters.
Instead of ending with “Contact us”, tell them what happens when they do.
This is particularly important when describing products and services.
A company might say:
Our software integrates with your existing CRM.
WHAT IT DOESKeep your existing CRM while removing the need to enter the same information twice.
WHY THEY CAREThat’s an outcome.
The feature explains what it does.
The benefit explains why they should care.
That’s the difference.
This doesn’t mean your website should become a bland collection of:
Problem → Solution → Buy Now.
Your story, experience, people and personality still matter.
In fact, they’re often an important part of building trust.
It’s simply about putting them in the right place.
Your visitor’s problem should generally come before your company history.
Your customer’s desired outcome should come before a list of internal capabilities.
And your explanation of why you’re different should connect back to something the customer actually values.
So you’ve got someone to your website.
They’ve understood what you do.
They’ve recognised that you might be able to solve their problem.
Now what?
This is where plenty of websites fall down.
They finish explaining the company’s services and then, almost as an afterthought, put a button at the bottom saying:
Contact us
That’s technically a call to action.
But it’s not necessarily a useful next step.
Imagine you’ve spent ten minutes researching a company.
You’ve read about its services.
You’ve looked at some examples.
You’re interested, but you’re not quite ready to speak to someone.
Then you see:
CONTACT US
-What happens next?
-Do you have to fill in a form?
-What should you ask?
-Will someone call you?
-Are you asking for a quote?
-Is it just an enquiry?
-How long will they take to respond?
Suddenly, the visitor has another decision to make.
And if they aren’t ready to make that decision, they might simply leave.
Not everyone arriving on your website is ready to buy.
Some visitors are just discovering you.
Some are researching a problem.
Some are comparing suppliers.
Some are almost ready to make a decision.
And some already know exactly what they want.
They shouldn’t all be given the same CTA.
| Visitor is thinking… | A better next step might be… |
|---|---|
| “What exactly is this?” | See how it works |
| “Could this solve my problem?” | Explore the solution |
| “Is this suitable for my business?” | Talk to an expert |
| “What would this cost?” | Get a quote |
| “I want to see what they can do.” | View case studies |
| “I need to check my own website.” | Check your website for free |
| “I’m not ready to talk to anyone.” | Download the guide |
| “I want to try it.” | Try the tool |
The important thing isn’t the exact wording.
It’s that the action makes sense given what the visitor has just learned.
This is particularly important on larger websites.
Imagine a visitor reading a page about a particular service.
You’ve just spent several paragraphs explaining:
And then the only option is:
Contact us
You’ve thrown away an opportunity to make the next step more relevant.
That’s much more specific.
The second CTA isn’t asking the visitor to buy anything.
It’s giving them something useful to do.
A visitor shouldn’t necessarily go:
Website → BUY NOW
They might go:
Website → Learn → Explore → Check → Compare → Talk → Buy
The website’s job is to help them move through that journey.
That’s why a CTA that works brilliantly on one page might be completely wrong on another.
They’re all trying to move the visitor forward.
But they’re meeting the visitor where they are.
This is probably the key point of the whole section.
If somebody has just discovered your company, “Buy now” isn’t necessarily the right next step.
You might need to give them:
before they’re ready.
And that’s particularly relevant in B2B, where the buying process can involve multiple people and decisions rarely happen from a single button click.
The website isn’t necessarily there to close the sale.
Sometimes its job is simply to get the visitor to the next sensible stage of the conversation.
A good CTA answers:
What happens if I click this?
The more uncertainty you remove, the easier it becomes for someone to take that next step.
Getting someone to your website is one thing.
Getting them to believe that you’re actually capable of solving their problem is another.
And the type of trust someone needs isn’t always the same.
A consumer buying a £30 pair of headphones might make a decision based on a few hundred reviews and a 4.8-star rating.
Someone considering a £100,000 piece of industrial equipment, a new business-critical software system or a major professional service purchase is probably going to want rather more reassurance.
For B2C, reviews, ratings, customer photos and social media can be hugely influential.
People often want to know:
That’s why things like star ratings, customer reviews, user-generated content and social proof can work so well.
Particularly when the purchase is expensive, technical or involves several people in the decision, the visitor may be looking for very different evidence.
They might want to know:
That’s why a website selling complex B2B products or services shouldn’t necessarily copy the trust signals used by an online clothing retailer.
The underlying principle is the same:
Give people evidence.
But the evidence needs to be relevant to the decision they’re trying to make.
We’re experts in our field.
ANYONE CAN SAY ITThere’s another trap here.
A company might put a huge list of logos on its homepage:
Company A | Company B | Company C | Company D | Company E
It looks impressive.
But a visitor might still be thinking:
Okay… but have they actually done anything relevant to me?
One detailed case study about a problem similar to theirs can sometimes be more persuasive than twenty logos.
Likewise, saying:
We’ve got 25 years of experience.
isn’t the same as demonstrating what that experience has enabled you to do.
Experience is a claim.
A project, result, case study or demonstration is evidence.
That’s an important distinction.
This is one of the simplest principles you can apply to a website.
If you say you build websites:
Show them one.
If you say you build interactive tools:
Let them use one.
If you say you improve website performance:
Show people what you’re checking and why it matters.
If you say you understand a particular industry:
Demonstrate that knowledge.
If you say your process produces better results:
Show the process and the outcome.
The more you can replace:
We’re really good at this.
with:
the less the visitor has to take your word for it.
This is something I think gets overlooked.
Your website isn’t just somewhere to talk about what you can do.
It can actually be part of the evidence.
An interactive calculator demonstrates technical capability.
A useful tool demonstrates that you understand a problem.
A detailed case study demonstrates experience.
A well-designed website demonstrates that you know how to design websites.
A fast website demonstrates that you take performance seriously.
You can even turn an assessment into part of the experience.
Instead of saying:
We’re experts in website performance.
you can say:
We’ll check your website and show you what we find.
Now you’re demonstrating expertise rather than simply claiming it.
And that’s where tools such as the Ullmatech Website Health Check become particularly useful.
It isn’t simply another sales pitch.
It’s an opportunity to let someone experience a small part of what Ullmatech can do before they ever become a customer.
There’s another important point here.
Trying to put every award, accreditation, client logo, testimonial, case study and certificate you’ve ever received onto your homepage can actually have the opposite effect.
It becomes noise.
Trust isn’t about throwing as much evidence as possible at someone.
It’s about providing the right evidence at the right point.
Someone looking for a website redesign might want to see your previous websites.
Someone considering a technical integration might want to see relevant technical experience.
Someone questioning whether you’re established enough might care about your track record and clients.
Someone who has almost decided but wants reassurance might want testimonials or a case study.
Relevance beats volume.
People don’t always arrive at your website ready to buy.
Often, they’re trying to work something out.
They’ve got a problem, they’ve found a few potential suppliers and they’re doing their research.
And that research usually involves questions:
Can you integrate with our CRM?
How long will this take?
Have you done something like this before?
What happens after I enquire?
Do you work with businesses like ours?
How much does it cost?
These might seem like fairly obvious questions to someone inside the business.
But if the website doesn’t answer them, the visitor is left with two choices:
Ask you.
Or find someone else who has already answered them.
And increasingly, people will simply choose the second option.
This is particularly important in B2B.
Someone might visit your website several times before ever contacting you.
They might be comparing suppliers.
They might be trying to convince a colleague or manager that your solution is worth considering.
They might be trying to understand whether your product will work with their existing setup.
They might simply be trying to establish whether you’re credible enough to contact.
Every useful piece of information you give them removes another reason to leave.
Instead of starting with:
What blog post should we publish this month?
start with:
What are our customers constantly asking us?
Those questions are often where your best content ideas are hiding.
If customers regularly ask:
“How long does implementation take?”
Answer it on the website.
If they ask:
“Does it integrate with X?”
Answer it.
If they ask:
“What’s involved in changing from our existing system?”
Answer it.
If they’re always asking:
“How much does something like this cost?”
Explain the factors that affect the price, even if you can’t give them an exact figure.
Your sales team may already have years’ worth of content ideas sitting in their inboxes.
This is where I think businesses sometimes get distracted by the idea that they need to become a publishing company.
You don’t necessarily need to produce three blog posts a week.
The useful information could take many different forms:
The format matters far less than the usefulness.
It’s easy to think of content as something the marketing department produces to get traffic.
A blog post gets published.
It gets shared.
Someone reads it.
Then everyone moves on to the next article.
But useful content can do much more than that.
A good article can answer an objection before someone contacts you.
A case study can demonstrate that you’ve solved a similar problem.
An FAQ can remove uncertainty.
A calculator can help someone understand the financial implications of a decision.
A guide can help someone build the internal case for buying your product or service.
An interactive website tool can demonstrate your expertise without asking the visitor to speak to anyone.
That’s not just marketing.
That’s part of the sales process.
One of the easiest ways to improve this is simply to listen.
Look at:
If you keep hearing the same question, your website should probably answer it.
And once you’ve answered it properly, you can reuse that information everywhere.
Your sales team can send the page to prospects.
Your support team can send it to customers.
Your marketing team can use it to create content for your social channels.
Your SEO can benefit from it.
And your potential customer gets the answer without having to wait for someone to reply.
There’s another mistake worth mentioning.
Sometimes the information exists – but it’s buried.
You might have a brilliant 20-page PDF explaining your product.
But if someone has to fill in a form, provide their email address, wait for an automated message and download a 14MB document just to find out whether you integrate with their CRM…
they’re probably going to look somewhere else.
Not everything needs to be gated.
Sometimes the best thing you can do is simply give people the answer.
Trust that if the information is useful enough, they’ll remember where they found it.
Your website might contain all the right information, but that doesn’t mean it’s easy to use.
A visitor shouldn’t have to think too hard about where to click, what something means or where to find the information they’re looking for.
Every extra bit of friction creates another opportunity for them to leave.
And the frustrating thing is that businesses often know their own website so well that they don’t notice it.
You know where everything is.
You know what your internal terminology means.
You know which menu contains which service.
You know that the little icon in the top-right opens the search.
Your visitor doesn’t.
This is a particularly common problem with B2B websites.
The company’s internal structure makes perfect sense to the people who work there.
So the navigation becomes:
Products | Solutions | Divisions | Industries | Resources | About
But what does the visitor actually want?
They might simply be thinking:
I need a replacement for this piece of equipment.
Or:
I need help with our website.
Or:
I need to integrate this with our existing system.
They shouldn’t have to understand how your business is organised before they can find the answer.
Your website doesn’t need to mirror the structure of your business.
Your company might have five departments.
Your customers don’t necessarily care.
They care about:
The website should make those things easy to find.
UX isn’t just about whether the menu looks good.
It’s everything that happens between someone arriving and getting what they came for.
Look at:
These things might sound like small details.
Collectively, they determine how easy your website is to use.
One of the simplest UX tests costs nothing.
Find someone who isn’t involved in your business.
Give them a task.
Don’t explain how to do it.
Just say:
Find the product/service/information you’d need if you had this problem.
Then watch what they do.
Don’t help them.
Don’t point at the menu.
Don’t say:
It’s under Solutions.
That’s cheating.
Watch where they click.
Watch where they hesitate.
Watch what they ignore.
And, most importantly, listen to the language they use.
If they say:
I wasn’t sure what that meant.
or:
I didn’t know where to look.
or:
I thought that button would take me somewhere else.
you’ve just found something worth fixing.
It’s easy to design a website on a large monitor and assume the mobile version is fine because everything technically fits.
But “it fits” isn’t the same as “it’s easy to use.”
On mobile:
And remember that someone using your website on their phone might be doing it while standing in a factory, sitting in a car park, walking between meetings or trying to solve a problem right now.
Make it easy for them.
The strange thing about good UX is that people don’t normally compliment you for it.
They don’t think:
What an elegantly structured navigation system.
They simply find what they wanted.
They understand what to do.
They complete the form.
They find the product.
They make the enquiry.
That’s the point.
Good UX removes the obstacles between the visitor and what they’re trying to achieve.
Let’s talk about speed.
Because yes, performance matters.
Nobody wants to wait five seconds for a page to load. A slow website is frustrating, particularly on mobile, and it can make an otherwise good website feel unreliable.
But there’s a trap here.
You can have a website that scores brilliantly on a performance test and still be a terrible website.
It can load almost instantly and still leave visitors thinking:
What does this company actually do?
Or:
Can they solve my problem?
Or:
Where am I supposed to go now?
Or simply:
Why would I choose these people?
Speed can’t answer those questions.
Imagine two websites.
Loads in under a second.
Perfect technical performance.
Beautiful Lighthouse score.
But:
Loads quickly enough.
Its technical performance could still be improved.
But:
Which website would you rather buy from?
That’s the point.
Performance matters.
But performance isn’t the same thing as effectiveness.
That doesn’t mean we should ignore performance.
Quite the opposite.
A slow website can undermine everything else you’ve done.
You’ve written great content.
You’ve designed a clear page.
You’ve created a compelling CTA.
You’ve built trust.
Then someone clicks the page and spends four seconds staring at a loading screen.
You’ve introduced friction at exactly the wrong moment.
Performance affects the experience people have of your website.
So, if you want to improve website speed, look at things such as:
But don’t optimise these things in isolation.
This is where I’d make the distinction really clear.
A performance score is useful.
It can identify technical problems.
It can give you something measurable to work on.
But the score isn’t the customer.
A website can gain points on a performance report without becoming meaningfully better for the person using it.
And the reverse can sometimes be true too.
You might spend hours chasing the last few points of a technical score while ignoring a confusing navigation menu that is costing you enquiries.
Fix the things that actually get in the visitor’s way.
This is why a proper website assessment shouldn’t just ask:
How fast is it?
It should also ask:
How well is it working?
Does the website attract the right people?
Can they understand what you do?
Does it build confidence?
Can they find what they need?
Does it give them an obvious next step?
And, yes…
Does it load quickly enough to make all of that possible?
That’s a much more useful way to think about website performance.
That’s why we look at more than speed when we assess a website.
A useful website health check should look at the technical side, but also the things that affect how people actually experience and use the site.
Because there’s not much point having a technically perfect website if the people using it can’t work out what to do.
A website isn’t performing well simply because it loads quickly.
It’s performing well when it helps the right people find what they need, understand what you’re offering and take the next step.
For a long time, that’s essentially what websites were.
You had a homepage.
An About page.
A few pages explaining your products or services.
Maybe a News section.
And a Contact page.
The website was there to tell people who you were and what you did.
And then they emailed you.
There’s nothing inherently wrong with that.
But the web has moved on.
Your website doesn’t have to be a digital brochure sitting on the internet waiting for someone to read it.
It can actually do things.
Think about what happens when someone arrives with a question.
Instead of simply giving them another paragraph of text, your website could:
Answer questions before they need to contact you.
Recommend relevant services based on what they’re looking for.
Demonstrate your expertise through useful content.
Let people try something rather than simply telling them about it.
Calculate potential savings or costs.
Assess their requirements and point them towards an appropriate solution.
Show relevant case studies based on their situation.
Capture enquiries with the right information attached.
Feed information into your sales process, so the conversation starts with some context.
That’s a very different proposition from:
Here’s our website. Here’s our phone number. Give us a call.
This is where things get interesting.
Imagine you’re looking for a new piece of equipment.
You could visit a supplier’s website and read:
We manufacture high-performance equipment for a wide range of industrial applications.
Fine.
Or the website could ask:
What are you trying to achieve?
You select your application.
You enter a few details.
The website shows you the relevant products.
Perhaps it calculates something.
Perhaps it explains the options.
Perhaps it shows you examples of similar installations.
And when you’re ready, it gives you a sensible next step.
The website hasn’t just told you something.
It has helped you make a decision.
That’s a completely different experience.
This doesn’t mean every website needs to become some enormous interactive platform.
Sometimes the right answer is simply a really well-structured website with clear information and good navigation.
But sometimes there’s an opportunity to do much more.
A calculator might help someone understand whether a solution is financially worthwhile.
A configurator might help them work out which product they need.
An assessment tool might identify a problem they hadn’t realised they had.
A comparison might help them choose between different options.
An interactive questionnaire might help you understand their requirements before they ever speak to you.
And a well-designed enquiry process can turn that information into a much more useful sales conversation.
There’s a temptation to add technology to a website simply because you can.
AI.
Chatbots.
Calculators.
Interactive tools.
Personalisation.
Automations.
But technology isn’t the point.
The question should always be: does this make the visitor’s journey better?
If an interactive tool helps someone answer a question they would otherwise have to email you about, that’s useful.
If an assessment helps someone understand a problem, that’s useful.
If a calculator helps them make a business case internally, that’s useful.
If a chatbot simply gets in the way of finding your phone number…
Maybe don’t build the chatbot.
For some businesses however, that can mean moving beyond a traditional website towards a custom digital platform.
The really interesting websites aren’t necessarily the ones with the most features.
They’re the ones where the features serve a purpose.
They help someone:
Understand.
Explore.
Compare.
Calculate.
Decide.
Act.
And that’s a very different way of thinking about what a website is.
A website can have good content.
It can look great.
It can load quickly.
It can have impressive case studies.
It can even have a really good contact form.
And still fail to generate enquiries.
Why?
Because all of those things need to work together.
A visitor rarely arrives at your website thinking:
Right. I’m going to look through every page you’ve created and then decide whether you’re worth contacting.
They’re usually trying to answer a question.
Solve a problem.
Compare options.
Find something.
Or work out whether you’re the right company to talk to.
Your job is to help them move from where they are now to what they need to do next.
A visitor might arrive through Google.
They land on a useful article.
The article answers their initial question.
It points them towards something relevant.
They see evidence that you know what you’re talking about.
They explore a service.
They interact with a tool or assessment.
And then they’re given a sensible next step.
Something like:
Search → Landing page → Useful content → Evidence → Interaction → CTA → Enquiry
That’s a journey.
Now compare that with:
Search → Homepage → Services → Services → Services → Contact
Technically, the visitor can still get where you want them to go.
But you’re making them do all the work.
This doesn’t mean every page needs to be trying to sell something.
In fact, that’s usually a mistake.
But each page should have an idea of where the visitor goes next.
That’s the difference between having a collection of pages and having a website that actually works as a journey.
When you’re looking at an important page, ask:
The answer gives you some context about what they’re likely to be interested in.
If you understand that, you can make the content much more relevant.
This is where your CTA comes in.
And that CTA shouldn’t necessarily be:
It should be the thing that makes the most sense at that point in the journey.
Sometimes that’s:
And sometimes the right answer really is:
The important thing is that the next step should feel natural, not forced.
This is an important distinction.
When people talk about conversion, they often mean:
What’s our CTA?
But the CTA is only one part of the process.
A visitor isn’t going to click “Contact us” simply because you’ve made the button pink.
They’ll do it when they’ve reached the point where they feel:
The website’s job is to help them get there.
The ten problems we’ve looked at aren’t really ten completely separate problems.
They’re connected:
Not in a creepy AI-overlord kind of way. 😂
Just in the sense that the website should anticipate what someone is likely to need next.
Don’t make the visitor start their journey again on every page.
Your website doesn’t need to be perfect.
It doesn’t need every new feature.
And you don’t necessarily need a completely new website.
But you should understand what’s working, what’s getting in the way and which improvements are actually worth making.
Because a website can look great, load quickly and still fail to do its job.
It needs to help the right people understand what you do, trust that you can help them and know what to do next.
Sometimes that means fixing a few things.
Sometimes it means improving the content or conversion journey.
And sometimes, yes, it means redesigning or rebuilding a website.
The important thing is understanding what your website actually needs before you start spending money on it.
Your website doesn’t have to do everything.
But it should do the things that matter.
Attract the right people. Help them understand what you do. Give them reasons to trust you. Answer their questions. Make it easy to take the next step.
That’s what a website that works actually looks like.
Found this useful? Add a link to it from your own website.
Choose the wording that fits your article, then copy the link.
Whether you need a high-performance WordPress website or a custom Laravel application, we build systems designed to scale.