Key Factors to Consider in a Website Redesign

The factors to consider in a website redesign span strategy, design, technology, content, and budget, and they are all interdependent.

Businesses that get the best outcomes from a redesign are those that systematically evaluate every factor before briefing an agency, not those who rush to aesthetics first.

Skipping any category creates gaps that are far more expensive to fix after launch than during planning.

This checklist covers all six factor categories, the questions each requires you to answer, and the order in which they should be addressed.

Key Takeaways

• Strategic factors must come first: Business goals, audience needs, and competitive context must be understood before any design or technical decisions are made.
• Technical factors determine what's possible: Platform choice, integrations, and performance targets constrain scope before aesthetics are even considered.
• UX factors determine what performs: Information architecture, conversion flows, and mobile experience drive post-launch results more than visual design.
• Budget and timeline are real constraints: Scope must match what is achievable in the available time and budget, over-scoping is a common and expensive mistake.
• Content is consistently underweighted: Copy, messaging, and content migration are high-effort workstreams that must be factored into scope from the very start.

Webflow Development Services

Webflow Experts On-Demand

Whether you're starting fresh or need a full revamp—we create fast, modern Webflow sites built for growth.

Let's talk

Strategic Factors

Planning around strategic priorities is the foundational work that makes every subsequent design and technical decision coherent. Without it, a redesign is an aesthetic exercise, not a business investment.

Business Goals and Current Site Performance

Every redesign must begin with two specific questions: What must the new site achieve? And where is the current site measurably failing?

• Define success in measurable terms: "More leads" is not a goal, "increase monthly qualified form submissions from 15 to 40" is a goal.
• Audit current performance before the brief: Baseline conversion rate, organic traffic, and bounce rate data define the gap the redesign must close.
• Connect every scope item to a business goal: Features that don't serve a defined goal are scope additions that dilute budget and timeline.
• Document what the current site does well: Preserving what works is as important as improving what doesn't, not every page needs to change.

Target Audience and Their Needs

Audience needs drive every information architecture, content, and conversion design decision. Designing without audience clarity produces a site that looks good but doesn't work.

• Define primary and secondary audiences specifically: "B2B procurement managers at mid-market manufacturing companies" is more useful than "business buyers."
• Document what each audience needs to find and do: The specific tasks your audience must complete on the site define its information architecture.
• Gather data from actual users, not assumptions: Analytics, customer interviews, and support ticket patterns all reveal real audience behavior.
• Identify audience device and context patterns: A field service audience on mobile during work hours needs a very different design than a boardroom decision-maker on desktop.

Competitive Landscape

Competitive context shapes where you have permission to differentiate and where industry norms create baseline expectations.

• Audit the top five direct competitors' websites: Identify their strengths, weaknesses, and the gaps your redesign can exploit.
• Identify design and UX patterns that are industry norms: Departing from norms creates friction, only do it intentionally and with a specific reason.
• Find the white space in content and positioning: What do competitors not cover well? That gap is your differentiation opportunity.
• Document feature parity requirements: Some competitor features are baseline expectations in your category, not including them creates a perceived disadvantage.

Goal and Measurement Factors

Setting and measuring redesign goals must happen before design begins, not after launch when everyone wants to claim credit for improvements.

Defining Success Before Design Starts

Without agreed, measurable success criteria, a redesign has no objective basis for evaluation. Every design decision must be traceable to a goal.

• Get stakeholder alignment on goals before the brief: Disagreements about goals that emerge after launch are costly to the agency relationship.
• Separate primary goals from secondary aspirations: Trying to optimize for too many outcomes simultaneously often produces a site that achieves none.
• Set realistic improvement targets based on benchmarks: Industry conversion rate benchmarks provide context for what's achievable with a well-executed redesign.
• Define the measurement period for evaluating success: Post-launch performance requires a minimum of 90 days to reflect the redesign's impact, not the launch spike.

Baseline Metrics Documentation

