G29DESIGN home
G29DESIGN home
G29DESIGN home
G29DESIGN home

UX vs Visual Design: What Matters More

UX vs Visual Design: What Matters More

When a website feels dated and enquiries are disappointing, it is tempting to choose between a new look and a better user experience. Start by following the task your customer came to complete. The right priority depends on what prevents that person from understanding, trusting or using the website.

Visual design gives information its emphasis and character. User experience covers the wider journey: what someone expects, what they can find, how the website behaves and whether they can complete their task. They overlap. Readable typography and a recognisable button are visual decisions that also affect usability.

What are you asking the website to do?

Give the review a specific starting point. “Improve the website” is too broad to guide a design decision. “Help a business owner understand whether this service suits them and send a useful enquiry” gives you something to examine.

A visitor comparing suppliers may need project evidence, scope and investment guidance. Someone returning after a conversation may be ready for contact details. An existing client may only need support. Giving all three people the same prominent booking prompt can make the website less useful.

This is where your marketing journey matters. A helpful explanation can earn attention; a relevant example can support consideration; a clear scope and next step can support a buying decision. The page should answer the visitor’s current question.

Look at the same page through both lenses

Consider an illustrative service page. It has an attractive opening image, a long description, several project thumbnails and an enquiry form. The following are review questions, not a case study or a claim about conversion improvements.

The service description

The user-experience question is whether the visitor can work out what is included, who the service is for and what happens next. The visual-design question is whether headings, spacing and type make those answers easy to notice and read. Enlarging a vague headline gives the vague message more prominence; useful copy still needs a clear hierarchy.

The project evidence

The visitor needs to understand what was delivered and why it is relevant. A tiny screenshot without context may contribute little to that decision. Give the work enough space to inspect, explain the particular problem it addresses and distinguish visible design work from measured business results. A polished image does not establish increased enquiries.

The enquiry form

Labels, field order, validation, keyboard use and confirmation all affect the task. Contrast, text size, spacing and focus indicators affect whether people can perceive and operate it. A prominent submit button cannot compensate for an error that gives no useful explanation. Equally, a working form still needs to look like a clear and credible next step.

Run a practical review before commissioning a redesign

  1. Choose one real journey. Write down the audience, where they arrive from, the question they need answered and the action they may reasonably be ready to take. Use an actual landing page rather than assuming everyone starts at the homepage.
  2. Follow it on a phone. Read the offer, inspect the evidence and find the next step. Note clipped text, obscured controls, unreadable images and information that only appears on hover. Record the device and page so the finding can be reproduced.
  3. Try the keyboard. Use Tab and Shift+Tab to move between links and controls. Check whether you can see the current focus, understand the control and reach or leave an open menu. W3C explains the purpose of a visible focus indicator. This is one check, not a complete accessibility assessment.
  4. Ask someone to explain the offer back to you. Give them a relevant task and observe where they hesitate. Ask what they believe is included, what evidence helped and what information is missing. Avoid leading questions that ask them to confirm that the design is good.
  5. Write the problem and its acceptance check. Replace “make this premium” with a concrete observation such as “the project image is too small to read on a phone”. State what the revised page must let someone see or do, then check that behaviour after the change.

For an accessible starting point, W3C’s Easy Checks covers subjects including headings, contrast, keyboard focus and form labels. Its scope is deliberately limited. A page can pass these initial checks and still have accessibility barriers.

Decide what deserves attention first

Address an obstructed task before adding decoration around it. Examples include text people cannot read, a menu they cannot operate, an unclear offer or a failed form. Then examine whether the presentation communicates the quality and character of the business: appropriate typography, authentic imagery, useful project detail and a consistent visual language.

The answer may be a focused correction rather than a complete rebuild. A larger redesign is easier to justify when structure, content, presentation and the underlying editing system all need coordinated work. Review when a website redesign is worth doing before treating a new platform as the solution to every problem.

Judge the result by more than appearance

Before release, check that the intended task works on the actual website. For an enquiry journey, separate a button click, a submitted form, receipt in the destination system and a qualified business conversation. Those are different outcomes.

After release, compare equivalent pages, audiences and periods where the data allows. Record changes in traffic sources, offers and campaigns that could affect the result. A small before-and-after sample cannot tell you that a colour or layout caused an increase in leads. Sometimes the first useful outcome is simply that a previously blocked action now works; record that accurately.

Our guide to how websites generate leads follows the wider path from audience intent through to a received and qualified enquiry.

What should a website proposal explain?

A useful proposal should connect the design work to the problem being solved. Ask which pages and journeys will change, what content and evidence are needed, who is responsible for each part, how you will review the work and what will be tested before release. It should also explain editing, ownership, ongoing costs and support.

Both user experience and visual design deserve deliberate work. Prioritise the obstacles affecting the customer’s task, then make the whole experience clear, distinctive and appropriate to your business. If you would like to discuss a particular page or journey, send G29DESIGN the website and what you want it to help people do.

Article revised 7 November 2026.

Supercharge Your Success with G29Design.

G29DESIGN home
G29DESIGN partners with businesses to design, build, and optimise high-performance digital platforms that drive real growth.

Contacts

Latest News

G29DESIGN © 2026 All Rights Reserved.