Website designYour questions, answered.

A good website helps its intended visitors understand the offer and complete a useful action. Clear structure, accessible content, trustworthy evidence and reliable performance matter alongside appearance. A polished design that hides essential information or makes buying difficult is not serving the business well.

Next step: Identify the three main visitor tasks and check whether each is straightforward on mobile.

Design defines the visual hierarchy, interaction and experience; development implements how the site works. The disciplines overlap but solve different problems. A complete project needs both a considered customer journey and reliable implementation, with content and testing supporting the result.

Next step: Ask who owns design, implementation, content and testing in the project scope.

Improve an existing site when its structure and technology still support the business. A redesign is more appropriate when fundamental navigation, content, accessibility or platform constraints make incremental work inefficient. Diagnose the issue first: replacing a site without understanding poor performance can reproduce the same problems.

Next step: Audit key journeys, technical limitations and search performance before deciding.

A homepage should make the business, audience and offer clear, then direct visitors towards relevant services or products. Add credible evidence and useful next steps rather than trying to fit every detail above the fold. Returning customers may need a different route from first-time visitors.

Next step: Test whether someone unfamiliar with the business can explain the offer after viewing the page.

Group content using language visitors recognise and make important destinations easy to reach. Consistent labels, visible page headings and sensible mobile menus help people understand where they are. A large menu is not necessarily useful if items overlap or hide the main tasks.

Next step: Ask several users to find one service, one proof point and the contact option.

A call to action invites a clear next step, such as enquiring, booking or buying. Its wording should match what happens afterwards. Too many competing actions can weaken a page; vague promises can create uncertainty. The right action depends on visitor intent and how much information they already have.

Next step: Give each key page one primary action and explain what the visitor can expect next.

Include enough information to help the buyer assess fit, value, process and risk. There is no universal word count that improves conversion or search visibility. Use headings and concise explanations, with deeper detail where questions justify it rather than filling space for its own sake.

Next step: Collect the questions your sales team answers repeatedly and address the relevant ones on the page.

People on smaller screens still need readable text, usable controls and complete information. Mobile design is not simply a smaller desktop page: navigation, forms and media must suit limited space and touch interaction. Device-specific problems can undermine otherwise strong campaigns.

Next step: Complete your most important customer journey on a real phone without zooming.

Responsive design adapts layout to available screen space rather than assuming one fixed device size. Content should remain readable and controls usable across widths. Rearranging elements is only part of the work; testing long headings, forms, tables and dynamic states exposes issues that a static mock-up misses.

Next step: Check key pages at narrow, medium and wide screen sizes with real content.

Accessibility helps people with disabilities perceive, understand and operate a website. It includes keyboard use, meaningful labels, text alternatives, contrast and predictable interactions. An automated checker can find some problems but cannot establish complete accessibility. Legal obligations depend on context and may require professional advice.

Next step: Test the enquiry journey with a keyboard and review it against relevant WCAG guidance.

Choose a small system that expresses the brand while keeping text and controls readable. Check contrast and legibility rather than selecting solely for appearance. Consistent type sizes and colour roles help visitors distinguish headings, links and secondary information without relying on colour alone.

Next step: Test your main text, links and button states for contrast and readability.

Use motion to clarify a change, draw attention appropriately or convey the brand without obstructing tasks. Constant movement, delayed content or heavy effects can distract visitors and affect performance. Respect reduced-motion preferences and ensure essential information is available without waiting for an animation.

Next step: Remove any animation that delays reading or prevents completing the main action.

Images should help people inspect the product, service, place or team, not merely fill a layout. Use accurate, appropriately sized media with useful alternatives where required. Decorative images do not need descriptive text, while meaningful images often do. Large downloads can make an attractive page frustrating.

Next step: Replace one generic image with specific evidence and optimise its dimensions for the layout.

Ask for information needed to respond usefully, not everything that might be interesting later. Clearly label required fields, explain relevant data handling and show genuine success or error states. More fields may reduce submissions, but fewer fields can also create poor-quality leads; test the trade-off.

