A redesign should solve a diagnosed business or customer problem. This review framework separates focused improvements from structural work and a full rebuild.
A redesign needs a diagnosis
A website can look dated and still work well. It can also look polished while making it difficult for customers to understand the offer, trust the business, or take the next step. Appearance alone is therefore a weak reason to rebuild it.
The useful question is whether the current website still supports the business and the decisions its customers need to make. A sound review looks beyond taste and separates an isolated page problem from a failure in the site's structure, technology, or operating model.
The size of the redesign should match the size of the problem. Rebuilding everything is not automatically more strategic than fixing the right few things.
Review the website in four layers
Appixi's review framework examines the customer experience, observable behavior, technical health, and the team's ability to operate the site. Looking at all four prevents a visual preference from becoming the entire brief.
Message and customer path
Open the website as if you know nothing about the company. Within a few seconds, can you identify what the business does, who it helps, and where to go next? Repeat the exercise on a phone and try to complete the most important action.
Points of friction often include:
- The main offer is hidden behind broad or internal language.
- Important services require several clicks to discover.
- Proof appears after the point where a visitor must decide whether to trust the business.
- Calls to action change from page to page without a clear reason.
- Contact forms ask for more information than the first conversation needs.
If these problems are confined to a few pages, focused content and layout work may be enough. If they are built into the navigation and page hierarchy, the problem is structural.
Behavior and conversion evidence
Internal frustration matters, but it should be connected to observable behavior. Review search queries, landing pages, navigation paths, form starts and completions, sales questions, customer-service conversations, and the pages people visit before making contact.
Google Analytics events can record interactions such as link clicks, form actions, searches, and other business-specific steps. The goal is not to collect every possible event. It is to measure the few actions that reveal whether customers can move from interest to a useful next step.
Technical performance
Test representative page types rather than relying on one homepage score. A service page, article, product page, and contact flow can fail in different ways. Google's Core Web Vitals provide field-oriented measures for loading performance, interaction responsiveness, and visual stability. They should be reviewed alongside image delivery, third-party scripts, form behavior, mobile navigation, and real-device testing.
A slow image or one unstable template can often be repaired. A platform that produces the same performance problems across every template may justify deeper technical work.
Accessibility and maintainability
Accessibility belongs in the diagnosis, not at the end of production. The Web Content Accessibility Guidelines 2.2 provide testable criteria for making web content more perceivable, operable, understandable, and robust.
The operating experience matters too. Ask the people who update the site how long routine changes take, which pages are easy to break, where content must be entered more than once, and whether integrations can be maintained without workarounds. A site that looks acceptable but resists every update may have reached the limits of its foundation.
Improve or rebuild?
No single row decides the project. The pattern across the rows does. One or two problems in the middle column usually support focused improvement. Repeated problems in the right column point toward a redesign or rebuild.
| Signal | Focused improvement is usually enough | A redesign or rebuild is more likely |
|---|---|---|
| Offer and audience | The offer is stable, but a few pages explain it poorly. | The business, audience, or service mix has changed substantially. |
| Navigation and structure | Visitors struggle with one pathway or section. | Several audiences compete inside the same pages and navigation. |
| Content | Useful content exists but needs editing, proof, or a clearer order. | Core pages are missing, duplicated, or organized around internal terminology. |
| Platform and CMS | Editors can publish safely after targeted template improvements. | Routine updates require workarounds or repeatedly break layouts. |
| Performance and accessibility | Problems are isolated to specific assets, components, or templates. | The same barriers recur across the design system or technical stack. |
| Integrations and measurement | A form, event, or connection can be repaired independently. | The site cannot reliably support the CRM, analytics, commerce, or workflow it now needs. |
| Brand expression | The identity is sound but inconsistently applied online. | The business has outgrown both its positioning and the digital system expressing it. |
An illustrative composite
This example is a composite created to explain the decision, not an Appixi client case study.
Imagine a regional home-services company that began with one primary service and later added plumbing, electrical work, and maintenance plans. Its website still places every service on one long page. The navigation says only "Services," the contact form does not ask which service is needed, editors duplicate the same content in several places, and analytics records page views without the form steps that matter to the business.
Changing the colors or rewriting the homepage would leave the central problems intact. The offer, page structure, form routing, publishing model, and measurement plan all need to change together, so a redesign has a defined job. If the structure and CMS were sound and only the form caused confusion, a focused form and landing-page improvement would be more proportionate.
This is the distinction a useful diagnosis should make: not whether a website feels old, but whether its problems share one underlying cause.
Define the outcome before the layout
Before discussing visual concepts, write down the decisions the next version must make easier. A useful list is usually short:
- Explain the offer and intended audience more clearly.
- Help the right customer find the right service.
- Place credible evidence before the next important decision.
- Make contact or conversion easier on every device.
- Give the business a maintainable publishing and measurement system.
Each outcome should connect to an observable check. For example, the team might verify that a customer can identify the right service from the main navigation, that important forms record a start and completion, or that editors can publish a standard page without duplicating content.
Choose the right scope
When the foundation is sound, website maintenance and focused improvements may solve the problem with less disruption. When customer journeys, content structure, and the technical system need to change together, review the scope of a website redesign. A broader change involving design, development, content, accessibility, analytics, and integrations belongs within Website Design and Development.
If the site collects activity but cannot answer useful business questions, the measurement plan may need its own marketing analytics review. The right starting point is the smallest scope that can solve the diagnosed problem completely.
Standards and measurement references
- Google Analytics events explain how website and app interactions can be collected for reporting.
- Core Web Vitals define Google's current measures for loading performance, responsiveness, and visual stability.
- WCAG 2.2 is the W3C Recommendation containing testable web-accessibility guidance.
The practical decision
Do not redesign because a certain number of years have passed. Redesign when the website no longer reflects the business, repeatedly obstructs customers, or cannot support the work expected of it. A clear diagnosis protects the project from becoming a visual exercise and gives every design decision a business reason.
If the evidence is mixed, start a conversation with Appixi and define the problem before defining the project.
