Services/Website Design & Development
Traffic you already earn, converting at a rate you don't.
Most sites do not have a traffic problem first. They have a destination problem. People arrive, fail to find the one thing they came for, and leave without anyone recording that it happened.
Which is why we look at what the site does with its existing visitors before recommending you buy more.
Why Redesigns Disappoint
A new site that nobody asked for solves nothing
Redesigns usually begin with an aesthetic complaint and end with a site that looks current and performs the same. The brief was appearance, so appearance is what changed. Nobody established what the old site was failing to do, which means nobody can tell whether the new one is better.
The failures that actually cost money are unglamorous. A phone number only on the contact page. A form asking for nine fields when three would do. Prices absent, so the visitor leaves to find someone who publishes them. A load time that quietly removes a portion of your mobile visitors before they see anything at all.
Worse, redesigns routinely destroy rankings. URLs change without redirects, content thins out in the name of cleanliness, and traffic that took years to build disappears in a weekend. We treat a rebuild as a migration problem as much as a design one, because that is what it is.
What The Work Is
Conversion, foundations, and not losing what you have
Conversion before decoration
We start by establishing where interest is currently being lost, then design around fixing that. Aesthetics matter and they are not the brief; the brief is that more of the people already arriving get in touch.
- Review of the existing journey: where people land, where they stop, what they never reach
- Contact paths that are visible on every page rather than filed under Contact
- Forms cut to the fields you genuinely need to reply
- The information that decides the sale, published rather than gated behind a call
- Design that is credible for the price point you sell at
Technical foundations
Google indexes the mobile version of your site by default, and page speed is both a ranking input and the reason a share of your visitors never see the page at all. This is measurable, unglamorous work with a direct commercial effect.
- Core Web Vitals and real-world load performance, not just lab scores
- Mobile-first build, because that is what gets indexed
- Clean semantic structure and schema, so machines are told rather than left to infer
- Accessibility to WCAG 2.1 AA, which is both right and increasingly a legal expectation
- Analytics and conversion tracking configured before launch, not after
Migrations that keep your rankings
If you already rank, the single largest risk in a rebuild is losing it. Handled properly a migration is uneventful. Handled carelessly it undoes years of compounding in a weekend, and recovery is slower than the original climb.
- Full URL inventory and redirect mapping before anything moves
- Content parity checks, so pages that earn traffic are not quietly thinned
- Staged launch with crawl and index monitoring
- Post-launch monitoring against a pre-launch baseline
- A rollback path, because the plan has to survive being wrong
Related
SEO
The traffic your site needs to be worth optimising.
Analytics & Measurement
Knowing where interest is actually being lost.
Website conversion review is part of the Diagnostic Audit, so this is usually assessed before anything is rebuilt.
FAQ
Common questions
Usually the latter, and we will say so. A rebuild is warranted when the platform is genuinely holding you back, when the structure cannot support the content you need, or when performance cannot be salvaged. Otherwise a focused set of conversion and technical fixes to the existing site costs less and moves the number sooner.
It can, and it frequently does when migration is treated as an afterthought. The risks are changed URLs without redirects, thinned content, and structural changes that break internal linking. We plan the migration before the design work starts and monitor against a pre-launch baseline, so if something moves we know within days rather than at the next quarterly review.
Whatever is right for how you will actually maintain it. We work with modern frameworks where performance and custom functionality matter, and with established CMS platforms where your team needs to publish without a developer. The wrong answer is a stack nobody at your business can update.
The build is rarely what takes the time. Copy, photography and internal decisions are. A focused site moves quickly when that material is ready and stretches for months when it is not. We would rather agree what is being decided by whom at the start than discover it halfway through.
Find out what your site is losing
Before you rebuild anything, it is worth knowing which pages already earn traffic and where that interest is being dropped.