Next step: Remove unnecessary fields and submit a test enquiry to confirm delivery and feedback.

Explain the customer's problem, the offer and the evidence in clear language. Specific detail is usually more useful than broad claims. Keep headings descriptive and make next steps easy to find. Copy should reflect what the business actually delivers rather than promises chosen only to sound persuasive.

Next step: Rewrite one page around customer questions, proof and a clear next step.

A wireframe outlines page structure and information hierarchy before detailed visual design. It can help agree content and journeys without debating colours prematurely. It is not a finished specification: interaction, accessibility and real content still need to be considered during design and development.

Next step: Review the main page wireframes using actual visitor tasks rather than aesthetic preference.

Give representative users realistic tasks and observe where they hesitate or misunderstand. Avoid explaining the interface while they work, which hides problems. A small qualitative test can reveal friction, but it is not a statistical proof of conversion performance or a replacement for broader evidence.

Next step: Watch three prospective customers find information and complete an enquiry without assistance.

Genuine, relevant testimonials can address buyer uncertainty, especially when they describe a specific experience. Obtain appropriate permission and avoid editing feedback into a stronger claim than the customer made. Testimonials support trust but cannot substitute for clear service information or reliable delivery.

Next step: Choose a verified testimonial that addresses a common concern and retain its permission record.

Inventory existing pages, identify visitor needs and assign content ownership. Draft essential headings and messages early so design reflects real information rather than placeholder text. Plan redirects for replaced URLs and decide which old content remains useful before deleting it.

Next step: Create a page list with purpose, primary action, content owner and migration decision.

Assess the design against visitor tasks, brand accuracy, accessibility and real content across devices. Check error states and interaction, not only screenshots. Approval should identify what is final and what still needs implementation or testing; a visual sign-off is not proof that the live site works.

Next step: Review the main journeys on mobile and desktop and keep a written list of unresolved issues.

Include useful contact routes, important navigation and relevant business and policy information. Keep it readable rather than repeating every menu item. A footer should help visitors finish a task, not compensate for unclear page structure.

Next step: Check the footer against common visitor questions and required business disclosures.

Identify tasks shared across audiences and information that genuinely differs. Use clear routes where needed without making everyone choose a category before understanding the offer. Test the labels with real visitors rather than internal department names.

Next step: Map your three main audiences to their most important website tasks.

Information architecture organises content and relationships so visitors can find and understand it. It includes categories, labels and navigation. Attractive layouts cannot fix confusing grouping, especially when services overlap or use terminology customers do not recognise.

Next step: Group your pages by visitor needs before choosing menu labels.

Start with customer tasks, sales questions and useful evidence, then group related information. Create a separate page when it serves a distinct need. Avoid adding pages simply to increase search volume or repeat the same service wording.

Next step: Create a page inventory with one purpose and primary audience per page.

Search should return relevant results, tolerate common wording and explain empty results clearly. It is particularly useful for larger libraries or catalogues. A search box is not a substitute for clear navigation or properly maintained content.

Next step: Test five real customer queries and review misleading or missing results.

Use descriptive headings, a clear reading order and navigation to important sections where useful. Long pages need not be cut arbitrarily if the detail serves readers. Avoid effects that hide content or force people through unnecessary scroll interactions.

Next step: Check whether a visitor can quickly locate pricing, proof and the next step.

Tabs suit closely related views when hiding inactive content does not obstruct comparison or essential tasks. Provide understandable labels and accessible keyboard behaviour. Content behind tabs still needs to remain usable on small screens and with assistive technology.

Next step: Test switching tabs by keyboard and check whether critical information is overlooked.

Accordions can reduce visual length for optional detail, such as supporting questions. Keep essential buying information visible and label sections clearly. They should open reliably by keyboard and touch without shifting controls unpredictably or trapping the reader.

Next step: Review which information must remain visible before placing it in an accordion.

