UI/UX design judged on what it produces, not how it looks

UX audits, user research, user interface design and design systems. We start with the journey that earns you money and work backwards from where people are leaving it.

◆ UX audits ◆ User research ◆ Prototyping ◆ Design systems ◆ Accessibility
Why design decides revenue

Most sites are not ugly. The user experience is just hard work

Nobody abandons a form because the colours are wrong. They abandon it because it asks for a phone number before explaining what happens next, or because the error message appears after they press submit rather than while they type.

Those are design decisions, usually made quickly by whoever was building the page. They rarely get revisited, because nothing looks broken.

Friction is invisible in analytics

A drop-off between two steps tells you people left. It does not tell you the field validation rejected a valid phone number. Only watching someone try it does.

Accessibility and usability are the same work

Low contrast, unlabelled fields and poor focus order fail disabled users first and everyone else second. Fixing them lifts completion for the whole audience.

Pages are getting heavier, not better

The average home page carries 14.3% more elements than a year ago and 10% more accessibility errors. More interface is not more design.

The evidence

What the research actually says

95.9%of the top million home pages fail WCAG 2 checks, averaging 56.1 errors eachWebAIM Million, 2026
70.2%average documented cart abandonment across fifty studiesBaymard Institute
35%potential conversion lift available to a large store from checkout design aloneBaymard Institute
5 userssurface roughly 85% of a site's usability problemsNielsen & Landauer
What we find in audits

The same four problems, almost every time

  • Forms that ask too much, too early

    The average checkout shows 11.3 fields across 5.1 steps. Eighteen per cent of shoppers abandon because the site insists they create an account first, and seventeen per cent because the process is simply too long.

  • Text nobody can read

    Low-contrast text appears on 83.9% of home pages. It is the single most common accessibility failure, it affects every user in bright daylight, and it is a one-line fix at design stage.

  • Inputs with no labels

    Fifty-one per cent of home pages have form fields without labels. Screen readers cannot announce them, autofill cannot populate them, and sighted users lose the label the moment they start typing.

  • No system, so nothing matches

    Buttons in four sizes, three shades of the same grey, two spacing scales. Each page was reasonable on its own; together they read as careless.

How we audit

We test the journeys that carry money first, on real devices, with real content, not a walkthrough of the home page.

Every finding is written with where it happens, what it costs and what to change. You keep the document whether or not we do the work.

Selected screens

Interfaces we have designed

Product pages, booking flows, configurators and design systems. Representative interface work across e-commerce, healthcare, hospitality and B2B.

Product configurator
Product configurator
Pricing and plan selection
Pricing and plan selection
Multi-location clinic template
Multi-location clinic template
Menu and ordering flow
Menu and ordering flow
Appointment booking flow
Appointment booking flow
Design system components
Design system components
B2B product and quote page
B2B product and quote page

More work in the portfolio.

Our process

Decide on a prototype,
not in production

Stage 01

Audit and research

Session recordings, task testing and an accessibility pass. Written findings with each problem tied to a number.

Stage 02

Structure

Information architecture and user flows agreed before anything is drawn. This is where most of the value is decided.

Stage 03

Prototype and test

Clickable flows put in front of real users. Problems found here cost an hour, not a sprint.

Stage 04

Design system and handover

Components, tokens, states and edge cases documented, so what gets built matches what was designed.

Why ScintillaWeb

We build what we design

The same team writes the front-end code. A design that cannot be built cleanly never leaves the file, and nothing is lost in a handover between two companies.

Start a project ↗
Design against a number +

Agreed before we start, form completions, checkout rate, enquiries. Taste is not a success criterion.

Real content, never lorem ipsum +

Placeholder text hides every layout problem your real copy will cause. We design with the words that will ship.

Accessibility from the first file +

Contrast, labels and focus order are design decisions. Retrofitting them after build costs several times more.

Tested on the devices people own +

Mid-range Android handsets on ordinary connections, not a retina laptop on office wifi.

A system, not a set of screens +

Components and rules your team can extend. Screens run out the moment someone needs a page you did not draw.

You own the files +

Source files, components and documentation handed over. No agency-locked libraries.

What we do

UI design and UX work we take on

From a one-week UX audit of a leaking checkout to a full user interface design system for a product team.

UX audit

A written review of the journeys that matter, enquiry, booking, checkout, with each problem tied to where people leave and roughly what it costs.

Why it matters

You get the findings whether or not you hire us for the fix. An audit that only makes sense as a sales pitch is not an audit.

Talk it through

User research

Interviews, session recordings and task testing with real users of your product, not a panel recruited to agree with us.

Why it matters

Five participants surface around 85% of usability problems. Research is cheaper than building the wrong thing twice.

Talk it through

Information architecture

Sitemaps, navigation and content structure decided before any page is designed, so people can find what they came for.

Why it matters

Most 'we need a redesign' requests are navigation problems wearing a visual disguise.

Talk it through

Wireframes and prototypes

Clickable flows you can put in front of a user before a line of code exists, so disagreements happen on a prototype rather than in build.

Why it matters

Changing a prototype takes an hour. Changing a built page takes a sprint.

Talk it through

User interface design

The visual layer applied to real content and real copy, never to placeholder text that hides how the page will actually behave.

Why it matters

A design that only works with perfect content is a design that will not survive its first month.

Talk it through

Design systems

Components, tokens and documented rules your team composes pages from, with the states and edge cases specified rather than improvised.

Why it matters

Without a system, the fifth page a developer builds stops matching the first four.

Talk it through

Accessibility

Contrast, labels, focus order and keyboard paths built in from the start, and tested rather than assumed.

Why it matters

95.9% of top home pages fail WCAG checks. It is also the cheapest thing to get right at design stage and the most expensive to retrofit.

Talk it through

Conversion design

Forms shortened, friction removed, and the decision a visitor is making made easier, measured against a number agreed before we start.

Why it matters

The average checkout asks for 11.3 fields across 5.1 steps. Most of them are there because nobody questioned them.

Talk it through
Questions

UI/UX questions, answered

Can you do UI design only, without the build? +

Yes. You receive the files, the design system and a developer handover document. We will also review the build if your team wants a second pair of eyes.

Do we need user research for a small site? +

Usually a light version. Five participants surface most problems, and a short round of task testing costs far less than redesigning on a hunch.

What does a UX audit cost? +

A focused audit of one journey typically runs as a two to four week sprint, quoted after a short scoping call. You keep the findings regardless of what happens next.

Do you work in Figma? +

Yes, and we hand over the file with components, tokens and documented states rather than a flattened set of screens.

How is UX design different from a redesign? +

A redesign changes how the site looks. UX design changes what it does. Often the answer after an audit is to fix three flows rather than rebuild everything.

Can you improve accessibility on an existing site? +

Yes. We audit against WCAG 2.2 AA, prioritise by impact, and fix the common failures first, contrast, labels, focus order and keyboard paths.

Will you redesign our brand too? +

We can. See brand identity and design. Interface design and brand identity are separate pieces of work, and we will say which one your problem actually needs.

How do you measure whether it worked? +

Against the number agreed at the start, reported after launch. If it did not move, we say so and look at why.

Know something is leaking but not where?

Thirty minutes on the journey that matters most. You leave with two or three things to fix, whether or not you hire us.

Book a free call ↗
Free 30-min call
No pitch deck
Book now