Every metric the redesign will be measured against must be recorded before launch. Without a baseline, improvements are impossible to quantify.

• Export 12 months of analytics data before the new site launches: This creates the comparison dataset for every post-launch performance claim.
• Document conversion rates by channel and page: Understanding where your current site converts, and where it doesn't, focuses redesign effort on the highest-impact areas.
• Record current keyword rankings for target terms: Organic ranking changes after a redesign require pre-launch rankings as the benchmark.
• Screenshot current Google Search Console performance reports: These records protect against data loss if the GSC property is changed during the redesign.

Measurement Tool Setup as a Scope Item

If your current analytics are incomplete or misconfigured, correcting them is a redesign deliverable, not an afterthought.

• Verify all conversion events are tracking correctly before launch: GA4 requires explicit conversion event configuration, most sites are missing critical tracking.
• Include analytics QA in the launch checklist: Post-launch analytics verification should happen within the first 24 hours, not weeks later.
• Configure goal tracking in Google Analytics 4 during the redesign: Every primary conversion must be explicitly marked as a conversion event in GA4.
• Set up Google Tag Manager as the tag management layer: GTM makes future tracking changes manageable without touching the site code.

Design and UX Factors

UX and design success elements determine how well the site performs after launch. Design that isn't grounded in user behavior is decoration.

Information Architecture and Navigation

How content is organized is the highest-impact UX decision in any redesign. It shapes every user journey on the site.

• Map content to audience tasks, not organizational structure: Users think in terms of what they need to do, not how your company is structured internally.
• Limit top-level navigation to the most critical paths: More than seven primary navigation items consistently reduces findability and increases cognitive load.
• Test navigation labels with actual users before finalizing: Labels that seem obvious internally often confuse external users with different vocabulary.
• Document the full page hierarchy before wireframing begins: IA decisions made on the fly during design produce inconsistent, hard-to-navigate structures.

Conversion Flow Design

Every primary conversion goal needs a deliberate user journey designed around it. Conversion flows added as afterthoughts consistently underperform.

• Map the full journey from landing page to conversion for each goal: Understanding the full path reveals the friction points where users abandon.
• Reduce form length to the minimum required fields: Every additional field reduces completion rates, include only what is genuinely necessary.
• Place conversion calls to action at multiple points in each journey: Users are ready to convert at different stages, don't force them to reach the bottom to find the CTA.
• Design confirmation and thank-you states as part of the conversion flow: Post-conversion communication sets expectations and reduces anxiety for first-time inquiries.

Mobile and Accessibility Standards

Mobile-first design is a standard requirement. Accessibility at WCAG 2.1 AA is increasingly a legal and ethical baseline in most markets.

• Design in mobile viewport first, then scale up: Mobile-first discipline ensures the core experience works on the smallest screen before expanding.
• Test WCAG AA compliance with both automated and manual tools: Automated tools catch approximately 30 to 40 percent of accessibility issues, manual testing is required for the rest.
• Document minimum touch target sizes in the design system: 44px minimum touch targets are a WCAG requirement and a significant mobile usability factor.
• Validate color contrast ratios for all text and interactive elements: WCAG AA requires a 4.5:1 contrast ratio for normal text, verify every color combination.

Technical Factors

Technical requirements to document before scoping prevents the budget overruns and timeline slips that most commonly originate from requirements discovered too late.

Platform and CMS Selection

The platform choice determines what is possible for content management, site speed, integration, and scalability. It must be evaluated against requirements, not defaults.

• Match the CMS to the content team's actual capabilities: A platform that the content team cannot use confidently will result in a neglected, outdated site.
• Evaluate platform performance characteristics before committing: Page speed scores for typical sites on each platform vary significantly, test before deciding.
• Assess the vendor's long-term roadmap and community: Platforms with declining communities or uncertain futures create migration risk within 3 to 5 years.
• Document all required CMS capabilities before vendor selection: Approval workflows, multi-language support, and content scheduling are examples that vary by platform.

