# Website Improvement Vancouver, Vancouver Website Design

> Replacing a functioning website is an expensive way to solve a handful of problems.

Canonical URL: https://vancouverwebsitedesign.com/services/website-improvement/

---

Service 07 Steady improvement, without a rebuild.
Replacing a functioning website is an expensive way to solve a handful of problems. We agree what to fix first, work in short cycles, and check afterwards whether each change did anything. If a cycle stops being worth the money, we stop.
Talk to us about this See work like this
How long
Cycles of 4 to 8 weeks
Who runs it
Reviewed by Dave Curtin, delivered by a small team
Fit When this is the right piece of work.
Cycles of 4 to 8 weeks
A first round of fixes, then carry on if it's earning its keep
Reviewed by Dave Curtin, delivered by a small team
This usually fits when
The site is fundamentally sound and replacing it would be wasteful.
There is a backlog, prioritised by opinion rather than evidence.
You want experienced review without committing to a redesign.
Probably not the right fit if
A site that needs replacing rather than improving.
No access to analytics, and nobody internally responsible for the site.
Decisions made together
01 What is worth fixing now and what can wait
02 What to test before committing to it fully
03 How to tell whether each change worked
What you get What the engagement includes.
01 A review of the site and its analytics
02 An ordered list of what to fix
03 A first round of changes, fixed in scope
04 Usability and content fixes
05 Speed and accessibility fixes
06 A review every quarter
Work like this We have done this before. Here it is.
All projects
Website Design Nevilles at the Cross
Brand + Website Limitless Health
Website Design Clonakilty Food Co.
Common questions The things people ask before they call.
Why improve rather than rebuild? Replacing a working site is an expensive way to fix a small number of problems. Where the foundation is sound, steady improvement achieves more for less. Where it is not, I will say so.
How does it work month to month? We agree priorities, work in short cycles, and review afterwards whether each change made a measurable difference. You can stop at the end of any cycle.
What kind of things get fixed? Whatever the evidence points to. Commonly: navigation people cannot follow, pages that do not answer the question that brought someone there, slow loading, and forms with high abandonment.
Do we need analytics set up first? It helps considerably. If nothing useful is running, setting up measurement properly becomes the first cycle of work.
Not sure this is the right service?
Describe the situation and I will tell you whether this is the right piece of work, whether something smaller would do, or whether it is too early.
Start a project See everything we do