bluntlyput

Before you replace
your website.

Review the journey a real customer needs to complete. Keep what works, fix the friction and turn the findings into a specific redesign brief.

By Bluntly Put · Reviewed November 7, 2026

1. Give the site one real task.

Choose a service and try to request a quote, make a booking or find the information needed to call. Start on the homepage, then repeat from a service page. Write down each point where you have to guess. A decorative homepage is not enough if the useful next step is hidden.

2. Repeat it on your phone.

Check text size, button spacing, menus and form fields. Look for sideways scrolling and content covered by sticky controls. Use a real phone as well as a resized browser. A page can fit the screen while still being awkward to use.

3. Read it as a new customer.

Can you tell what the business sells, who it helps and what to do next? Replace vague claims with the actual service, relevant work and clear contact details. Remove outdated prices, broken links and information that conflicts across pages.

4. Follow the inquiry into the business.

With permission, send a labeled test inquiry and verify who receives it, where it is recorded and what the customer sees. A success message on the website does not prove an email arrived or a booking was saved. Use a test environment for payments and other consequential actions.

5. Measure before promising an improvement.

Use PageSpeed Insights to investigate loading and stability. Its lab results are diagnostic, not proof of lost sales or future rankings. If field data is available, review that too. In Search Console, note the pages and queries already bringing visitors before changing URLs.

6. Protect what is already working.

List the pages worth keeping, important URLs, existing content, form destinations and account owners. Agree redirects for replaced pages, preserve necessary data and decide who will maintain the new site.

For each issue, record: the page, the task attempted, what happened, the desired behavior and how you will verify the fix. That becomes a much more useful brief than “make it modern.”

A focused fix or a full rebuild?

If the structure is sound, a targeted improvement may be enough. If the content, layout and integrations all prevent customers from completing the journey, a rebuild may be more practical. Compare the scope and ongoing costs before deciding.