Make included features, restrictions and total costs comparable across options. Avoid visual emphasis that obscures meaningful differences. On mobile, preserve the ability to understand each option without requiring visitors to remember information from distant columns.

Next step: Ask a prospect to compare two options and explain the differences.

Explain the starting problem, work delivered and verified outcome with relevant dates and scope. Separate measured results from client opinion and avoid implying one outcome is typical. Obtain permission for confidential details, screenshots and testimonials.

Next step: Build one case study using documented work and approved evidence.

Accurate team photographs can make a service feel tangible when people matter to the buying decision. Obtain permission and keep them current. Use suitable sizes and meaningful descriptions where needed; generic stock portraits should not be presented as staff.

Next step: Review photo permissions and replace outdated team details.

Start with the customer problem and the practical result, then reveal process and technical detail in layers. Use a relevant example to reduce ambiguity. Oversimplification becomes misleading when limitations, responsibilities or eligibility are essential to understanding the offer.

Next step: Test the explanation with someone unfamiliar with the service.

Confirm only a submission that was successfully received and explain the realistic next step. Provide a reference or alternative contact route where useful. Do not promise a response time the team cannot deliver or display success after a failed request.

Next step: Submit a real test enquiry and verify receipt before checking the confirmation.

Explain which field needs attention and how to correct it, preserving information already entered. Use visible labels and accessible error association rather than colour alone. Validation should prevent avoidable mistakes without rejecting valid names or unnecessarily narrow telephone formats.

Next step: Test missing fields, invalid entries and recovery by keyboard.

Tell the visitor the request was not confirmed, retain their entered information where safe and offer a retry or alternative route. Avoid exposing private error details. Repeated clicks should not create accidental duplicate enquiries.

Next step: Test a failed request and confirm the visitor can recover safely.

A 404 page explains that the requested page cannot be found and offers relevant navigation or search. Keep it consistent with the site. A friendly design should still return the correct missing-page status rather than disguising every error as a successful page.

Next step: Test a nonexistent URL and check its navigation and response status.

Provide understandable choices and ensure the actual tracking behaviour matches them. Consent requirements depend on the technologies and current rules. A branded banner alone does not establish compliance or prevent tags from running before the relevant choice.

Next step: Review the choices and test network behaviour after accepting and declining.

Describe what the download contains, its format and any meaningful size or accessibility limitations. Make the resource usable and current. If collecting details, explain the purpose rather than implying that downloading automatically subscribes someone to unrelated marketing.

Next step: Test the download and review its accessibility and information-collection wording.

Gating may help identify interest but can also discourage readers and limit discovery. Keep a meaningful public explanation so visitors can assess value. Match any required details to the resource and clarify subsequent contact and marketing choices.

Next step: Compare qualified enquiries and resource use with and without a gate.

A chatbot is useful when it reliably answers common questions or routes visitors to support. It needs accurate information, escalation and privacy controls. A confident but incorrect answer can create more friction than a clear human contact route.

Next step: Pilot the bot against common questions and define when it hands over.

Use lightweight, relevant footage that does not impair reading or delay the main content. Provide a static fallback and consider motion preferences. Essential information should not depend on hearing audio or waiting for a video sequence to finish.

Next step: Check loading, contrast and reduced-motion behaviour on a phone.

Extra font files and styles increase downloads and can delay text rendering. Load only the styles needed and use reliable fallbacks. A brand font can be retained while reducing unnecessary weights, oversized files or repeated font requests.

Next step: Audit loaded font files and remove unused styles.

Reserve space using suitable dimensions or aspect ratios before images load. Serve appropriately sized files and avoid changing container sizes unexpectedly. Image compression alone cannot prevent shifts caused by missing dimensions or late-inserted content.

Next step: Check page movement during a slow initial load.

Core Web Vitals measure loading, responsiveness and visual stability using LCP, INP and CLS. They describe important aspects of user experience, not every aspect of website quality. Assess real-user data where available alongside controlled diagnostic tests.

Next step: Compare field data with test results for your main landing pages.

