Clients ask for a “redesign” when they mean a refresh, and they ask for a “refresh” when they actually need a redesign. The distinction is not semantic — it determines how long the project takes, what it costs, and whether the result solves the actual problem. Here is how to tell the difference.
What a Website Refresh Is
A refresh changes how a site looks without changing what it is built on. New colors, updated typography, better photography, revised copy, modernized button styles. The underlying codebase — the theme, the template structure, the CMS — stays the same.
A refresh makes sense when:
- The site loads fast and functions well, but looks dated
- The brand has evolved but the architecture is sound
- You want to update specific pages without affecting others
- Budget and timeline do not allow a full rebuild
A refresh is typically faster and cheaper than a redesign. The trade-off is that you inherit whatever limitations exist in the current codebase. If the theme is Elementor-based with poor performance, a refresh does not change that. If the site structure causes SEO problems, a refresh does not fix them.
What a Website Redesign Is
A redesign starts from zero. New information architecture. New wireframes. New development. The site you launch after a redesign may look similar to the old one or radically different — but the codebase is new regardless.
A redesign is necessary when:
- The current site has fundamental structural problems (poor performance, broken mobile layouts, outdated CMS version)
- The business has changed significantly and the site architecture no longer matches how customers navigate to conversion
- The underlying platform needs to change (moving from Wix to WordPress, from page builder to custom code)
- The site is holding back SEO because of technical debt that cannot be patched
A redesign is a larger investment in both time and money. Done right, it is also a larger return — because you are not iterating on something broken, you are building something that works.
The Wrong Reason to Redesign
The most common reason clients decide they need a redesign: the site looks old. That is a refresh problem, not a redesign problem.
The most common reason clients decide to refresh: they got a quote for a redesign and it seemed expensive. That logic costs more in the long run. If the site’s performance is dragging down Google rankings, if the mobile experience is losing conversions, if the checkout flow is broken — a coat of paint does not fix any of that.
The question to ask is not “what do we want it to look like?” It is “what is the site failing to do, and is that a visual problem or a structural one?”
How to Diagnose Which You Need
Run your current site through honest.designodin.com or Google PageSpeed Insights. Look for two categories of issues:
Visual and content issues — images look dated, typography is inconsistent, copy is outdated, color scheme does not match current branding. These are refresh problems.
Structural issues — PageSpeed score below 50, mobile layout breaking at specific widths, Core Web Vitals in the “Poor” range, high bounce rate on mobile sessions, crawl errors in Google Search Console. These are redesign problems.
If your PageSpeed score is 38 on mobile and your LCP is 8 seconds, updating your color palette does not move the needle. The problems are in the code, not the design.
What Changes in a Full Redesign
When we do a redesign at Designodin, the starting point is not the current site. It is the business: who are the visitors, what do they need to do, and what is the fastest path to conversion.
From that foundation, the work includes:
- New sitemap and URL structure (planned around SEO and user navigation)
- New wireframes for key page templates
- Custom design in Figma, reviewed and approved before development starts
- Hand-coded WordPress theme built from scratch — no page builder, no template starter
- Performance optimization built in from the first line of code
The result is a site that performs at 90+ on PageSpeed from day one, loads correctly on every device, and does not inherit the technical debt of whatever came before it.
What a Refresh Actually Involves
A refresh on a well-built site is a legitimate project. If the foundation is solid, you can update a custom CSS layer, swap brand colors globally, replace photography, and update copy — without touching the underlying structure.
The risk: refreshing a poorly-built site to make it look better is a short-term fix with a visible expiry date. A year later, you are back in the same conversation. Except now the old site is more dated and the new visual layer has created inconsistencies the original developer did not anticipate.
If the site you want to refresh is an Elementor build with a PageSpeed score under 50, the honest answer is that a refresh will change what visitors see but not what they experience. Performance will stay the same. Mobile behavior will stay the same. SEO signals will stay the same.
Timeline and Cost: What to Expect
A professional website refresh — copy, visuals, photography, minor structural updates — typically runs 2–4 weeks. Cost varies widely based on the number of pages affected, whether new content is being created, and how deep the CSS changes go.
A custom WordPress redesign from Designodin runs 4–8 weeks from kickoff to launch. Our custom WordPress development packages start at $10,000 for sites that need a full rebuild. For smaller sites where the foundation is sound, our WordPress Starter package at $697 delivers a new hand-coded build without the enterprise price tag.
The decision is not about what you can afford right now. It is about what the problem actually is. Pay for a refresh on a broken foundation and you will pay again, sooner than you expect.
Signs You Are Being Sold the Wrong Thing
Watch for these situations:
Agency recommends a redesign when a refresh would do. This happens when an agency sells projects rather than solutions. If your PageSpeed score is 90, your mobile experience is clean, and your conversion rate is reasonable — updating the visual design is a refresh, not a rebuild.
Agency recommends a refresh on a site that needs a rebuild. This happens when the agency cannot or will not build from scratch. If your Elementor site is loading in 8 seconds and they offer to “update the theme styling,” they are avoiding the conversation about the actual problem.
Ask any agency you are evaluating: what specifically in the current site requires a full rebuild versus what can be updated in place? If they cannot answer that with specifics, they have not actually diagnosed your site.
The Ownership Question
One factor that affects both options but rarely gets discussed: who owns the code.
On a page builder site (Elementor, Divi, WPBakery), the “design” lives inside a proprietary interface. Switching away from that page builder in a refresh means rebuilding those pages regardless. The visual layer is architecturally tied to the builder. A refresh on those sites is always more expensive than it looks, because you cannot simply swap CSS — you are working within the page builder’s constraints.
On a hand-coded WordPress site, the code is yours. A refresh means editing CSS and templates directly. No proprietary interface. No builder to fight against. The work is proportional to the scope.
Code you own never becomes a hostage. That applies to redesigns and refreshes equally.
If you are not sure which your site needs, start with an audit. honest.designodin.com gives you a concrete picture of your site’s current performance and structural health. From there, the decision becomes clear. When you are ready to act, our fixed-price packages cover both options.