How to Conduct a Usability Audit: A Step-by-Step Guide for Better User Experiences

A usability audit is a structured, evidence-based review of an existing website or digital product that identifies where users experience friction, confusion, or failure — and produces a prioritised set of recommendations to address those issues. It is not a redesign. It is a diagnostic. The seven-step process in this guide covers how to define the audit scope and success criteria, gather quantitative and qualitative user data, run a heuristic evaluation against Jakob Nielsen's 10 usability principles, audit accessibility compliance against WCAG 2.1 standards, evaluate mobile and performance metrics, prioritise issues by severity, and present findings in a format that stakeholders can act on. For Singapore businesses whose websites are generating traffic but not generating leads, a usability audit is typically the most direct and cost-effective intervention available before committing to a full redesign.

A website can look professionally designed, pass technical quality checks, and still fail its users systematically — through navigation that does not match how users think, CTAs placed where users do not look, forms that are too long to complete on mobile, or content hierarchies that bury the most important information below the fold. A usability audit surfaces these failures before they become expensive to fix.

This guide covers the full seven-step usability audit process. For the specific research methods that generate evidence during the audit — usability testing, heatmaps, card sorting, tree testing — see our guide on evaluative UX research methods. For the complete UX design process that the audit fits within, see our guide on the UX design process.

What Is a Usability Audit and Why Does It Matter?

A usability audit is a systematic evaluation of a website or digital product against established usability principles, user behaviour data, accessibility standards, and performance benchmarks. The output is a prioritised list of identified issues — each categorised by severity and accompanied by a specific, actionable improvement recommendation.

The distinction between a usability audit and a full UX audit is worth clarifying: a usability audit focuses on how well users can accomplish their goals — the functional dimension of user experience (navigation clarity, task completion, cognitive load, error recovery). A broader UX audit extends into branding, market positioning, content strategy, and emotional resonance. Both are valuable; a usability audit is typically the appropriate starting point for a business with an existing website that is underperforming, while a full UX audit is more appropriate when the strategic positioning itself needs reassessment.

Why conduct a usability audit?

Four commercially significant reasons apply to virtually every Singapore business with a website:

• Identify conversion blockers — cluttered interfaces, unclear navigation, confusing copy, and poorly placed CTAs all suppress conversion rates. A usability audit identifies these friction points with evidence from real user data rather than designer assumption
• Improve SEO performance — Google's ranking systems evaluate UX signals including Core Web Vitals, mobile usability, and engagement behaviour. A usability audit covers the same dimensions and produces improvements that compound into ranking benefits
• Stay competitive in Singapore's dense digital market — with over 112,000 active enterprises in Singapore and most having an online presence, UX quality is an increasingly significant commercial differentiator. An audit reveals where competitors are outperforming your digital experience
• Comply with accessibility standards — Singapore's Digital Government Blueprint encourages inclusive design, and IMDA guidelines mandate WCAG 2.1 AA compliance for public sector digital services. Private sector businesses in regulated industries (financial services, healthcare) increasingly face the same expectations from enterprise clients

The Seven-Step Usability Audit Process

The table below summarises each step, what it involves, and the tools that support it. The sections that follow cover each step in detail.

Step 1: Define Audit Goals and KPIs

The most common mistake in usability audits is beginning without a clear scope. An audit without defined goals produces findings that are hard to prioritise — because every observation carries equal weight when there is no framework for determining which issues matter most to the business outcome.

Before any data is gathered or any page is evaluated, align the audit with the business and user goals it is designed to serve. Host a scoping session with key stakeholders — typically the business owner, the marketing lead, and the web designer or developer — and work through three questions:

• What is the primary purpose of this website? — lead generation, e-commerce sales, investor relations, professional credibility? The answer determines which pages, which user flows, and which conversion actions the audit should prioritise
• What user actions indicate success? — contact form submissions, purchases, newsletter sign-ups, document downloads? These define the conversion events that should be traced through the user journey
• Which KPIs are most relevant to current performance? — bounce rate, average session duration, conversion rate, mobile vs desktop performance gap? These are the baseline metrics the audit's recommendations should measurably improve

The output of Step 1 is a scope document: a one-to-two page brief that defines the pages being audited, the user personas being evaluated, the devices to be tested (mobile first for Singapore), the KPIs that define success, and any constraints or compliance requirements that apply.

