Most website improvement advice is a list of everything you could possibly do, which is useless when you have a budget, a quarter, and a business to run. What follows is the order we actually work in when a client asks us to improve a site rather than replace it, and why that order matters.
The short version: find out what is broken before you redesign anything, fix speed and mobile before you fix aesthetics, and make sure someone can keep the site current afterwards. Everything else is refinement.
Start with evidence, not opinions
The fastest way to waste a website budget is to redesign based on what the leadership team dislikes. Spend a week gathering evidence first.
Analytics: which pages get traffic, which pages people leave from, and what share of visitors are on a phone.
Search data: which queries already bring you visitors, and which pages rank for them.
Sales and support: the questions your team answers repeatedly are the pages your site is missing.
A performance and accessibility scan, so you have numbers rather than impressions.
By the end of that week you usually find that two or three pages carry most of the value, and that is where the work should go.
Fix the first five seconds
Above the fold, a visitor needs three things answered: what you do, who it is for, and what to do next. If your homepage headline could be pasted onto a competitor's site without anyone noticing, it is not doing any work.
Be specific. Name the industries you serve, the outcome you deliver, and the region you operate in if that is relevant to buyers. Put one clear primary action in view, and stop competing with it — a header with six equally weighted buttons is a header with no call to action at all.
Make the phone experience the real one
Mobile is usually the majority of traffic and still gets designed second. Check the things that break in practice: tap targets that are too small or too close together, sticky headers that eat a third of a small screen, forms that demand too much typing, tables that overflow, and text that is only comfortable at 16 pixels or larger.
Test on a real device on a real connection, not just a browser window dragged narrow. The two experiences are not the same.
Performance is a conversion issue
Speed work in 2026 is mostly unglamorous and mostly effective. The usual wins, in order of payoff:
Images: correctly sized, modern formats, and lazy loading everywhere except the one large image at the top of the page. That hero image should load eagerly, because it is almost always what the browser measures your load time against.
Fonts: fewer families and fewer weights, loaded so text is visible while they download rather than after.
Third-party scripts: every chat widget, heatmap, and tag costs you. Audit them and remove the ones nobody has opened a report from in six months.
Layout stability: reserve space for images and embeds so content does not jump while the page loads. Nothing feels cheaper than a page that moves under your thumb.
Accessibility, done properly, improves the site for everyone
Colour contrast, a logical heading structure, visible keyboard focus, labelled form fields, descriptive link text, and alt text that describes the image rather than repeating the file name. None of this is expensive when it is designed in, and all of it also helps search engines and AI assistants understand your pages. Our accessibility guide goes through the specifics.
Get the content out of the design
If updating a case study or a team member means asking a developer, your site will go stale. Anything that repeats — work, services, team, locations, posts — should live in a CMS with clearly named fields, so a non-technical person can add an entry and have it appear correctly everywhere it is referenced.
This is the single change that most reliably keeps a site alive two years after launch, and it is the main reason we build on modern platforms rather than a hand-rolled stack. If you are weighing those platforms up, we compared them in Webflow vs Framer and set out our reasoning for Webflow in particular on our Webflow page.
SEO and AEO in the same pass
Search has two audiences now: the ranking algorithm and the AI assistants that summarise answers. Fortunately they reward a lot of the same things.
Give every page one clear H1 and a heading structure that reflects the actual content. Write a distinct meta title and description per page. Answer the specific question a page is about in the first paragraph, in plain language, rather than building up to it. Use structured data where it applies. Keep URLs readable and stable. And link between your own pages deliberately — internal links are the cheapest ranking improvement most sites have available and the one most consistently ignored.
Then make it look like you
Visual polish comes after the above, not before. When it does come, the highest-value moves are usually consistency rather than novelty: a tightened type scale, real spacing rhythm, restrained motion, and your own photography instead of stock. Stock imagery is the fastest way to make a credible business look generic, and buyers spot it immediately.
Decide who owns it on the Monday after launch
Most sites decay because nobody owns them. Before you finish the work, agree who publishes content, how often the site gets reviewed, and who is called when something breaks. If that person does not exist internally, buy the capacity — it is what our website support service exists for.
A realistic 90-day order of operations
Weeks 1 to 2: gather evidence, audit performance and accessibility, and agree what the site is actually for.
Weeks 3 to 5: rewrite the homepage and your two highest-value pages, and fix mobile on those pages first.
Weeks 6 to 8: performance and accessibility fixes site-wide, plus metadata and internal linking.
Weeks 9 to 12: move repeating content into the CMS, add the pages your sales and support data says are missing, and hand over ownership properly.
If, halfway through that, you conclude the underlying site is fighting you at every step, that is a legitimate finding. A rebuild is sometimes cheaper than a year of workarounds — and if you need something lean and fast, a single-page site is often more than enough.
You can see how this plays out across real projects in our work. If you want an outside read on which of these would move the needle most for your site, get in touch.
