When a redesign actually makes sense
Redesign is the answer to a specific problem you can measure. If you don't have a metric that should improve after the overhaul, you don't need a redesign.
First reason - the site isn't mobile-friendly. If buttons overlap on phones, text is unreadable, and forms don't fit the screen, that's not cosmetic. Check your analytics: if 60-80% of traffic comes from mobile but conversion there is several times lower than desktop, the problem is obvious. A redesign is fully justified here.
Second - outdated visuals kill trust. If your site looks like 2010, visitors may think the company stopped operating years ago. This is especially critical for consumer-facing businesses: people decide in seconds. But important: if the design just isn't to your taste but conversion is fine, that's not grounds for a rebuild.
Third - the site is slow. If pages take more than three seconds to load, some visitors leave before they see anything. You can check with Google's PageSpeed Insights. But here's the nuance: a slow site often doesn't need a full redesign, just optimization - compress images, configure caching, clean up code. Redesign is needed if the current implementation is so bloated it's easier to rewrite than fix.
Fourth - your business model changed. You sold services to corporations, now you're moving to consumers. Or you added an online store to an informational site. The old structure doesn't support that, and here redesign isn't a whim, it's a necessity.
When redesign is wasted money
Redesign won't solve problems that lie outside the design. That sounds obvious, but in practice half of redesign requests are attempts to ignore the real reason for failure.
First trap - low conversion due to a weak offer. If your product is more expensive than competitors without a clear reason, or your value proposition sounds like 'quality, reliability, experience,' new design won't help. Pretty packaging doesn't sell an unattractive offer. Check this: if the site has traffic but no inquiries, start by analyzing copy, pricing, competitors. If inquiries come in but don't close, the problem is in sales, not on the site.
Second - the site is slow because of hosting or backend. Sometimes the frontend is light but pages load for five seconds because the server is weak or the database is poorly configured. Redesign does nothing here. Ask your current developer to check server response time - if it's over a second, fix the backend first.
Third - you just want to refresh it. This is the worst reason for a redesign. If the site brings in inquiries, conversion is growing, and the mobile version works, don't touch it. Any design change is a risk: you might lose elements users are familiar with, break the usual path to conversion, drop search rankings because of structural changes. Updating for the sake of updating is like tearing down a house because you're bored with the wallpaper.
Fourth - there's no traffic. If 50 people visit the site per month, redesign won't change the situation. First set up advertising, SEO, social media. When traffic appears, you'll see whether the current design works or needs adjustments.
Partial redesign: when targeted fixes are enough
A complete overhaul is rarely needed. More often it's enough to change specific blocks that aren't working. It's cheaper, faster, and safer: you don't break what's already bringing results.
If the problem is localized - low conversion on the contact form, unclear homepage, awkward catalog - start with targeted fixes. Connect your analytics, enable session recordings and click maps. See where visitors stop, what they click, at what point they leave. This shows exactly what needs to change.
Example: you see 70% of visitors reach the order form but don't submit it. You open a session recording - there are eight fields including tax ID and patronymic. Remove unnecessary fields, keep phone and name. Conversion grows. That took an hour of designer work and two hours of programming, not a month-long full redesign.
Another example: the homepage has traffic but almost no one goes further. You watch a session - visitors scroll, don't find the section they need, and close the site. Solution: add clear navigation and a services block at the top. That's not a redesign, it's a structural fix.
Partial redesign works if the site foundation is sound: responsive layout, normal speed, logical structure. Then you only change the problem areas.
How to tell the problem is actually the design
Before redesigning, you need to prove the problem is the design and not traffic, your offer, or ad settings. Without that you risk spending money for nothing.
Step one: check if there's traffic. Open your analytics and look at visitor count over the last month. If it's under 500, work on traffic first, then think about redesign. With low traffic you can't assess whether the design works.
Step two: look at conversion. That's the percentage of visitors who submitted an inquiry, called, or bought. If conversion is below 1-2% for consumer sites or below 3-5% for business sites, dig deeper. Turn on click maps and session recordings in your analytics, record 20-30 sessions. Watch: do people scroll to the bottom or leave immediately? Do they try to click inactive elements? Do they start filling the form but abandon it halfway?
Step three: compare mobile and desktop. If conversion on phones is three times lower, the problem is responsiveness. If it's equally low everywhere, it's not the layout but the offer or content.
Step four: check speed. Go to PageSpeed Insights, paste your site URL. If the score is below 50 for mobile, that's critical. But remember: slow loading can be due to hosting, not design.
Redesign and SEO: how not to lose rankings
Redesign is a risk for search optimization. If you change page structure, URLs, or headings, you can lose rankings you spent months building. To avoid this, plan the migration ahead of time.
First: don't change URLs unless absolutely necessary. If a page was called /services/web-development, keep it that way. If you must change addresses, set up 301 redirects from old URLs to new ones. That's an instruction for the server: 'this page moved, send the user there.' Without redirects the search engine thinks pages were deleted and drops them from the index.
Second: preserve heading structure. H1, H2, meta title and description tags - that's how search engines understand what the page is about. If the old design had H1 as 'Web Development Services,' don't change it to 'We Make Websites.' That's a drop in rankings.
Third: don't delete text content. If the old site had an article or service description section, transfer it to the new design. Search engines rank sites by content, not images.
Fourth: verify responsiveness. Google has used mobile-first indexing since 2021 - meaning it evaluates the mobile version first. If the new design works poorly on phones, rankings will drop.
Fifth point: ask your developer to connect search console tools right after launch. You'll see indexing errors, broken links, configuration problems. The first two weeks after redesign are critical, when you need to monitor traffic changes and quickly fix errors.
What redesign costs and what goes into the price
Redesign price depends on scope: how many pages, whether you need layout from scratch, whether content transfers, what integrations are connected. An exact quote requires a brief, but EFIMOV DEV publishes starting ranges for each service - that helps you orient before reaching out.
A landing page or simple five-page corporate site is cheapest to remake: design, responsive layout, basic setup. If the site is more complex - product catalog, user dashboard, CRM integration - price grows proportionally to screen count and logic.
Common question: can you use the old engine or need a new one? Depends on condition. If the site is on WordPress or another popular CMS that's updated and supported, you can keep the backend and redo only the frontend. If the engine is custom-built, outdated, or sluggish, it's easier to rewrite from scratch on a modern stack. We use React and Node.js, which lets us build fast and scalable solutions.
Another factor - content. If texts, photos, and structure stay the same, that saves time. If you need to manually transfer materials from the old site, write new descriptions, or process images, that's separate work that goes into the estimate.
And last: testing and revisions. After the first version you usually need two or three iterations to get the design to working condition. That's normal and built into the timeline. If a contractor says they'll do a turnkey redesign in a week, that's a red flag.
How not to waste budget: what to check before starting redesign
Before ordering a redesign, check three things so you don't spend money for nothing.
First: state the redesign goal in one sentence. 'I want it prettier' isn't a goal. 'Increase conversion from 1% to 3%' or 'Make the site usable on phones so mobile conversion matches desktop' are goals. If you can't name the metric that should change, you don't need a redesign.
Second: ask for an itemized estimate. Not one line 'site redesign - $5,000' but a breakdown: homepage design, internal page design, layout, form connection, CMS setup, content transfer, testing. If the contractor can't detail what you're paying for, that's a bad sign.
Third: discuss what stays from the old site. Will URLs, headings, texts be preserved? Who will set up redirects? Who will verify analytics didn't break? These questions need answers before signing a contract, not after launch when traffic has already dropped.
What to do after redesign launch
Redesign isn't the end point, it's the start of testing. The first two weeks after launch are critical: you need to track metrics and quickly fix errors.
First week: check analytics. Is it connected, are goals working (form submission, call, purchase). If the tracking isn't installed or goals aren't recording, you're working blind.
Second week: turn on session recordings and record 20-30 sessions. Watch how visitors use the new design. If you see them clicking past buttons, not finding the menu, abandoning forms, that's a signal for fixes.
First month: compare conversion with the previous period. If it didn't grow or dropped, dig deeper. Maybe functionality broke, load time changed, or search engines haven't reindexed pages yet. If after a month conversion is still lower, go back to the contractor with questions.
Last advice: don't change everything at once. If you have a large site, launch redesign gradually: first the homepage and key pages, then the rest. It's easier to control results and you don't risk all traffic.
Redesign is a tool, not an end in itself. It's justified when design hurts conversion: the site doesn't work on mobile, loads slowly, looks so outdated it kills trust, or doesn't fit a changed business model. In all other cases - weak offer, lack of traffic, backend problems - redesign won't help. Before starting, state your goal in one sentence, ask for an itemized estimate, and verify the problem really is the design and not something else. If you need consultation or assessment of your current site, let's discuss your project directly.
Frequently asked
Can you skip redesign if the site is old but working?
Yes, if conversion is normal, traffic exists, and the mobile version works. 'Old' isn't a diagnosis. If the design doesn't prevent you from reaching business goals, don't touch it.
How do you know redesign will pay off?
Calculate current conversion and average profit per inquiry. If redesign increases conversion by even 1-2 percentage points, calculate additional profit over three months. If that covers redesign cost, it will pay off.
Do you need to remake the site if it's not mobile-friendly?
Yes, that's one of the most justified reasons for redesign. If 60-80% of traffic is from phones but the site doesn't work there, you're losing most potential clients.
Can you redesign without losing search rankings?
You can, if you preserve URLs, headings, text content, and set up redirects. But there's always risk, so redesign needs to be done carefully, with SEO involvement.
How long does redesign take?
From two weeks for a simple landing page to two or three months for a large corporate site or online store. Exact timeline depends on page count, integrations, and revision rounds.