For Singapore-based SMEs where lead generation is the primary goal: ensure that every CTA in the audit scope is evaluated against a single standard — does this CTA clearly communicate what happens when you click it, and does it appear where users are most likely to be ready to act?

Step 2: Gather User Data and Feedback

A usability audit grounded in actual user behaviour data is fundamentally more reliable than one based on expert opinion alone. Before evaluating any pages, gather the quantitative and qualitative data that reveals what is already happening on the site.

Quantitative data sources:

• Google Analytics 4 — identify the pages with the highest bounce rates, the lowest average engagement time, and the most common exit points in conversion funnels. These are the pages the audit should prioritise
• Hotjar or Microsoft Clarity — review scroll maps to see how far users read, click maps to see where users are tapping (including rage clicks on non-interactive elements), and session recordings to observe individual user journeys through the site
• Google Search Console — identify the queries generating traffic to each page, and whether the CTR for those queries aligns with the position ranking. Low CTR at good positions suggests a meta title or description issue; high CTR with poor engagement suggests the landing page is not matching user intent

Qualitative data sources:

• User interviews or moderated usability testing sessions — five to eight participants completing realistic tasks on the site, observed and recorded. The most direct source of insight into why users behave as they do
• On-site polls — targeted single-question prompts placed at exit points: "What stopped you from completing this form?" or "What were you looking for that you did not find?" generate direct user feedback at low cost
• Customer support queries — recurring support requests often map directly to navigation failures or content gaps. "Where do I find your pricing?" appearing three times in the same month signals an information architecture problem worth investigating

Case Insight: How a Hotjar Audit Improved Sign-Up Rates by 30%

A Singapore SaaS client noticed a significant drop-off at the account sign-up page — traffic was arriving but registrations were not completing. A Hotjar scroll map revealed that fewer than 40% of users were scrolling past the hero section on the sign-up page, and a session recording review showed users repeatedly encountering a multi-field form that required company size, industry, and team headcount before they could proceed. The form was restructured to ask only for email and password at the initial sign-up step, with the additional fields deferred to the post-registration onboarding sequence. Sign-up completion rates improved by 30% within three weeks of the change — without any design changes to the surrounding page.

Step 3: Run a Heuristic Evaluation

A heuristic evaluation is an expert review of the site against established usability principles — a structured walk-through of each page in scope, documenting every deviation from best practice with a severity rating and a specific recommendation. The standard framework is Jakob Nielsen's 10 Usability Heuristics — the most widely used usability evaluation framework in the industry:

1. Visibility of system status — the site always keeps users informed about what is happening through appropriate feedback within reasonable time
2. Match between system and the real world — the site uses language and concepts familiar to the user, not internal jargon
3. User control and freedom — users can clearly undo or exit actions they did not intend
4. Consistency and standards — the site follows platform conventions and is internally consistent
5. Error prevention — the design prevents problems from occurring rather than relying on error messages
6. Recognition rather than recall — the interface minimises memory load by making objects, actions, and options visible
7. Flexibility and efficiency of use — the site accommodates both novice and expert users
8. Aesthetic and minimalist design — every visual element serves a purpose; irrelevant information competes with relevant information
9. Help users recognise, diagnose, and recover from errors — error messages are plain language, specific about the problem, and constructive about the solution
10. Help and documentation — if documentation is necessary, it is easy to find, task-focused, and concise

For each heuristic violation identified, document: the page and specific element affected, the heuristic violated, a severity rating (critical / major / minor), a description of the problem, and a specific recommendation. A shared Notion database or Google Sheet with these fields allows the audit team to collaborate, filter by severity, and generate the prioritised issue list that forms the audit's core deliverable.

Use Figma to annotate problem areas with numbered comments that reference the heuristic being violated. This produces a visual deliverable that stakeholders can navigate page by page — significantly more effective for communicating design issues than a text-only report.

Step 4: Audit Accessibility Compliance

Accessibility is both an ethical standard and a practical UX requirement. WCAG 2.1 Level AA is the internationally recognised baseline — and the standard Singapore's IMDA recommends for public sector digital services. For private sector businesses, meeting Level AA improves usability for all users, not just those with disabilities, and reduces legal and reputational risk in an increasingly compliance-aware market. For the full accessibility implementation guide, see our article on how to improve website accessibility.

The four WCAG principles and their most critical audit checks:

