A UI audit checks the visual consistency, clarity and interaction quality of an interface. Start with this UI audit checklist to find friction quickly. Then complete the copy/paste UI audit template and the simple report outline to write a clean report. Keep the sections that you need and delete the rest. If you need a review of the whole journey, use the UX audit template instead.
What is a UI audit?
A UI audit is a structured review of a product interface that finds the visual inconsistencies, unclear interactions and layout issues that cause friction. It also checks how the interface looks and behaves, and how easily users can complete tasks.
UI audit vs UX audit
A UI audit focuses on layout, typography, color, components and visual consistency. A UX audit focuses on the broader user journey, usability and outcomes. The two audits overlap, but a UI audit is narrower and more visual.
When to run a UI audit
Run a UI audit when you plan a redesign, or when visual inconsistencies grow across pages. It is also useful when conversion or engagement drops with no clear technical cause, and when you need a baseline before you change the interface.
Core areas to review
A strong UI audit covers the visual design and layout, the clarity of the navigation, content and CTAs, and the interaction states and feedback. It also checks mobile responsiveness, performance and speed, accessibility basics and behavior data such as heatmaps and drop-offs.
UI audit checklist
Use this UI audit checklist to keep reviews consistent.
Goals and scope
- Define the audit goal (conversion, clarity, brand alignment)
- Identify key pages and flows to review
- Pick the success metrics you will track
Layout and hierarchy
- Is the layout easy to scan?
- Are primary actions in expected positions?
- Is spacing consistent and purposeful?
- Are related elements grouped clearly?
Color and contrast
- Are colors consistent with the brand palette?
- Is text contrast readable?
- Do colors communicate state and priority?
- Is meaning clear without color alone?
Typography and readability
- Are fonts legible at all sizes?
- Is hierarchy clear across headings and body text?
- Are line length and spacing comfortable?
- Are styles consistent across pages?
Components and consistency
- Are buttons, forms, and icons consistent?
- Do components follow a clear pattern?
- Are interactive elements easy to identify?
- Are states consistent (hover, focus, disabled)?
Interaction feedback
- Do inputs show success, error, and loading states?
- Are error messages clear and actionable?
- Is progress visible on multi-step flows?
Responsiveness and accessibility
- Does the UI work on mobile and desktop?
- Are touch targets large enough?
- Can users navigate with keyboard and screen reader?
- Is semantic structure used for headings and lists?
Behavior and performance
- Review heatmaps and session recordings
- Identify drop-off points and confusion spots
- Check page speed and heavy assets
UI audit template (copy/paste)
Audit brief
| Section | Details |
|---|---|
| Goal | What outcome are we improving? |
| Scope | Pages, flows, devices |
| Metrics | Ex: CTR, drop-off rate, activation |
| Users | Primary personas or segments |
| Tools | Analytics, heatmaps, surveys |
Page inventory
| Page | Goal | Issues found | Priority |
|---|---|---|---|
| Pricing | Increase demo requests | CTA blends in | High |
Component inventory
| Component | Usage | Issues | Recommendation |
|---|---|---|---|
| Primary button | 12 screens | 4 variations | Standardize style |
Findings log
| Area | Issue | Evidence | Severity | Recommendation |
|---|---|---|---|---|
| Checkout | Error state is unclear | Screenshot + drop-off | High | Add inline error copy |
UI audit report outline
- Summary (top 5 findings)
- Goals and scope
- Methods and data sources
- Findings by severity
- Recommendations and examples
- Next steps and owners
Example (short)
Goal: Improve trial signup completion.
Scope: Signup and onboarding screens (desktop + mobile).
Top findings:
- Primary CTA color blends into the background
- Form labels are inconsistent across steps
- Error messages appear after users submit
Next steps:
- Increase CTA contrast and size
- Standardize labels and helper text
- Add inline validation states
FAQ
Do UI audits replace UX audits?
No. A UI audit focuses on the interface layer, but a UX audit covers the full journey.
Do UI audits need heuristics?
Heuristics help reviewers find predictable usability issues, and they keep audits consistent.
What should a UI audit report include?
A UI audit report should include the findings, the evidence, the severity and the recommendations, so that teams can act quickly.
Related resources
For a fast review of one page, run a Roast My Web website design audit for the visual layer or a website UX audit for usability. To review a whole journey, use the UX audit template. To check the interface against usability heuristics, use the heuristic evaluation template.