Integrations and Third-Party Dependencies

Every tool the site must connect to is a technical dependency that affects scope, timeline, and budget. These must all be documented before scoping begins.

• List every third-party integration with current API documentation: CRM, marketing automation, payment, booking, and analytics integrations each add scope and complexity.
• Verify API compatibility between the new platform and existing tools: Platform migrations often break integrations that worked previously, check before committing.
• Assign integration ownership in the project plan: Each integration needs an owner who can access credentials, test connections, and troubleshoot failures.
• Budget for integration testing as a distinct scope item: Third-party integrations routinely require more testing time than the integration itself, account for this explicitly.

Hosting, Security, and Performance Requirements

Infrastructure decisions belong in the brief, not as a post-launch discovery. They have direct implications for performance, security, and operating cost.

• Define minimum Core Web Vitals targets before selecting infrastructure: Hosting environment, CDN configuration, and caching strategy all affect LCP, FID, and CLS scores.
• Document SSL certificate requirements and renewal ownership: Let's Encrypt automatic renewal vs. paid certificate management must be decided before launch.
• Specify backup frequency and retention requirements: Data loss after a site failure is preventable, backup policy must be defined in the scope.
• Evaluate CDN necessity for media-heavy or globally served sites: Sites with significant image or video content and international audiences will see dramatic performance improvements with CDN delivery.

Budget and Timeline Factors

Budget and timeline are constraints, not suggestions. Scope must be calibrated to what is achievable, not what is aspirational. Understanding process decisions that affect outcomes helps teams make informed trade-offs before committing to a scope.

Scoping to a Realistic Budget

A budget that is too low for the required scope produces a compromised site. Full requirements documentation prevents both over-delivery and under-delivery.

• Build a complete requirements document before requesting quotes: Agencies pricing against incomplete requirements will price for assumptions that may not match reality.
• Separate must-have from nice-to-have features explicitly: Prioritized scope allows trade-offs to be made transparently rather than discovered mid-project.
• Account for content production in the total budget: Copy writing, photography, and video production are often 20 to 40 percent of total project cost, not zero.
• Include post-launch support and iteration budget: The first 90 days after launch typically surface issues and optimization opportunities that require additional investment.

Launch Date Constraints and Their Impact on Scope

A hard launch deadline may require descoping features to maintain quality. A partially scoped, well-executed site outperforms a rushed full-scope launch.

• Define the hard deadline and its business drivers explicitly: Understanding why a date is fixed helps teams make smarter trade-off decisions when scope conflicts arise.
• Identify which scope items are launch-critical vs. phase two: Not everything needs to launch on day one, phased delivery protects quality and deadlines.
• Build buffer into every phase for review and revision cycles: Client review turnaround time is the most common source of timeline slippage, plan for it.
• Agree on a scope reduction protocol before the project starts: Knowing in advance how descoping decisions will be made prevents conflict when the inevitable trade-off arises.

Internal Resource Availability

The client team's availability is a timeline constraint as real as the agency's capacity. It must be factored into the project plan from day one.

• Identify who owns content production and approval on the client side: Content production is consistently the longest-lead item in any redesign, start early.
• Define the review and approval process before the project begins: Unclear approval chains cause revision cycles to multiply and timelines to compress.
• Block client stakeholder calendars for critical milestone reviews: Unavailable stakeholders are the most common cause of redesign timeline slippage.
• Assess whether content migration can be completed by internal teams: Large content migrations may require dedicated resources, internal teams often underestimate the time required.

Using a Framework to Weigh All Factors

Decision framework for redesign thinking gives teams a structured tool for evaluating all factors systematically so nothing is overlooked.

The Four-Quadrant Factor Assessment

Group all factors into four quadrants: strategic, design and UX, technical, and constraints. Rate readiness on each before briefing any agency.