Test conditions, network assumptions, page changes and third-party services can affect diagnostic scores. Real-user reports cover a different population and period. Compare repeatable trends and the underlying problems rather than treating one score as an exact customer experience.

Next step: Run comparable tests and prioritise recurring issues affecting real journeys.

Maps, booking widgets and social embeds can add downloads, tracking and accessibility constraints. Load only what supports a visitor task and provide alternatives when useful. The host website remains responsible for checking how the complete journey behaves.

Next step: Audit embeds for performance, privacy and keyboard usability.

Decide which audiences and languages justify maintained content and how visitors switch between versions. Translation needs review for meaning, terminology and local expectations. Search annotations and URL structure should match the actual language versions rather than unsupported regional claims.

Next step: Assign translation owners and map the pages required in each language.

A design system defines reusable visual and interaction patterns so pages remain consistent as the site grows. It should include usable states and accessibility expectations. Documentation alone is insufficient if new work repeatedly bypasses the agreed patterns.

Next step: Define shared typography, controls and error states for your main journeys.

Content should remain readable and operable when visitors enlarge it. Flexible layouts and sensible wrapping help avoid clipped text and hidden controls. Test important tasks rather than assuming that a desktop screenshot demonstrates accessibility.

Next step: Complete an enquiry with browser zoom increased and check for lost controls.

A visible focus indicator helps keyboard users identify the active control. It must remain clear against surrounding colours and not be removed merely for appearance. Focus order should follow a meaningful journey and avoid hidden or inaccessible elements.

Next step: Navigate the main menu and form without using a mouse.

Use wording that describes the destination or action in its context. Repeated vague labels can make scanning and assistive navigation harder. An enquiry link, download and external resource should not all suggest the same outcome.

Next step: Replace unclear links with labels that match what happens next.

Keep headings and relationships understandable and provide controlled horizontal scrolling where needed. Some data is better presented as a list, but conversion should not remove comparison context. Never shrink text until it becomes unreadable just to fit every column.

Next step: Test your longest table with real data on a narrow screen.

Make destinations readable, touch controls stable and opening and closing predictable. Allow the menu itself to scroll when necessary and preserve access to the close control. Effects and promotional content should not obstruct navigation.

Next step: Test the menu with long content and a small phone viewport.

Sticky controls can keep useful actions available, but they should not obscure content, form fields or other controls. Consider screen height as well as width. Use them selectively where access matters rather than keeping every page element fixed.

Next step: Check the control while scrolling and entering information on a phone.

Place relevant evidence near the decision it supports, such as genuine reviews beside an enquiry route. Avoid repeating credentials so heavily that they compete with the offer. Each claim should be accurate, current and understandable to the intended customer.

Next step: Remove unsupported badges and retain the strongest relevant evidence.

Choose contact options that match visitor urgency and staff availability. A booking route helps arrange planned conversations; a number can suit immediate help. Clearly explain what each action does and keep contact routes consistent across devices.

Next step: Review contact preferences and test each route through to a response.

Group work by relevant needs or capabilities and explain the contribution made on each project. Attractive screenshots should be supported by context and permission. Do not claim ownership of work or results that belong to another supplier.

Next step: Add your role, scope and approved evidence to each portfolio entry.

Observe task completion, misunderstandings and recovery from errors, not just whether participants like the design. Qualitative findings identify problems but do not automatically quantify conversion gains. Use realistic tasks and avoid coaching participants through confusing steps.

Next step: Define three customer tasks and record where users need help.

Schedule checks for key journeys, broken links, outdated facts and changes introduced by services or editors. Keep content ownership clear. A launch checklist cannot protect a site indefinitely when forms, integrations and business information continue to change.

Next step: Assign owners and a recurring check for the most valuable customer journeys.

Fix broken or inaccessible core tasks first, then address high-impact friction using evidence. Visual refinements matter, but should not displace failures that prevent enquiry or purchase. Track the change and outcome so future decisions build on learning.

Next step: Create a short issue list ranked by customer impact and confidence.