Skip to main content

Website Audit

Find out what is actually holding your website back.

A website audit gives you a clear view of the issues affecting credibility, conversion, accessibility, search visibility, performance and maintainability before you commit to a rebuild or improvement plan.

Audit focus

  • Customer journey
  • Accessibility
  • Performance
  • Search visibility
  • Technical maintainability

Useful for businesses that need technical clarity before spending money on the wrong work.

Typical situations

A good audit creates direction before implementation starts.

The goal is not to produce a long list of complaints. The goal is to separate the work that matters from the work that can wait.

  1. The website is not generating enough enquiries.

    The issue might be positioning, page structure, trust signals, performance or the enquiry path itself.

  2. A rebuild is being considered.

    Before replacing the website, it is worth knowing which problems require replacement and which can be improved directly.

  3. Search visibility is unclear.

    The site needs a practical review of metadata, structure, internal links and crawlable business context.

  4. The website feels difficult to maintain.

    Small content or design changes have become slow, fragile or dependent on technical workarounds.

  5. Performance has started to affect confidence.

    Slow pages, layout shift and heavy scripts can make a credible business feel less reliable.

  6. Accessibility needs review before launch.

    Keyboard access, focus states, forms, headings and contrast need to be checked before the site goes live.

  7. Internal teams disagree on the next step.

    An independent technical review can clarify what should be fixed first and why.

  8. The website has grown without a clear system.

    Pages, components and content may need a more maintainable structure before more work is added.

What the audit clarifies

The output should help you decide what to do next.

A useful audit connects findings to business impact, effort and sequencing rather than treating every issue as equally urgent.

  1. What is blocking trust.

    Issues that make the business harder to understand, verify or contact.

  2. What affects conversion.

    Page structure, CTA clarity, content hierarchy and enquiry flow issues that reduce action.

  3. What creates technical risk.

    Fragile implementation, duplicated patterns, heavy scripts or platform decisions that make future work harder.

  4. What should wait.

    Lower value work is separated from launch blockers so the improvement plan stays practical.

The audit looks across the whole website system.

Review areas

The review combines customer experience, technical implementation and content clarity so the recommendations do not become isolated fixes.

  • Conversion path

    Review how clearly visitors move from problem to service to enquiry.

    Hero clarity · CTA placement · Form path

  • Trust and proof

    Check whether the site gives enough credible evidence for qualified buyers.

    Case studies · Decision evidence · About content

  • Accessibility

    Review the parts that affect real use, including keyboard access, labels, headings and contrast.

    WCAG 2.2 AA · Forms · Navigation

  • Performance

    Identify the implementation choices that affect perceived speed and Core Web Vitals.

    Images · Client JavaScript · Layout stability

  • Search and AI readiness

    Review whether the business, services and relationships are clear to search engines and AI assistants.

    Metadata · Structured data · Internal links

  • Maintainability

    Look for duplication, fragile patterns and content structures that make future improvement harder.

    Components · Content model · Route structure

Audit process

The review turns uncertainty into a prioritised plan.

  1. Clarify

    Understand the business goal and current concern.

  2. Inspect

    Review the visible journey, content and implementation.

  3. Prioritise

    Separate launch blockers from improvements that can wait.

  4. Explain

    Document the reasoning behind each recommendation.

  5. Plan

    Turn findings into a practical next sequence.

Common questions

Is this only a technical audit?

No. The review connects technical issues to customer experience, trust, conversion and maintainability.

Will the audit tell us whether to rebuild?

Yes. A useful audit should make it clearer whether the right move is a rebuild, targeted improvement or a smaller first step.

Do you fix the issues afterwards?

Where appropriate, yes. The audit can lead into implementation, website growth work or fractional technical support.

Can you audit a site before launch?

Yes. Pre-launch audits are useful for catching broken journeys, missing metadata, accessibility issues and content gaps before visitors find them.

Practical writing that helps frame the same kinds of website and technical decisions.

  1. AI governance

    Automated decisions need more than a privacy policy update

    New Australian transparency rules cover more than fully automated AI. Businesses should map consequential decisions, personal information, vendors and human judgement before updating their privacy policy.

    Read the decision workflow guide
  2. AI governance

    AI meeting notes need a business policy

    Google Meet is switching on automatic AI notes by default for some business plans. Review consent, sharing, retention and human verification before the setting becomes normal practice.

    Read the meeting notes guide
  3. Website security

    AI threat signals need human review

    Cloudflare can now turn security reports into threat signals. Small businesses still need human review, local evidence and a safe rollback path.

    Read the threat signals guide

Make the next website decisionwith clearer evidence.

Share the website and the decision you are trying to make. I will help identify what needs attention first and what can safely wait.

I'll personally review every enquiry and get back to you.

The best technical decisions usually begin with a conversation.

Get in touch

Available for

  • Fractional Technical Partner
  • Technical leadership & advisory
  • Project delivery & implementation