• Perceivable — all non-text content has text alternatives; colour is not the only means of conveying information; minimum 4.5:1 contrast ratio for body text (check with WebAIM Contrast Checker)
• Operable — all interactive elements are keyboard navigable; no content flashes more than 3 times per second; users have sufficient time to read and use content
• Understandable — the page language is correctly specified in HTML; error messages are specific and descriptive; labels are correctly associated with form fields
• Robust — HTML is valid and well-structured; ARIA attributes are used correctly where custom components require them; the site functions correctly with assistive technologies such as screen readers

Recommended tools: WAVE (browser extension — identifies accessibility errors on live pages visually), Axe (browser DevTools integration — more comprehensive, used by enterprise accessibility programmes), and Google Lighthouse (built into Chrome DevTools — provides an accessibility score alongside performance and SEO scores). For Singapore government-adjacent projects, also review against IMDA's Digital Service Standards, which build on WCAG 2.1 with additional Singapore-specific requirements.

Step 5: Evaluate Performance and Mobile Experience

Performance is a usability dimension, not just a technical one. A page that loads in five seconds on mobile is failing its users before they have seen a single word of content. In Singapore, where over 85% of users browse on mobile and the standard is nationwide 5G infrastructure, users expect fast experiences as the baseline — and a slow website is interpreted as a signal of low quality. For the full website speed optimisation guide, see that dedicated article.

Core Web Vitals are the primary performance audit framework — Google's quantified measurement of user experience that directly affects search rankings:

• Largest Contentful Paint (LCP) — target under 2.5 seconds. Measures how long the largest visible content element takes to load
• Interaction to Next Paint (INP) — target under 200 milliseconds. Measures responsiveness to user interactions throughout the session (replaced FID in March 2024)
• Cumulative Layout Shift (CLS) — target below 0.1. Measures visual stability during page load

Mobile-specific audit checks beyond Core Web Vitals: tap targets minimum 44×44px with adequate spacing between them, no horizontal scrolling required on 375px screens, font sizes minimum 16px for body text, primary CTA visible above the fold without scrolling, navigation accessible without deep menu hierarchies. Use Google PageSpeed Insights (mobile tab) for the scored assessment, and BrowserStack to evaluate the site on real device models used by Singapore's market (iPhone 15, Samsung Galaxy A-series, iPad).

Run PageSpeed Insights on your five highest-traffic pages separately — not just the homepage. Service pages and blog articles frequently have performance issues that the homepage does not, because they contain different asset types and embed codes.

Step 6: Prioritise and Categorise Issues

By Step 6, the audit has generated a substantial list of identified issues across heuristic evaluation, accessibility, performance, and mobile UX. The prioritisation step converts this raw list into an actionable improvement backlog — ordered by the combination of severity and implementation effort.

Categorise issues by type first:

• Navigation — menus, breadcrumbs, mobile navigation, link clarity
• Content — readability, scannability, content hierarchy, localisation
• Forms — field labels, form length, validation messages, mobile keyboard types
• Visual design — spacing, colour contrast, typographic hierarchy, responsiveness
• Technical — load speed, broken links, missing alt text, schema markup gaps
• Accessibility — WCAG violations by principle, severity, and affected user group

Then apply the MoSCoW prioritisation framework to each issue:

• Must have — critical issues causing conversion failure, accessibility violations at Level A, or performance issues producing bounce rates above benchmark
• Should have — significant issues reducing conversion or engagement, WCAG AA violations, or mobile UX failures on high-traffic pages
• Could have — improvements that would benefit UX but are not causing measurable failure — minor heuristic violations, low-priority content improvements
• Won't have (for now) — valid observations that are out of scope for the current audit cycle — strategic content changes, full navigation restructures that require broader agreement

Build the prioritised backlog in a project management tool — Airtable, Notion, or Linear all work well — with fields for issue description, category, MoSCoW rating, assigned owner, and implementation status. This transforms the audit from a report into an actionable UX improvement programme.

Step 7: Present Your Findings and Recommendations

The final step is presenting the audit findings to stakeholders in a format that drives action. The most common failure mode at this stage is a report so comprehensive that it overwhelms rather than enables — stakeholders see a 40-page document of issues and conclude that the website needs to be rebuilt rather than understanding that 80% of the impact can be achieved with 20% of the issues addressed.

The recommended deliverable format for a usability audit:

