Page clarity
Revise headings, page order and calls to action so each page answers its buyer question early and leads to one useful next step.
Website redesign that improves the site you already have.
Improve page clarity, navigation, forms, mobile journeys and performance on your current site. A rebuild or migration is not the default.
Existing websites / Mobile journeys / Before-and-after checks
The scope
Fix what is in the way.
Keep what works.
Start with the problems visitors meet on the current site. Change the platform only when it blocks the fix.
See the before-and-after checksA redesign does not have to mean a new website. Clearer pages, simpler mobile navigation, accessible controls, working forms and lighter pages can be scoped on your current stack. We confirm during discovery whether we can work on that stack and what access it needs.
A business whose site gets visitors but makes the offer, navigation or enquiry step hard to understand or use. If the platform itself blocks the work, a migration is a separate decision with its own case.
Mobile navigation
Simplify menus, tap targets and page order for phone screens. Check that priority pages are easy to reach and readable without zooming.
Accessibility
Review headings, contrast, labels, keyboard access and focus states on priority pages. Fix what the agreed scope covers and record what remains.
Forms and enquiries
Remove unnecessary fields, check validation and confirm with a labelled test that each submission reaches the right inbox or CRM record.
Performance
Find heavy images, scripts and layout shifts on important mobile pages. Measure before and after under the same test conditions.
Design refresh
Update typography, spacing and components where the current design gets in the way. The brand stays recognisable unless a change is agreed.
Stay or move
What can change
without a migration.
Decide what can be fixed in place first. Treat a platform change as a separate decision with its own case.
When a migration makes senseWork that can stay in place
Subject to access and how the site is built.
- Copy, headings and page order
- Navigation labels and menu structure
- Form fields, validation and destinations
- Image sizes, formats and loading
- Accessibility fixes to templates and components
- Internal links and calls to action
Signs a migration is worth discussing
Each one needs evidence before it justifies a move.
- The platform cannot produce the page structure you need
- Editing is so restricted that pages fall out of date
- A required integration cannot be connected reliably
- Performance problems come from the platform, not the content
- Working around the platform costs more each time
Before and after
Record the start.
Compare like with like.
Every agreed change gets a recorded starting point and a comparison made under the same conditions.
Website OptimiserPage clarity
Before the change: Note the page's main question, where it is answered and where the next step sits
After the change: Review the revised page against the same questions with your team
Mobile navigation
Before the change: Record the taps needed to reach priority pages on a phone-sized screen
After the change: Repeat the same journeys on the same screen sizes
Accessibility
Before the change: Log issues found in headings, contrast, labels, keyboard access and focus
After the change: Recheck each logged issue and record what is fixed or still open
Forms
Before the change: Submit a labelled test and record where it arrives, or where it fails
After the change: Repeat the test and confirm the agreed destination receives it
Performance
Before the change: Measure priority pages with a recorded device, connection and page state
After the change: Measure again under the same conditions. Report lab results separately from real-user Core Web Vitals
Enquiries
Before the change: Note the baseline for valid enquiries where measurement exists
After the change: Compare consistent periods. A redesign by itself proves no conversion uplift
Deliverables and inputs
What you receive.
What we need from you.
Both lists are agreed before changes start, including what stays out of scope.
How delivery worksWhat you receive
- A prioritised list of issues on your key pages
- Revised copy, layouts and components within the agreed scope
- Mobile navigation and form fixes, tested on phone-sized screens
- An accessibility issue log with fixed and open items
- Before-and-after records for each agreed check
- A recommendation on whether a migration is worth considering, and why
What we need from you
- Access to the website, its CMS or code, and hosting where changes need it
- Your priority pages and the questions customers ask most
- Analytics or form data, if it exists
- Someone who can approve copy and design changes
- Brand assets and any accessibility requirements that apply
The process
Six stages.
Measured both ways.
Each stage ends with something you can review, from the first walkthrough to the final comparison.
How engagements workReview the current site
Walk priority journeys on phone and desktop. Note where visitors may get stuck and confirm we can work on the current stack.
Record the baseline
Capture the starting point for each agreed check, including the device, screen size and test conditions.
Prioritise the fixes
Agree which issues to fix first, based on business priority and effort. Keep the rest on a recorded list.
Design and change
Revise copy, layouts, navigation, forms and components. Review the changes on staging where the platform allows it.
Compare and report
Repeat each check under the same conditions and report what changed, what did not and what needs more time.
Decide the next step
Use the results to choose further improvements, ongoing optimisation or, if the platform blocks the work, a migration.
An example
Check the measurement
before the design.
When form starts are recorded but submissions are not, first test the event path and the form itself. A design change cannot fix missing measurement on its own.
Scope and availability
No traffic, conversion or performance score is promised. The platforms we can work on, and the access needed, are confirmed during discovery. Website Optimiser audits are Live in the Ciny platform, run by the Ciny team on demand. Automatic changes to a live site and staged page release are planned. A redesign project is a separate, scoped engagement.
Check platform capabilitiesDo we need a new website?
Not necessarily. The first review should establish what to retain, what to improve and whether a migration is necessary.
Can you work on our current platform?
We confirm this during discovery, based on the platform, how the site is built and the access available. If we cannot work on it well, we say so before any work is scoped.
Will a redesign increase our traffic or enquiries?
No outcome is guaranteed. We record a baseline and compare consistent periods afterwards. A redesign by itself proves no conversion uplift.
Do you promise a performance score?
No. We measure priority pages before and after under the same conditions. A lab score is not a real-user guarantee, and field data is reported separately where it is available.
Is accessibility included?
An accessibility review of priority pages can be part of the scope. It records issues and fixes them within the agreed work. It is not a compliance certificate.
Tell us what is not
working yet.
Share the site, the pages that matter and where visitors struggle. We agree the scope and the checks before any work starts.