Website performance should be part of a redesign brief from the start. A new visual direction can still feel slow if large images, unnecessary scripts or expensive interactions remain unresolved.

Before choosing a new framework or hosting platform, identify where visitors encounter difficulty. The aim is to improve the experience people actually use, with measurements that help the team decide what to fix.

Begin with important journeys

List the pages and actions that matter to the business: arriving on a service page, opening a case study, comparing an offer or submitting an enquiry. Test those journeys on a phone as well as a desktop, including slower network conditions.

Record specific problems. “The main image appears late” points to a different investigation from “the page looks ready but the menu does not respond”. Also check whether a form or embedded booking tool introduces its own delay.

Understand the three Core Web Vitals

Google’s Web Vitals guidance describes three measures of loading, interactivity and visual stability:

  • Largest Contentful Paint (LCP): when the main visible content appears. Review large hero assets and delays before those assets start loading.
  • Interaction to Next Paint (INP): how quickly the interface responds visually to interactions. Investigate heavy scripts and work that blocks responses.
  • Cumulative Layout Shift (CLS): unexpected movement in the layout. Reserve space for media and review elements that appear after the page begins rendering.

These are useful diagnostic signals, not a complete assessment of a website. A fast page can still have confusing copy or a broken enquiry journey. Performance work should accompany content, accessibility and usability checks.

Check the assets before replacing the stack

  • Serve appropriately sized images rather than using the largest source file for every card.
  • Choose a suitable image format and compression level, then inspect the result for visible damage.
  • Prioritise the main content and load less urgent media when needed.
  • Review font files and weights so the design does not request assets it never uses.
  • Audit third-party scripts and embeds, keeping those that serve a clear purpose.

Vector artwork can help with logos: it remains sharp without relying on a small bitmap being enlarged. Large photographic case-study images need a different treatment. Optimisation should respect what the asset is meant to show.

Match the technical approach to the problem

A redesign does not automatically require microservices, serverless infrastructure or a headless CMS. Those choices introduce costs and operational responsibilities as well as potential benefits. Agree how content will be edited, what integrations are needed and who will maintain the site.

For a content-led studio website, a well-managed CMS may be appropriate. A product with authenticated workflows and changing data has different requirements. Ask the development team to explain the trade-offs using your actual constraints rather than an assumed future user count.

Use portfolio work as design evidence

The Finto independent concept demonstrates a banking website and interface direction. Its screens can support a discussion about hierarchy and presentation, but they are not evidence of measured production speed or capacity. Ask for separate technical measurements when evaluating performance claims.

Make launch checks measurable

Keep a record of representative pages before and after the changes. Use lab checks to investigate issues during development, and real-user data where available to understand the deployed experience. If traffic is too low for reliable field data, state that limitation rather than inventing a score or an outcome.

Our website design and development service connects content, interface design and implementation. Share your current website and the journeys you want to improve so the brief can start with a concrete problem.

Contrivea studio notes · Updated 17 October 2026. About the studio.