• Executive summary (1 page) — the three to five most critical findings, the estimated impact of addressing them, and the recommended next actions. Written for a business owner who will read only this page
• Annotated Figma mockups — screenshots of each audited page with numbered comments referencing the issue tracker. Communicates design problems visually in a way text descriptions cannot
• Issue tracker with severity levels — the full prioritised backlog with MoSCoW ratings, category labels, and specific recommendations. This is the working document the development team uses to implement changes
• Suggested design or copy improvements — for the highest-priority issues, provide specific before/after recommendations rather than general guidance. "Replace 'Submit' with 'Get My Free Consultation'" is actionable; "improve CTA copy" is not

For presenting to non-technical Singapore stakeholders — business owners, finance directors, operations managers — use Loom to record a narrated walkthrough of the annotated mockups. A five-minute video walkthrough of the top ten findings communicates the same information as a forty-page report, in a format that most Singapore business owners will actually engage with before their next meeting.

Conducting a Usability Audit on a Webflow Site

Webflow's architecture has specific characteristics that affect both how usability issues are likely to manifest and how they are most efficiently addressed. As a Webflow-first agency, we have conducted usability audits on dozens of Webflow sites and found consistent patterns worth knowing.

Webflow-specific audit considerations:

• CMS collection pages — blog articles and case study pages generated from CMS collections often inherit metadata from the collection template rather than having page-specific settings. Audit a sample of CMS pages specifically for missing or duplicate meta titles and descriptions
• Interaction and animation performance — Webflow's animation tools are powerful, but animation-heavy pages frequently produce INP issues on mid-range mobile devices. Test interactions on an Android mid-range device specifically — not just flagship hardware
• Form embed compatibility — third-party forms embedded in Webflow (HubSpot, Typeform, Calendly) occasionally produce layout issues on mobile viewports. Every embedded form in the audit scope should be tested on mobile
• Responsive breakpoint completeness — Webflow allows independent styling at each breakpoint (desktop, tablet, mobile landscape, mobile portrait). Audit all four breakpoints, not just desktop and mobile portrait — tablet and mobile landscape are frequently overlooked and produce visible layout issues on iPads and landscape phone orientations

Singapore-Specific Audit Considerations

Beyond the standard seven-step process, three Singapore-specific dimensions should be incorporated into every usability audit for a Singapore-facing website.

PDPA compliance in forms and data collection

Singapore's Personal Data Protection Act (PDPA) requires that websites collecting personal data include a clear consent mechanism, a link to the privacy policy, and specific disclosure of how data will be used. Usability audits should include a PDPA compliance check on every form in scope: is the consent checkbox visible and properly labelled? Is the privacy policy link present and linking to a current policy? Are data purposes clearly stated? These are both legal requirements and UX requirements — users who cannot find a clear privacy policy or consent mechanism on a Singapore form will frequently abandon rather than complete.

Multilingual content evaluation

If the website serves both English and Mandarin-speaking audiences — common for consumer-facing Singapore businesses in healthcare, F&B, professional services, and retail — evaluate each language version of the site against the same audit criteria. Heuristic violations that exist only in the Mandarin version (inconsistent navigation labels, missing alt text on localised images) are easily missed in an English-only audit. If the site serves Malay or Tamil audiences, those versions warrant evaluation too.

MAS-regulated and healthcare content

For Singapore businesses in MAS-regulated financial services or MOH-regulated healthcare, the audit scope should include a review of the regulatory content presentation: are required disclaimers visible and clearly readable? Are product risk disclosures placed at the appropriate points in the user journey? Is regulatory copy formatted in a way that users can actually read and process it, rather than being displayed in 8px grey text in the footer? These are usability requirements within a compliance constraint — the goal is to make regulatory content genuinely communicative rather than technically present.

Frequently Asked Questions

How often should I conduct a usability audit?

At minimum: once every six months as a scheduled review, and immediately after any major website update or unexplained traffic drop or conversion rate decline. The six-month cadence ensures the audit catches issues introduced by content updates, plugin changes, browser updates, or Google algorithm changes that affect mobile usability. More frequent audits — quarterly — are appropriate for high-traffic e-commerce sites, regulated financial services platforms, or any site where conversion rate directly drives revenue. After major events such as a redesign, a CMS migration, or a platform change, a full audit should be conducted within four to six weeks of the change going live.

Can I audit a site that is not yet live?

Yes — and it is often more cost-effective to audit at prototype stage than post-launch. High-fidelity Figma mockups can be evaluated against all seven heuristics, tested for click behaviour using Maze or UsabilityHub, and reviewed for accessibility using design-level contrast and structure checks. The limitation is that performance audits (Core Web Vitals) and real-user behaviour data (heatmaps, session recordings) are only available after launch. A pre-launch audit catches structural and design issues; a post-launch audit catches performance and real-user behaviour issues. Both are valuable, and the most thorough audit programmes include both.