• Score strategic readiness first: If goals and audience are unclear, every other investment is premature, resolve these before proceeding.
• Identify technical unknowns explicitly: Unknown integrations, undocumented platforms, and unclear hosting requirements are the source of most budget overruns.
• Document constraint clarity: Vague budget ranges and soft deadlines create more risk than hard constraints, get to specifics early.
• Use low-readiness scores as discovery agenda items: Factors where readiness is low become the questions your agency must answer in discovery.

Prioritizing When Factors Conflict

When budget constraints conflict with scope ambitions, the goal hierarchy resolves the conflict. Build the scope items that most directly serve the primary goal first.

• Rank scope items by direct impact on primary goal: Items with high goal alignment and lower cost deliver the best ROI ratio and should be prioritized.
• Defer high-cost, low-goal-impact items to phase two: Nice-to-have features that don't serve the primary conversion goal can be built later without compromising launch.
• Evaluate trade-offs in terms of conversion impact, not effort: A feature that takes twice as long but doubles conversion rate is worth the extra time.
• Document every scope trade-off decision in writing: Written records of descoping decisions protect both the agency and client when scope questions arise later.

Using Factor Gaps to Define Discovery Questions

Factors where readiness is low become the agenda for the discovery phase. The agency's job in discovery is to resolve the gaps the client has identified.

• Present your factor assessment to the agency at kickoff: Sharing your own readiness scores gives the agency a structured starting point for discovery.
• Require the agency to produce a discovery findings document: Discovery should produce documented answers to every low-readiness factor, not verbal discussions.
• Treat discovery outputs as binding scope inputs: The scope agreed after discovery should be traceable to specific discovery findings.
• Budget for discovery as a distinct project phase: Rushing from brief to design without a discovery phase is the single most common cause of redesign scope surprises.

Conclusion

Every factor in this checklist affects the final outcome of your redesign. Skipping the strategic factors produces a site that looks different but performs the same.

Skipping the technical factors produces budget overruns and post-launch surprises. Skipping the content factors produces a beautiful site with placeholder text that never gets replaced.

Score your current readiness on each factor category before your next agency conversation.

The factors where your readiness is lowest are your preparation list, and addressing them before you brief a single agency will produce a better scope, a more accurate quote, and a significantly better outcome.

Webflow Development Services

Webflow Experts On-Demand

Whether you're starting fresh or need a full revamp—we create fast, modern Webflow sites built for growth.

Let's talk

LOW/CODE Agency Evaluates Every Factor Before Scoping a Single Page

LOW/CODE Agency's discovery process systematically addresses every factor in this checklist, strategic, UX, technical, and commercial, before any scope is agreed or any design begins.

We don't skip the hard questions because they make the brief more complicated.

We work as a strategic product team, not a dev shop.

That means our clients arrive at scoping with a complete picture of what their redesign needs to accomplish and why, not a wishlist that becomes a scope fight mid-project.

• Strategic discovery and goal alignment: Facilitated sessions that align stakeholders on measurable goals before design begins.
• Technical requirements documentation: Full integration, platform, and infrastructure assessment before any scope is agreed.
• UX and information architecture design: Audience-driven IA and conversion flow design grounded in real user behavior data.
• Content strategy and migration planning: Copy, messaging, and content production scoped and scheduled as first-class deliverables.
• Budget and timeline calibration: Honest scope-to-budget matching that prevents over-delivery and mid-project cuts.
• Measurement and analytics setup: GA4, Google Tag Manager, and conversion tracking configured as a standard deliverable, not an afterthought.
• Post-launch optimization support: Data-driven iteration in the first 90 days when redesign impact is highest and changes are most valuable.

LOW/CODE Agency has delivered 450+ digital products for clients including Coca-Cola, American Express, Sotheby's, Medtronic, Zapier, and Dataiku. We bring the same systematic rigor to mid-market businesses that enterprise teams demand.

Start with a scoping call with the redesign agency that considers everything.