A site redesign is a change of look on a live site that already has addresses, items, and visitors. The task here is twofold: to do better and not to reset what worked before you. Therefore, we start not with the layout, but with measurements - the list of addresses, the weight of HTML, the time of the first server response, the state of the counter. The term of work is 20–45 working days. There is no price on the page on purpose: a cosmetic update and a restructuring of the structure look the same from the outside, but are calculated completely differently.
119.5 KB in dark layout with animated first screen
after a free audit
Price
30
Guarantee
days after project sign-off
119.5
The lightest multi-page HTML in our sample
KB in dark layout with animated first screen
285.9
The first response from the same server
ms, full HTML in 439.4 ms, measured on 07/31/2026
751.2
The most difficult document among the same 16 sites
KB is four times the sample median
20-45
Redesign period
working days, six stages
free audit with measurements, 3-5 working days
Before the estimate
30
After acceptance
calendar day warranty and re-measurement
Free audit before redesign
The most expensive redesign mistake is losing what already worked. Therefore, before the layouts, we take the state of the site: which pages give traffic, which addresses cannot be touched, and which technical aspects should be corrected at the same time.
What we measure
A complete list of addresses and their statusHow many pages are there in the site map, how many of them are unique, which give 301 and 404. This is the basis of the redirect map: without it, moving to a new design eats up items.
What exactly changes — appearance or structureIf the addresses remain, this is one volume of work. If paths change, a one-to-one redirect map is required and is a separate step visible in the estimate.
Speed and weight before recyclingWe measure the first response of the server and the weight of HTML to the works. In our sample, there were 119.5 KB with a saturated visual layout, and 751.2 KB with a simple main one.
Structured data and meta tagsWhat is currently being searched for and what should be saved from it. We don't touch the title of pages that give traffic for no reason - even if the new design asks for a different length.
Analytics: Is there anything to compare with?We check whether the counter is alive. If not, we put it before the start of work, otherwise, a month after the launch, there will be nothing to prove that things have gotten better.
A map of addresses marked as untouchable and a draft map of redirects if the paths change.
List of technical defects that should be fixed with the redesign.
A conversation for 40 minutes, where we go through the document and the scope of changes.
Timeline: 3-5 working days
Why is it free
Because after measurements, it often turns out that the site does not need a redesign, but three corrections and new photos. We prefer to say this before the contract, not after.
What's next
After the audit, we give an estimate by stages with calendar dates and a separate line — traffic conservation work. "After" measurements are taken two weeks after launch and placed next to the initial ones.
Short form: your contact and site URL
Contract, act and 30-day warranty
Every project gets a written contract: scope, deadlines, amount, acceptance procedure. After delivery — act and invoice, then 30 calendar days of warranty.
Sole proprietor & bank transfer
The contractor is a registered sole proprietor. Payment by invoice with closing documents.
Rights & access — yours
Code, design and materials transfer to you after full payment. Domain, hosting, repository and analytics are registered to you.
Client portal instead of email chains
During the project you get access to a portal: contracts, invoices, acts and project status in one place.
European clients
Among our work — projects for Norway, Bulgaria, Moldova and Spain.
Verifiable numbers
Every case in the portfolio comes with a link to a live site and a technical measurement.
Audit first, then pricing
There is no price list on the site intentionally: the scope of the same work differs multiples between clients.
We say "no" when unsure
If the task isn't ours or the deadline is unrealistic — we tell you upfront.
What affects the price
Why two seemingly identical tasks are priced differently
Number of page typesIt is not the total number of pages that counts, but the number of dissimilar templates. Five types on a site of one hundred pages is a common story; twenty unique layouts for the same volume double both design and layout.
Do addresses change?Redesign without changing paths is the cheapest and safest option. As soon as the structure moves, a separate step is added: address inventory, 301 one-to-one map, validation of each rule after launch.
The platform the site lives on nowA WordPress site with a standard theme changes clothes predictably. A self-written engine without documentation or a constructor without export requires parsing someone else's code - this is a time that cannot be estimated until you look inside.
Content and photo statusReady-made texts and photos on a uniform background save weeks. If the service descriptions are in PDF, and the photos are screenshots from the messenger, content preparation becomes a separate line of the estimate.
Language versionsEach additional language is not only a translation, but also a hreflang, separate URLs and a separate redirect check. A bilingual site gives twice as many rules to break when moving.
Pace of approvals on your partThe most frequent reason for a deadline shift is not a layout, but a week of waiting for a decision on the main issue. One person with the right to say "I approve" shortens the calendar term more significantly than any acceleration on our side.
Who it's for
Situations where this service delivers results
Scenario 1 of 4
The site is six or seven years old, and it is immediately visible from the phone
The menu cannot be opened with a finger, the table moves out of the screen, the application button is under the form that needs to be completed. Such a site is not "a little inconvenient" - it cuts off the part of the audience that enters from a mobile phone, which is usually the majority. Here, the redesign gives the fastest effect, because it changes not the taste, but the physical ability to get in shape.
We'll review your situation in a free audit
Scenario 2 of 4
The company has changed, and the site tells about the previous one
New directions appeared, old ones disappeared, the scope of clients changed. The site remained an extract from the state at the time of launch: the sections are called incorrectly, the main one promises the wrong thing, and the new service has nowhere to be put. This task is not about beauty, but about making a person understand where he got to in the first five seconds.
Scenario 3 of 4
The structure rested on the ceiling
The sign is simple: to add a section, you have to break something, and the same page opens from three different ways. Then the redesign affects the addresses, and this is already a move — with a map of redirects, and not just with new colors. The amount of work here is different, and we show it in a separate line of the estimate, and do not hide it in the total amount.
Scenario 4 of 4
There is traffic - and that is why touching is scary
The most frequent state of our customers: the site is ugly, but it gives applications from somewhere, and no one wants to break what feeds them. That's why we start with a list of pages that actually bring people and fix them as inviolable: the address, title and structure of the titles remain, the shell around them changes.
What's included
Complete list of work and what you get as a result
We record the state of the site before work — speed, HTML weight, list of addresses, markup — so that there is something to compare with after launch
We draw a design under your brand with a set of templates: main, typical internal, card, forms - it's cheaper and faster than a unique layout for each page
We make an adaptive with a weight budget: the target figure is fixed before the beginning of the design, and not explained after the fact
We leave the old addresses wherever the structure allows: the cheapest way to save items is simply not to move
Where addresses do change, we map 301 redirects one-to-one: page to corresponding page, not everything to the main page
We do not touch the title of pages that are already giving traffic, even if the new layout asks for a different length of the title
We transfer content with analysis of duplicates and empty pages - what makes sense goes to the new site, not everything in a row
We close technical SEO at the same time: canonical, sitemap without duplicates, robots.txt with the working line Sitemap
We put JSON-LD — Organization, BreadcrumbList and types for your niche; we mark only what is actually on the page
We check the counter and adjust events for key actions, otherwise in a month there will be nothing to prove that things have gotten better
We measure after launch and put next to the initial numbers; guarantee of 30 calendar days after acceptance
When this service isn't right
What's not included — so there are no surprises at delivery
Rebranding: logo, corporate style and brand book
Copywriting of all site texts from scratch
Photography and purchase of illustrations
Post-launch promotion and compensation for seasonal traffic fluctuations
Moving to another platform is a separate task with a separate estimate
Process steps
Transparent stages with approval at every step
Total duration:20–45 days
1
Audit and map of addresses
3-5 working days
We take measurements "to", collect a complete list of addresses, mark the pages that give traffic and which cannot be touched. The output is a document based on which the estimate is calculated.
2
Prototypes
3-5 working days
Skeletons of typical pages without colors: what is where, in what order it is read, where the button leads from. Editing the structure here costs hours, after layout - days.
3
Design
6-10 working days
Main and typical internal in your identity. Here we fix the target weight of the page: in our sample, on the same tasks, HTML weighs from 119.5 to 751.2 KB, and the difference is not in beauty.
4
Layout and assembly
7-14 working days
Responsive layout, building templates on your platform, forms, connecting mail and messenger. In parallel, we prepare a map of redirects if the paths change.
5
Transferring content
3-8 working days
Texts, photos, metatags are moved with analysis of duplicates and blanks. Title pages with traffic are transferred without changes - this is a rule, not a wish.
6
Redirects, testing, launching
2-4 working days
Running each 301 rule, checking forms, markup and counter, returning the full sitemap to Search Console immediately after switching.
Did not find your case?
Describe how it works on your side — we will tell you whether “Redesign of the site” fits and what it means in your situation. No brief and no call: one question, one answer.
Cases
Tasks and results in numbers — all metrics measured by us
aesthetic medicine clinic abroad
Task
Put together a site with a complex visual layout - a dark scheme with accents, an animated first screen, a service directory, reviews and FAQ - and not turn it into a heavy document.
Solution
WordPress with Bricks builder and custom layout instead of a ready-made theme. Semantic layout, localization for the country's market, connected GTM, GA4 and Meta Pixel.
Result
Measurement 07/31/2026: 26 published pages under X-WP-Total header of open REST API, first server response 285.9ms, full HTML load 439.4ms at 119.5KB. It's the lightest multi-page document among the 16 sites measured — only one is lighter in the sample, and that's a single page. Defects found, which we recorded: the site map is not given to any of the standard addresses and is not declared in robots.txt, there is no structured markup of the establishment. Both points are in the works.
plastic surgery clinic with JavaScript frontend
Task
The site is assembled as a single-page application: the browser draws the content for a person, and the ready-made HTML must be given to the search bot. The question was whether such a scheme would withstand the search requirements.
Solution
A prerender for bots plus a full set of structured data. The robots.txt policy is written separately: training AI-crawlers are blocked, searches with source citation are allowed.
Result
Measurement 07/31/2026: 126 KB of HTML is given to the bot in 145 ms to the first byte and 178 ms to the full document, in the markup of 10 types of JSON-LD, a site map of 89 addresses. At the same time, the browser receives a 3.0 KB shell without H1 and description - this is how the scheme is arranged, and that is why the prerender is not an ornament here, but a condition for indexing. Defect found: The inline GTM snippet self-blocks due to an error in the exit condition, so the container does not load at all.
Ukrainian SaaS platform for working with product descriptions
Task
Show what a lightweight public product site looks like: eight pages, structured data, payment to the FOP account.
Solution
Next.js, JSON-LD with SoftwareApplication, Offer, Organization, WebSite and FAQPage, connected PWA manifest.
Result
Measured on 07/31/2026: 220.6ms first response at 140.8KB HTML, the fastest response of the 16 sites measured. There are two defects nearby, which we show openly, because they are often brought with them after a redesign: robots.txt refers to a sitemap that gives a 404, and the markup declares a rating of 4.8 with 50 ratings, which is not on the page.
Technologies & integrations
What we build on and what it connects to
Stack
Next.js + React + TypeScript — when the site must be fast, and the content rarely changes; restrictions: you cannot edit the layout without a developer
WordPress + Bricks Builder — when pages and news are maintained by your marketer; limitations: the designer easily turns a good layout into heavy HTML, so we hold the weight with our hands
OpenCart — if the redesign affects the store: change the theme, leave the catalog and checkout in place
Tailwind CSS — styles do not spread between templates; limitation: it is more expensive to rewrite someone else's topic on it than your own
nginx and HTTP/2 — returning static and parallel requests without a queue
Cloudflare - cache and TLS; limitation: the cache masks a slow server, not cures it
Integrations
Google Search Console
GA4
Google Tag Manager
Meta Pixel
Google Maps
Telegram bot for applications
KeyCRM
reCAPTCHA
Redesign vs. a new site from scratch
How this option differs from the alternative
New site from scratchOur approach
What will happen to the addressesstructure from scratch, old addresses have to be completely coveredremain where possible; where not - 301 one-to-one
Risk for itemshigher: for search it is a move, the detour takes timelower: the search sees familiar addresses and familiar titles
What will happen to the contentmostly it is written anew - a separate budget and a separate termmoves with analysis of takes, texts mostly remain
Technical debt of the platformresets with the old coderemains if the engine is not changed: the old code will not go anywhere
When appropriatethe engine is not supported, the structure must be completely rebuiltthe site is alive, it gives applications, the problem is in the form and convenience
What we need from you
We can't start without this — best to prepare in advance
1Access to your existing site, hosting and domain control panel.
2Access to analytics and Search Console to see which pages are driving traffic.
3The answer to the question of what exactly does not suit: appearance, structure, speed or number of applications.
4Vector logo and corporate colors; if there is a brand book - his too.
5New photos or consent to use existing ones.
6One person with the right to approve layouts and scope of changes.
If something is missing — let us know, we'll help you gather it or do it as a separate task.
FAQ
Most frequently asked questions — with concrete answers
Will traffic drop after the redesign?
Short-term subsidence is possible, and we will not promise the opposite: the search needs time to go around. The risk is reduced by four things — save addresses where possible, put 301 one-to-one where you can't, don't change the title of pages with traffic and give a full sitemap immediately after the switch. The mistake after which the traffic does not return for months is the same: redirects "all to the main". For search purposes, this means that the old page is no longer there, not that it has moved.
How to understand that you need a redesign, and not a new site?
According to the state of the platform, not according to the state of taste. If the engine is updated, the structure withstands new sections, and the content is up-to-date - this is a redesign: the shell changes, addresses and texts remain. If the engine has been without updates for years, the structure does not allow adding a section, and half of the texts are still rewritten - it is more honest to count the new site, because in the "redesign" nothing will remain from the old one except the domain. We say this at the audit, not after the signing.
Is it possible to do a redesign without changing addresses?
Yes, and this is the safest scenario. If the structure suits and only the appearance changes, the paths remain as they are, and for the search the move actually does not happen. Addresses should be touched only when the current structure interferes — for example, when one page is accessible from five different ways and multiplies duplicates. But keep in mind: cleaning duplicates does not add traffic, it stops scattering it, and on a small site the effect is close to zero.
Will the new design make the site slower?
Don't have to. It's a matter of discipline, not beauty: how many fonts, how many libraries, what images. We measured a clinic site with a dark layout, an animated first screen, and a service catalog, rendering 119.5 KB of HTML in 285.9 ms, the lightest multi-page document in our sample. On another project of the same sample, the main one weighs 751.2 KB, four times more than the median. The difference is not in how complex the layout is, but in what is connected to it. Therefore, we fix the target weight at the design stage, and do not measure it after complaints. A fair boundary: our measure is the server part and the weight of the document, and what a particular person sees depends on their device and network.
How long does the redesign last and why is the lower limit 20 days, and not the sum of the minimums by stages?
20-45 working days. By stages, it looks like this: audit 3-5, prototypes 3-5, design 6-10, layout and assembly 7-14, content migration 3-8, redirects and testing 2-4. Add the minimums - you get 24, not 20. The difference is that part of the work goes in parallel: the redirect map is prepared during layout, and the content is transferred while the templates are being edited. That's 20 days on a simple site with five types of pages. Twenty unique layouts are never included in this term.
What do you measure after launch and when?
Two weeks after the switch, the same things were measured before: the first response from the server, the weight of HTML, the number of addresses in the site map and the share of duplicates, the presence of structured data, the number of events in analytics. Two measurements side by side is the only honest way to tell if it's gotten better or not. Without initial numbers, the conversation about the result of the redesign is reduced to impressions. Separately, honestly: it is too early to compare applications for the first month, because the season is superimposed on them, and we look at them in the horizon of the quarter.
Is it possible to do the redesign in parts, and not all at once?
You can, and sometimes it's smarter. The working order is as follows: first the main page and one type of internal page, launch, measurements, then the rest of the templates. So you see the result earlier and don't pay for everything at once. The price of this approach is a longer overall term and a period when two registrations coexist on the site. For a store with tens of thousands of addresses, this is normal, for a site with twelve pages it is too much gloom, and we will say it directly.
Who is responsible if something falls off after launch?
We, within 30 calendar days after acceptance — this is the warranty period according to the contract. It covers mistakes on our end: broken links, forms that don't submit, a redirect rule that goes the wrong way. Does not cover new additions, consequences of independent changes in the code by third parties and hosting failures. Items in the search are not and cannot be included in the warranty: we are responsible for the technical side of the move, and the contractor does not make the decision to issue.
Send the address of the site and in one sentence - what exactly you do not like about it.
In response, you get measurements of your site, a map of addresses marked as inviolable, and an estimate of works by stages with dates. If it turns out from the numbers that the redesign is not needed now, you will hear it in the first email.
From measured casesMeasured on 07/31/2026: 220.6ms first response at 140.8KB HTML, the fastest response of the 16 sites measured
There is no price list on the site on purpose: the same work differs several times over between two clients, and a “from” figure explains nothing in that case. First a free audit — we count your pages, duplicates and speed — then we name the sum and the deadline and fix both in the contract.