What is the difference between a usability audit and a UX audit?

A usability audit focuses on the functional dimension of user experience: can users accomplish their goals efficiently, without confusion or frustration? It evaluates navigation, task completion, cognitive load, error recovery, and accessibility. A UX audit is broader: it encompasses everything a usability audit covers, plus branding, emotional resonance, market positioning, content strategy, and business alignment. A usability audit is the appropriate starting point for a business with an existing website that is underperforming on conversion or engagement metrics. A full UX audit is more appropriate when the strategic positioning or the overall brand experience needs reassessment. For the evaluative research methods that underpin both, see our guide on evaluative UX research methods.

Should I use AI tools for usability audits?

AI tools can accelerate specific components of a usability audit — generating initial heuristic checklists, summarising qualitative feedback from user interview transcripts, identifying patterns in session recording observations, or suggesting copy improvements for flagged CTAs. What AI cannot replicate is the contextual judgement that distinguishes a critical usability issue from a minor inconsistency, the understanding of the specific business objectives that determines which issues matter most, and the Singapore market context that shapes what users in this specific environment expect. Use AI tools to increase the efficiency of the audit process; use human expertise to make the judgements that determine what to prioritise and what to recommend.

How much does a professional usability audit cost in Singapore?

For a Singapore SME website of six to fifteen pages, a professional usability audit by an experienced UX designer typically costs S$1,500 to S$4,000 depending on the scope (number of pages, number of user personas, whether user research sessions are included) and the depth of the deliverable (heuristic evaluation only versus full seven-step audit with annotated mockups, issue tracker, and presentation). Audits that include moderated usability testing sessions with recruited participants cost more — participant recruitment in Singapore typically adds S$800 to S$2,000 to the total engagement cost. For organisations that need to audit a large site or require formal WCAG compliance documentation, costs are higher. Our UX research service covers the full range from lightweight heuristic reviews to comprehensive usability audits with user testing.

What is the ROI of a usability audit for a Singapore business?

The ROI is most directly expressed through conversion rate improvement. A Singapore professional services firm receiving 1,000 monthly website visitors at a 1.5% conversion rate generates 15 leads per month. A usability audit that identifies and fixes the friction points suppressing conversion — producing a 2.5% conversion rate — generates 25 leads per month. At an average client value of S$5,000, that improvement is worth S$50,000 per month in additional pipeline. The audit investment that produced it was S$2,000–S$4,000. Beyond conversion rate, usability audits improve the UX signals that influence search rankings — reduced bounce rate, increased dwell time, deeper session engagement — which produce compounding SEO benefits over the months following implementation.

What tools do I need to conduct a usability audit myself?

The minimum viable toolkit for a self-conducted usability audit: Google Analytics 4 (free — quantitative behaviour data), Microsoft Clarity (free — heatmaps and session recordings), Google PageSpeed Insights (free — Core Web Vitals scoring), WAVE browser extension (free — accessibility errors), and Chrome DevTools Lighthouse (free — integrated performance, SEO, and accessibility scoring). For heuristic evaluation, Jakob Nielsen's 10 usability heuristics are documented free at nngroup.com. For user testing: Maze has a free plan that supports limited tests. Together these tools cover the full seven-step audit at near-zero cost — the investment is time and the UX knowledge required to interpret the findings correctly.

Conclusion

A usability audit is not a luxury reserved for large organisations with dedicated UX teams — it is a structured, evidence-based process that any Singapore business with a website can use to identify why users are not converting and what to change. The seven steps in this guide are deliberate in their sequence: define before gathering, gather before evaluating, evaluate before prioritising, and prioritise before presenting. Each step builds on the last, and skipping any step produces either incomplete findings or recommendations that cannot be acted on.

For most Singapore businesses, the highest-return first step is installing Microsoft Clarity (free) today and reviewing the mobile heatmap data after two weeks. That data will tell you whether the audit needs to begin with a conversion funnel problem, a navigation problem, a performance problem, or a content hierarchy problem — and will make every subsequent step of the audit more precisely targeted.

At ALF Design Group, our UX research service includes structured usability audits for Webflow websites and broader digital products. If you want an expert assessment of where your site is losing users and what improvements would produce the most commercial impact, get in touch.

{{build-better-experience="/directory"}}