The Complete UI/UX Audit Checklist for SaaS Products

Most SaaS products accumulate UX debt faster than they accumulate technical debt. Every sprint adds features, but rarely removes complexity. Every customer request adds a menu item, a toggle, a configuration option. After 2-3 years, the product that started as "simple and intuitive" has become a maze of screens, settings, and workflows that even the product team can't navigate without thinking.

After conducting UX audits for 40+ SaaS products — from pre-seed startups to enterprise platforms with 10,000+ users — we've compiled the checklist we actually use. It's organized by product area, with specific metrics to measure, common problems to look for, and benchmarks to compare against.

How to use this checklist

Step 1: Gather data before auditing. Install analytics (GA4, Amplitude), session recording (Hotjar, FullStory), and heatmaps (Hotjar, Clarity) at least 2 weeks before the audit. You need baseline data to identify patterns.

Step 2: Walk the product as a new user. Create a fresh account and go through every step of the user journey, from landing page to core value. Document friction points as you encounter them.

Step 3: Score each section. Use a 1-5 scale (1 = critical issues, 5 = excellent). Prioritize fixes by impact × effort.

Step 4: Validate with users. Your expert assessment is hypothesis. User testing (5-8 users) confirms which issues are real friction points versus theoretical concerns.

Section 1: First impressions and signup

The landing page → signup transition

Check:

• Is the value proposition clear within 5 seconds? (Can a new visitor explain what the product does?)
• Is the CTA visible above the fold without scrolling?
• Does the signup form request only essential information? (Name, email, password — nothing else for initial signup)
• Can users sign up with SSO (Google, GitHub, Microsoft)? (Expected for B2B SaaS in 2026)
• Is the signup flow mobile-optimized?

Common problems:

• Value proposition buried below a hero image with no text
• "Request a demo" as the only CTA (losing self-service signups)
• Requiring company name, phone number, and job title at signup (each additional field reduces conversion 3-5%)
• No SSO options (B2B users expect Google/Microsoft login)

Benchmark: Top-quartile SaaS products convert 3-7% of website visitors to signups. Below 2% indicates a landing page or signup friction problem.

Metric to track: Website visitor → signup conversion rate, broken down by traffic source.

Email verification

Check:

• Is email verification required before the user can use the product?
• If yes, can users explore the product while waiting for verification?
• Is the verification email sent within 30 seconds?
• Is there a "resend" option?

Common problems:

• Requiring email verification before showing any product value (kills 15-25% of signups who don't verify immediately)
• Verification emails landing in spam (test with Gmail, Outlook, and corporate email)
• No fallback for users who don't receive the email

Best practice: Let users explore the product immediately. Show a banner "Please verify your email to unlock all features" but don't block access to the core experience.

Section 2: Onboarding

Time to first value

Check:

• How many steps between signup and the first "aha moment" (the moment the user experiences the product's core value)?
• Can the user reach first value in under 5 minutes?
• Does the onboarding guide the user to first value, or does it dump them into a dashboard?

Common problems:

• Onboarding that focuses on product features ("here's your sidebar, here's your settings") instead of user outcomes ("let's create your first project")
• Mandatory tutorials that can't be skipped
• Onboarding flows that require data import before the user can do anything (provide sample data as an alternative)

Benchmark: Best-in-class SaaS products achieve first value in 2-3 minutes. If your time-to-first-value exceeds 10 minutes, you're losing a significant portion of trial users.

Metric to track: Signup → first key action completion rate and time.

Onboarding flow design

Check:

• Is there a progress indicator showing how far along the user is?
• Can the user skip steps and come back later?
• Does the onboarding adapt to the user's role or use case? (A marketing manager and a developer should see different onboarding paths)
• Are empty states helpful? (When a dashboard is empty, does it explain what goes there and how to add it?)

Common problems:

• Linear onboarding that forces all users through the same 8-step flow regardless of their use case
• Empty dashboards with no guidance ("No data yet" — what should I do about that?)
• Overwhelming tooltip tours that highlight 20 UI elements in sequence (users dismiss these without reading after the 3rd tooltip)

Best practice: Ask users their goal during onboarding (max 3 options), then guide them to achieve that specific goal. Everything else can wait.

Section 3: Navigation and information architecture

Primary navigation

Check:

• Can users find any feature within 3 clicks from anywhere in the product?
• Is the navigation structure consistent across all pages?
• Are navigation labels clear and specific? ("Analytics" is better than "Insights"; "Team Members" is better than "People")
• Is there a global search that covers all product areas?
• Does the navigation collapse appropriately on smaller screens?

Common problems:

• Nested navigation more than 3 levels deep (users get lost)
• Inconsistent navigation labels (the sidebar says "Analytics" but the page header says "Reports")
• No global search (forces users to remember where every feature lives)
• Navigation items ordered by development chronology instead of user frequency (the newest feature at the bottom, even if it's the most used)

Metric to track: Average clicks to reach key features (measure with session recordings or click-path analysis).

Search

Check:

• Does global search cover all content types (records, settings, help docs)?
• Does search understand common misspellings and abbreviations?
• Are search results grouped by type and ordered by relevance?
• Does search support keyboard navigation (arrow keys to select, Enter to go)?
• Is search accessible from a keyboard shortcut (Cmd/Ctrl+K is now standard)?

Common problems:

• Search that only covers one content type (searches projects but not tasks, or searches records but not settings)
• No fuzzy matching (misspelling "invioce" returns no results for "invoice")
• Search results that don't indicate which section of the product the result is in

Section 4: Core workflows

Task completion flow

For each of your product's 3-5 core workflows, check:

Check:

• How many steps does it take to complete the task?
• Is the sequence logical? (Does each step's output naturally lead to the next step's input?)
• Are there unnecessary confirmation dialogs? ("Are you sure?" for non-destructive actions)
• Can the user undo actions instead of confirming them?
• Is progress auto-saved? (If the user closes the tab mid-task, can they resume?)

Common problems:

• Confirmation dialogs for every action (dialog fatigue — users click "Yes" without reading)
• No undo capability (forcing irreversible actions increases user anxiety)
• Losing work when navigating away (no auto-save or draft state)
• Required fields that aren't marked as required until submission fails

Metric to track: Task completion rate and time for each core workflow.

Forms

Check:

• Are required fields marked before the user submits (not just after submission fails)?
• Is validation inline (showing errors as the user types) or only on submit?
• Do text inputs have appropriate type attributes (email, tel, number)?
• Are default values sensible? (Don't make users select their country from a list of 240 when you know 80% are in the US)
• Are long forms broken into logical sections or steps?

Common problems:

• Validation only on submit (user fills 15 fields, submits, scrolls up to find which one is wrong)
• No character counts on text areas with limits (user writes 500 characters, finds out the limit is 200 after submitting)
• Date pickers that default to January 1, 2024 (instead of today's date)
• Dropdown menus with 100+ options and no search/filter

Data tables

Check:

• Are tables sortable by column?
• Is there a column filter or search?
• Can users customize which columns are visible?
• Is pagination or infinite scroll implemented for large datasets?
• Are bulk actions available (select multiple rows, bulk delete/export/update)?
• Do tables work on mobile? (Horizontal scroll, card layout alternative, or priority columns)

Common problems:

• Tables that load all 10,000 rows at once (performance and usability disaster)
• No way to export data (users screenshot tables to share with colleagues)
• Row actions hidden behind a "..." menu that's too small to tap on mobile
• Sorting that reloads the page instead of sorting client-side

Section 5: Settings and configuration

Check:

• Are settings grouped logically? (Account, Notifications, Billing, Integrations — not one long list)
• Is each setting's effect explained? (Not just "Enable feature X" but "When enabled, X will Y")
• Are dangerous settings (delete account, downgrade plan) visually distinct and require confirmation?
• Can settings be searched?
• Do settings changes take effect immediately or require a save/apply action? (Be consistent — don't mix both patterns)

Common problems:

• 100+ settings on a single page with no categorization
• Settings that require a page refresh to take effect (without telling the user)
• No explanation of what a setting does (toggle labeled "Advanced Mode" — what does that mean?)
• No way to reset settings to defaults

Section 6: Error handling and empty states

Error messages

Check:

• Do error messages explain what went wrong in plain language?
• Do error messages suggest what the user can do to fix it?
• Are errors displayed near the field or action that caused them (not just a red banner at the top)?
• Are network errors handled gracefully (not a blank page or raw error stack)?

Common problems:

• "An error occurred. Please try again." (What error? Why? What if trying again doesn't work?)
• Technical error messages shown to non-technical users ("500 Internal Server Error" or "TypeError: Cannot read property 'id' of undefined")
• Errors that clear the user's input (they have to re-enter everything)

Empty states

Check:

• Does every list/table/dashboard have a meaningful empty state?
• Does the empty state tell the user how to add their first item?
• Is there a call-to-action in the empty state (button to create first item)?
• Are empty states visually pleasant (not just "No data")?

Common problems:

• Bare "No results found" or "Empty" text with no guidance
• Empty state that looks like a bug (is the data not loading, or is there genuinely no data?)

Section 7: Billing and plan management

Check:

• Is pricing clearly displayed before and after signup?
• Can users upgrade and downgrade without contacting sales?
• Is the billing page easy to find?
• Are invoices downloadable?
• Is the payment flow PCI compliant and using a reputable payment processor?
• Are trial expiration warnings clear and timely (3 days, 1 day, expiration)?

Common problems:

• Hiding pricing (forces all prospects to "request a demo")
• Making downgrade difficult (5-step process with retention offers on every step)
• No self-service cancellation (requiring users to email support to cancel violates trust and, in some jurisdictions, regulations)
• Unclear what happens to data after cancellation

Section 8: Performance

Check:

• Does the initial page load in under 3 seconds?
• Do navigation transitions complete in under 300ms?
• Do data tables render in under 1 second for typical data volumes?
• Are images optimized (WebP, lazy-loaded, properly sized)?
• Is there a loading indicator for actions taking more than 200ms?

Metrics to track:

• Largest Contentful Paint (LCP): should be under 2.5 seconds
• First Input Delay (FID): should be under 100ms
• Cumulative Layout Shift (CLS): should be under 0.1
• Time to Interactive (TTI): should be under 3.5 seconds

Section 9: Accessibility

Check:

• Does the product pass WCAG 2.1 AA automated checks? (Run axe DevTools on every major page)
• Is all interactive content keyboard accessible?
• Do all images have descriptive alt text?
• Are color contrasts sufficient (4.5:1 for normal text, 3:1 for large text)?
• Does the product work with screen readers? (Test with VoiceOver on Mac, NVDA on Windows)
• Are focus states visible for all interactive elements?

Common problems:

• Focus trapped in modals with no escape
• Custom dropdown components that aren't keyboard accessible
• Decorative images with verbose alt text (or functional images with no alt text)
• Color as the only indicator of state (red for error, green for success — invisible to colorblind users)

Section 10: Mobile experience

Check:

• Are the top 5 user workflows usable on mobile?
• Are touch targets at least 44×44px?
• Is text readable without zooming (minimum 16px for body text)?
• Do forms work with mobile keyboards (appropriate input types)?
• Does the product work in portrait and landscape orientation?

Common problems:

• Desktop sidebar that becomes an unusable hamburger menu on mobile
• Tables that require horizontal scrolling with no indicator that content is hidden
• Buttons too small to tap accurately
• Modal dialogs that overflow the mobile viewport

Scoring and prioritization

After completing the audit, score each section 1-5 and prioritize fixes using this matrix:

Priority	Criteria	Fix timeline
Critical (P0)	Blocks core workflow, affects >50% of users	This sprint
High (P1)	Significant friction in core workflow, affects >20% of users	Next 2 sprints
Medium (P2)	Moderate friction, workaround exists	Next quarter
Low (P3)	Minor annoyance, cosmetic issue	Backlog

Focus on the critical and high items. Every SaaS product has 50+ UX improvements in the backlog. The ones that move metrics are the ones that reduce friction in core workflows — not the ones that make the settings page slightly prettier.

---

Want us to audit your SaaS product? Talk to our design team — every audit includes a scored checklist, session recording analysis, and a prioritized recommendations report.