Web design that converts, not just impresses

What actually makes a website convert?

Conversion comes from clarity, not decoration. A visitor arriving cold needs to work out three things fast: what you do, whether you do it for someone like them, and what happens next. If any of those three take effort to find, the visit ends. Most sites that underperform are not ugly. They are vague.

The second driver is trust. People buy from businesses that look like they will still exist next year and will answer the phone. Trust is built with specifics: named people, real photography, plain pricing signals, clear service descriptions, and proof that is genuinely yours. Vague superlatives do the opposite, because everyone claims them.

The third driver is friction. Every extra form field, every ambiguous button, every step that demands a decision before the visitor is ready costs you enquiries. Good design removes steps rather than beautifying them.

• One clear message per page, visible without scrolling
• One primary action, repeated at sensible points down the page
• Trust signals near the decision, not buried on an about page
• Forms that ask only for what you need to have the first conversation
• Pages that load fast enough that nobody notices them loading

How visual hierarchy does the persuading

Hierarchy is the order in which the eye takes things in, and it is the strongest tool a designer has. Size, weight, colour contrast, spacing and position all tell the reader what matters. When everything is emphasised, nothing is, and the visitor has to read the whole page to find the one line that would have sold them.

The practical test is the squint test. Blur the page until you cannot read the words. What still stands out should be the headline, the primary button and the one image that carries the message. If a decorative panel or a stock photo dominates instead, the hierarchy is working against the goal.

Spacing is the part people underestimate. Generous space around an element is what makes it read as important. Cramming more content above the fold usually reduces how much of it gets read, because nothing has room to be noticed.

From wireframe to design system: how the process runs

We start with structure before style. A wireframe settles what each page must say and in what order, using grey boxes and real headline drafts. Arguing about content order in a wireframe takes minutes. Arguing about it in a finished visual design takes days, because everything is tied to a look.

Once structure is agreed, we design a small number of key pages in full: usually the home page, a service page and a contact or conversion page. These set the visual direction, the type scale, the colour usage and the component vocabulary. You review a real thing rather than a mood board.

From those pages we extract a system. Buttons, cards, headings, forms, navigation and spacing rules become defined components with rules for how they behave on every screen size. After that, new pages are assembled rather than invented, which is what keeps a site consistent two years after launch.

• Wireframes to settle content order and page purpose
• Two or three full designs to set the visual direction
• Interactive prototypes for anything with a flow, such as booking or checkout
• A component library so every future page starts from agreed parts

Mobile-first is not a layout choice, it is the default reality

For most of the sites we work on, the majority of visits arrive on a phone. That makes the small screen the real design, and the desktop version the variation. Designing desktop first and shrinking it produces the familiar result: a cramped phone page with a giant hero image, a buried call to action and a menu that hides everything.

Mobile-first forces useful discipline. There is only room for one message, so you have to choose it. Navigation has to be short, so you have to decide what people actually need. Long forms become obviously painful, so they get shorter. The decisions that improve the phone experience usually improve the desktop one too.

It also changes what you can afford. Heavy images, multiple font weights and animation libraries cost more on a mid-range phone over mobile data than they do on a designer laptop over office broadband. We test on real devices and throttled connections, because that is the condition most visitors are in.

Accessibility is a requirement, not an upgrade

Accessible design means the site works for people using screen readers, keyboard navigation, magnification or high contrast modes, and for anyone with a temporary limitation such as bright sunlight or a broken arm. It is the right thing to do, and in many markets it is also a legal expectation for organisations of a certain size.

The practical work is not exotic. Sufficient colour contrast on text and buttons. Real heading structure rather than large bold paragraphs. Labels on form fields. Focus states that are visible when tabbing. Alt text that describes the image rather than repeating the file name. Buttons that are buttons in the code, not styled divs.

The side effect is that accessible pages tend to be better pages. Clear headings, readable contrast, descriptive links and sensible structure help every visitor, and they also give search engines and AI crawlers a cleaner document to read.

• Text contrast checked against WCAG levels, including on coloured buttons
• Every interactive element reachable and usable by keyboard
• Headings in real order, so a screen reader can skim the page
• Images described, decorative images marked as decorative

Why design decisions and search decisions are the same decisions

Where the content sits, how the headings are ordered, how much real text a page carries and how fast it renders are design choices and search choices at the same time. When a designer decides to replace a paragraph with an icon strip, that page just lost the text a search engine would have used to understand it.

The same applies to AI answer engines. Best available evidence suggests several of the major AI crawlers fetch pages but do not run JavaScript, so content that only appears after a script runs may simply not exist to them. That makes it a layout and build decision as much as a technical one. Core content belongs in the page, not in a tab that loads on click.

This is why we do not hand a design to a separate team and hope. The person deciding the page structure should already know which questions the page needs to answer and in what order. Retrofitting search structure onto a finished design is how sites end up with a beautiful home page that ranks for nothing.

How to judge a design objectively

Personal taste is the least useful review criterion, and it is the one most review meetings run on. Replace it with questions that have answers. Can a stranger say what this business does within five seconds of landing here. Is the next step obvious without scrolling. Does the page load quickly on a phone. Is the text readable without zooming.

Then check it against the job. Every page should have one purpose. If you cannot say what a page is for in a single sentence, the page is the problem, not the design. Pages that try to do three jobs usually do none of them.

Finally, judge it after launch with evidence rather than opinion. Scroll depth, click behaviour on the primary action, form starts against form completions, and the enquiries you actually receive. A design that reviewers loved and visitors ignore is a failed design, and the numbers will say so within weeks.

• Five-second test: can a stranger describe what you do
• One purpose per page, stated in one sentence
• Speed measured on a mid-range phone, not a desktop
• Post-launch behaviour reviewed against the goal, not against taste