UX Audit Checklist: 50 Points to Evaluate Your Digital Product

Artyom Dovgopol

Most UX audits I see are either too shallow (just heuristics) or too academic (nobody acts on them). This checklist is what we actually use internally — 50 checks, grouped by impact, with clear pass/fail criteria. If you score below 35, you're leaving money on the table.

Key takeaways 👌

Table of Contents

1. How to Use This Checklist

2. Performance & Core Web Vitals (Points 1–5)

3. Navigation & Information Architecture (Points 6–10)

4. Mobile Experience (Points 11–15)

5. Forms & User Input (Points 16–20)

6. Visual Design & Consistency (Points 21–25)

7. Accessibility (Points 26–30)

8. Content & Readability (Points 31–35)

9. Trust & Credibility (Points 36–40)

10. Search, Filtering & Discovery (Points 41–45)

11. Analytics & Measurement (Points 46–50)

12. Scoring and Next Steps

Introduction

A UX audit tells you what's broken before you decide what to build.

Most digital products accumulate UX debt the same way they accumulate technical debt — gradually, invisibly, and expensively. A button that confused 2% of users at launch now confuses 5% because three features were bolted on around it. A page that loaded in 1.8 seconds now takes 4.2 because nobody audited the third-party scripts. A mobile experience that was "good enough" in 2023 is now losing 30% of visitors to competitors who actually optimized for thumb zones.

The problem isn't awareness. Most teams know something feels off. The problem is diagnosis. Without a structured framework, UX improvements become opinion-driven — the CEO wants bigger buttons, the designer wants more whitespace, the developer wants fewer animations. Everyone's right about something. Nobody's looking at the whole picture.

This checklist provides that picture. Fifty checks across ten categories, each with clear criteria. It's not a redesign plan — it's a diagnostic tool. Use it to identify which problems are costing you the most, then prioritize fixes based on impact and effort. For a deeper look at what current UX design trends expect from digital products, that context helps calibrate your scoring.

We use a version of this checklist on every UX/UI audit we conduct at Toimi. The public version below is simplified for self-assessment, but the structure is the same.

How to Use This Checklist

Scoring: Rate each point on a 0–1–2 scale:

• 0 = Fail. The issue is clearly present and measurable.
• 1 = Partial. Some effort exists, but it's inconsistent or incomplete.
• 2 = Pass. The standard is met consistently across the product.

Maximum score: 100 points (50 checks × 2 points each).

Interpreting your score:

• 85–100: Strong UX foundation. Focus on optimization and A/B testing.
• 70–84: Solid but leaky. You have specific friction points costing conversions.
• 50–69: Structural problems. Users are working around your product, not with it.
• Below 50: Critical. UX is actively driving users away. Prioritize a full audit.

How to audit: Open your product in Chrome DevTools (for performance), a mobile device (for mobile checks), and a screen reader like NVDA or VoiceOver (for accessibility). You'll need Google PageSpeed Insights, your analytics tool, and 2–3 hours.

Who should do it: Product managers, UX designers, or developers — ideally two people independently, then compare scores. Disagreements reveal the most interesting problems.

CATEGORY 1: Performance & Core Web Vitals

Performance is the foundation of UX. A beautiful interface that loads in 5 seconds loses 38% of users before they see it. Google uses Core Web Vitals as ranking signals, so performance directly affects both UX and SEO. Solid web development practices at the build stage prevent most of these issues from appearing at all.

Point 1: Largest Contentful Paint (LCP) under 2.5 seconds

LCP measures how long it takes for the largest visible element (usually a hero image or heading) to render. Google's threshold: under 2.5s is "good," 2.5–4s is "needs improvement," over 4s is "poor."

How to check: Run your homepage and three key landing pages through PageSpeed Insights. Check both mobile and desktop.

Common fixes: Optimize hero images (WebP format, proper sizing), preload critical resources, reduce server response time (TTFB), remove render-blocking JavaScript.

Point 2: Cumulative Layout Shift (CLS) under 0.1

CLS measures visual stability — how much the page layout shifts as it loads. A CLS above 0.1 means elements are jumping around, causing misclicks and frustration.

How to check: PageSpeed Insights or Chrome DevTools Performance tab. Pay special attention to pages with ads, images without dimensions, or dynamically loaded content.

Common fixes: Set explicit width and height on all images and videos, reserve space for ad slots, avoid inserting content above existing content.

Point 3: Interaction to Next Paint (INP) under 200ms

INP replaced First Input Delay in 2024 as Google's responsiveness metric. It measures the delay between a user interaction (click, tap, keypress) and the visual response.

How to check: Chrome DevTools Performance tab or Web Vitals JavaScript library. Test on actual mobile devices, not just desktop simulation.

Common fixes: Break up long JavaScript tasks, defer non-critical scripts, reduce main thread blocking time.

Point 4: Total page weight under 3MB on key pages

Page weight includes all resources: HTML, CSS, JavaScript, images, fonts, third-party scripts. Heavy pages drain mobile data and slow rendering.

How to check: Chrome DevTools Network tab — check "transferred" size with cache disabled. Test homepage, product/service pages, and blog.

Common fixes: Audit third-party scripts (analytics, chat widgets, tracking pixels), lazy-load below-fold images, remove unused CSS and JavaScript. A site optimization service covers most of these fixes systematically without requiring a full redevelopment cycle.

Point 5: Time to First Byte (TTFB) under 600ms

TTFB measures server responsiveness — how quickly the server starts sending data after receiving a request. Slow TTFB indicates server-side problems that no frontend optimization can fix.

How to check: PageSpeed Insights (Server Response Time) or curl -o /dev/null -w "TTFB: %{time_starttransfer}\ " https://yoursite.com

Common fixes: Upgrade hosting, enable server-side caching, optimize database queries, use a CDN. Persistent TTFB issues often indicate problems that technical SEO and server audits surface together, since slow response times directly suppress search rankings.

CATEGORY 2: Navigation & Information Architecture

Navigation is how users find what they need. Poor navigation doesn't just frustrate — it makes your content invisible. Pages that can't be found might as well not exist.

Point 6: Primary navigation is consistent across all pages

The main menu should appear in the same position, with the same items, on every page. Inconsistencies force users to re-learn the interface on each page.

How to check: Visit 10 random pages including homepage, service pages, blog, and contact. Is the navigation identical? Are there pages where items disappear or change order?

Point 7: Users can reach any page in 3 clicks or fewer

The "3-click rule" is debated, but the principle holds: deep hierarchies increase abandonment. If your most important pages require 4+ clicks from the homepage, they're buried.

How to check: Map click paths from the homepage to your top 10 pages by traffic. Count clicks. Check both desktop and mobile paths.

Point 8: Current location is always visible (breadcrumbs or active states)

Users should always know where they are. This requires breadcrumbs on interior pages and active/highlighted states in the navigation for the current section.

How to check: Navigate to a deep interior page. Can you tell which section you're in without reading the page content? Is there a breadcrumb trail?

Point 9: 404 page is helpful, not a dead end

A custom 404 page should include navigation, a search bar, and links to popular pages. A default "Page Not Found" with no navigation is an exit point.

How to check: Visit a non-existent URL on your site. Does the 404 page help users recover, or does it abandon them?

Point 10: Footer contains secondary navigation and key links

The footer is the last chance to catch users who didn't find what they needed. It should include sitemap-style links, contact information, legal pages, and social links.

How to check: Review the footer. Does it include links to all major sections? Is contact information visible? Are legal pages (privacy, terms) linked?

CATEGORY 3: Mobile Experience

Mobile accounts for 60%+ of web traffic globally. A desktop-first product that "works on mobile" is not the same as a mobile-optimized product. This category checks whether your mobile experience is designed, not just adapted.

Point 11: Touch targets are at least 44×44 pixels

Apple's Human Interface Guidelines and Google's Material Design both specify minimum touch target sizes. Buttons, links, and interactive elements smaller than 44×44px cause misclicks on mobile.

How to check: Use Chrome DevTools device simulation. Try tapping every interactive element with your thumb. Are any frustratingly small?

Point 12: No horizontal scrolling on any page

Horizontal scrolling on mobile is almost always a bug — content that overflows the viewport. It breaks the mental model of vertical scrolling and makes pages feel broken.

How to check: Open every major page on a real mobile device. Swipe left and right. Any horizontal movement that reveals empty space or hidden content is a fail.

Point 13: Text is readable without zooming (minimum 16px body)

Body text below 16px on mobile requires pinch-to-zoom, which Apple and Google both discourage. If users need to zoom to read your content, you've failed a basic mobile standard.

How to check: Open your site on a phone. Can you comfortably read body text at arm's length without zooming?

Point 14: Mobile menu is reachable with one hand

The most common mobile interaction is one-handed, thumb-driven browsing. If your hamburger menu or primary CTAs are at the top of the screen, they're in the hardest-to-reach zone.

How to check: Hold your phone normally. Can you reach the menu icon and primary CTA with your thumb without shifting your grip?

Point 15: Critical content appears above the fold on mobile

"Above the fold" on mobile means the first 600–700px of screen height. Your value proposition, primary CTA, and key information should be visible without scrolling.

How to check: Screenshot the top of your homepage on a mobile device. Does it communicate what you do, for whom, and what to do next?

CATEGORY 4: Forms & User Input

Forms are where UX meets revenue. Every unnecessary field, confusing label, or unhelpful error message reduces completion rates. This category audits the friction in your most important conversion points. Usability testing is the most reliable way to discover which form issues are costing you the most conversions.

Point 16: Forms ask only for necessary information

Every additional field reduces form completion by 5–10%. If you're asking for company size, job title, and phone number on a newsletter signup, you're filtering out leads.

How to check: List every field in your primary form. For each one, ask: "Do we need this to deliver the first value?" If no, remove it.

Point 17: Input fields have visible labels (not just placeholders)

Placeholder text disappears when users start typing, leaving them without context. Labels should be persistently visible above or beside the input field.

How to check: Start filling out your forms. When you're in the third field, can you still see what the first field is asking for?

Point 18: Error messages are specific and appear inline

"Please fix the errors below" is useless. Error messages should appear next to the specific field, explain what's wrong, and suggest how to fix it.

How to check: Submit your forms with intentionally wrong data (invalid email, empty required fields). Are errors specific? Do they appear next to the right field?

Point 19: Form progress is visible for multi-step processes

If your form has more than 3 steps, users need to know where they are and how much is left. Progress indicators reduce abandonment by setting expectations.

How to check: Start a multi-step form. Can you see how many steps total and which step you're on? Can you go back without losing data?

Point 20: Successful submission provides clear confirmation

After submitting a form, users should see a clear confirmation message, know what happens next, and have a path forward (not a dead-end "thank you" page).

How to check: Submit your primary form. Is the confirmation message clear? Does it tell you when to expect a response? Is there a next action available?

CATEGORY 5: Visual Design & Consistency

Visual consistency builds trust unconsciously. Inconsistent spacing, mixed button styles, and clashing typography make products feel unreliable — even if the functionality works perfectly. A professional UI/UX design system is what keeps these elements consistent at scale.

Point 21: Color system is consistent (max 3 primary + 2 accent colors)

A bloated color palette signals design debt. Every page should use the same color roles: primary action, secondary action, success, error, neutral backgrounds.

How to check: Screenshot 5 different pages. Compare button colors, background colors, and text colors. Are they consistent? Can you identify the primary action color immediately?

Point 22: Typography hierarchy is clear and consistent

Users should be able to distinguish H1, H2, H3, body text, and captions at a glance. If heading sizes are inconsistent or body text varies between pages, the hierarchy is broken.

How to check: Compare heading sizes across 5 pages. Is H1 always the same size? Is body text the same font and size everywhere? Are there more than 3 font families in use?

Point 23: Spacing and alignment follow a consistent grid

Inconsistent padding and margins create visual noise. Elements should align to a baseline grid (typically 4px or 8px increments) across the product.

How to check: Enable grid overlay in your browser DevTools. Do major elements align? Are margins between sections consistent?

Point 24: Button styles are consistent and distinguishable

Primary, secondary, and tertiary buttons should each have a distinct, consistent style. If primary buttons are sometimes blue and sometimes green, users can't predict behavior.

How to check: Find every button style in your product. Are there more than 3 distinct styles? Can you immediately tell which button is the primary action on each page?

Point 25: Visual hierarchy guides the eye to the most important element

On every page, one element should dominate attention — usually the headline or primary CTA. If everything competes for attention, nothing wins.

How to check: Squint at each page (or use a blur tool). Can you still identify the most important element? If the page looks like uniform gray when blurred, hierarchy is weak — a sign the product may benefit from custom UI/UX design rather than incremental patches.

CATEGORY 6: Accessibility

Accessibility isn't optional — it's a legal requirement in many jurisdictions (ADA, EAA) and a UX improvement for everyone. These 5 checks cover the most impactful accessibility issues.

Point 26: Color contrast meets WCAG AA (4.5:1 for text)

Insufficient contrast makes text unreadable for users with low vision — and harder to read for everyone in bright sunlight or on low-quality screens.

How to check: Use WebAIM Contrast Checker or Chrome DevTools accessibility panel. Test body text, heading text, and button text against their backgrounds.

Point 27: All images have meaningful alt text

Alt text serves screen reader users and appears when images fail to load. "IMG_2847.jpg" or empty alt attributes are failures.

How to check: Inspect 10 images across your site. Do they have alt attributes? Are the descriptions meaningful (describing content, not "image" or "photo")?

Point 28: Site is navigable by keyboard alone

Users who can't use a mouse (motor impairments, power users, screen reader users) rely on Tab, Enter, and Arrow keys. Every interactive element must be reachable and operable via keyboard.

How to check: Put your mouse in a drawer. Navigate your site using only Tab, Shift+Tab, Enter, and Escape. Can you reach every link, button, and form field? Is the focus indicator visible?

Point 29: Focus indicators are visible on all interactive elements

When tabbing through a page, the currently focused element should be clearly highlighted. Removing or hiding focus outlines (a common CSS "fix") breaks keyboard navigation.

How to check: Tab through your site. Can you always see which element is currently focused? Is the focus ring visible against the background?

Point 30: Page structure uses semantic HTML (headings, landmarks, lists)

Screen readers use HTML semantics to build a page outline. If your headings skip levels (H1 → H3), your navigation is a <div> instead of <nav>, or your lists are styled <p> tags, screen reader users can't navigate your content.

How to check: Run the WAVE accessibility checker or use the headings outline feature in the axe browser extension. Is the heading hierarchy logical? Are landmarks (nav, main, aside, footer) properly marked?

CATEGORY 7: Content & Readability

Content is the interface. Beautiful design with unclear copy is like a luxury store with no price tags — impressive but frustrating. This category evaluates whether your content actually works.

Point 31: Headlines clearly communicate value (not just topic)

"Our Services" tells users nothing. "Web Development for B2B Companies" tells them everything. Every page headline should answer "what do I get?" — not just "what is this about?"

How to check: Read only the headlines of your top 10 pages. Without reading body text, can you understand what each page offers and to whom?

Point 32: Body text uses short paragraphs (max 3–4 sentences)

Long paragraphs are walls of text on mobile. Break content into scannable chunks with clear topic sentences.

How to check: Open 5 content-heavy pages on mobile. Are there paragraphs longer than 4 sentences? Do any paragraphs extend beyond one screen on mobile?

Point 33: Technical jargon is explained or avoided

Every industry has jargon that insiders forget is jargon. If your audience is broader than your team, test whether outsiders understand your copy.

How to check: Show your homepage to someone outside your industry. Ask them to explain what you do. If they can't, your copy is too insider-focused.

Point 34: CTAs use action verbs and set expectations

"Submit" is a CTA. "Get Your Free Audit in 24 Hours" is a better one. CTAs should tell users what happens next, not just label a button.

How to check: List every CTA on your site. Does each one tell the user what they'll get? Is there a time or value signal? Replace every "Submit" and "Learn More" you find.

Point 35: Content is scannable with subheadings, bullets, and bold text

80% of users scan rather than read. If your pages are continuous prose without visual anchors, users will miss your most important points.

How to check: Scroll through your key pages quickly (2 seconds per page). Can you extract the main points from subheadings and bold text alone?

CATEGORY 8: Trust & Credibility

Trust is the invisible UX layer. Users decide whether they trust your product in the first 3–5 seconds. These signals operate below conscious awareness but directly affect conversion.

Point 36: Social proof is visible on key conversion pages

Testimonials, client logos, case studies, or ratings should appear near conversion points — not buried on a separate page.

How to check: Visit your homepage, pricing page, and contact page. Is social proof visible without scrolling? Are testimonials attributed to real people with names, titles, and companies?

Point 37: Contact information is easy to find

Hidden contact information signals that you don't want to be reached. Phone, email, and address should be in the header, footer, or a persistent element.

How to check: From any page, how many clicks does it take to find a phone number or email? Can you find it in under 5 seconds?

Point 38: Security indicators are present on forms and checkout

HTTPS padlock, payment badges, privacy policy links, and SSL certificates reassure users when submitting sensitive information.

How to check: Inspect your form and checkout pages. Is HTTPS active? Are payment and security badges visible? Is a privacy policy linked near the form?

Point 39: Content is current and dates are recent

Outdated copyright years, blog posts from 2019, and "2023 Guide" titles in 2026 signal abandonment. Users trust active, maintained products.

How to check: Check your footer copyright year, most recent blog date, and any date references in content. Is everything current?

Point 40: Team or company information is transparent

Real photos, team bios, and company history build trust. Generic stock photos and anonymous "About Us" pages feel suspicious.

How to check: Visit your About page. Are there real team photos? Do bios include names and roles? Can a visitor verify that your company is real?

CATEGORY 9: Search, Filtering & Discovery

For products with more than 20 pages of content, search and filtering become primary navigation tools. Poor search is equivalent to poor navigation — users can't find what exists.

Point 41: Search is available and prominently placed

If your site has more than 30 pages, search should be accessible from every page — typically in the header.

How to check: Can you see a search icon or input from every page? Does it work on mobile?

Point 42: Search results are relevant and ranked by usefulness

Searching for your primary service should return the service page first, not a blog post from 2021. Relevance ranking matters.

How to check: Search for 5 common terms your users would use. Are the top 3 results for each search actually the most useful pages?

Point 43: Filters are available on content-heavy pages

Blog archives, product catalogs, and resource libraries need filtering by category, date, or type. Without filters, users abandon large content collections.

How to check: Visit your blog or product catalog. Can you filter by category or topic? Are filters usable on mobile?

Point 44: "No results" pages suggest alternatives

A blank "no results found" page is a dead end. Suggest related content, popular pages, or spelling corrections.

How to check: Search for a misspelled term or obscure query. Does the results page offer alternatives, or is it a dead end?

Point 45: Recently viewed or related content is suggested

Recommendation systems (related articles, "you may also like") increase pages per session and reduce bounce rate.

How to check: Read a blog post or view a product page. Are related items suggested at the bottom? Are the suggestions relevant?

CATEGORY 10: Analytics & Measurement

You can't improve what you don't measure. This final category checks whether you have the infrastructure to track UX problems and measure improvements.

Point 46: Analytics tracks key user flows, not just page views

Page views tell you where users go. Flow analysis tells you where they get stuck. Track the complete journey through your most important conversions.

How to check: Can you answer: "What percentage of homepage visitors reach the contact form? Where do they drop off?" If not, your analytics setup needs work.

Point 47: Heatmaps or session recordings are active on key pages

Analytics shows what users do. Heatmaps and recordings show how they do it — where they hover, where they rage-click, where they get confused.

How to check: Do you have Hotjar, Clarity, or a similar tool running on your top 5 pages by traffic? Have you reviewed recordings in the last 30 days?

Point 48: Core Web Vitals are monitored continuously

One-time performance checks catch problems. Continuous monitoring (via Google Search Console or a real-user monitoring tool) catches regressions before they affect rankings.

How to check: Open Google Search Console → Core Web Vitals. Do you have enough data for an assessment? Are all URLs in "Good" status?

Point 49: Error tracking captures JavaScript and API failures

Broken features that don't trigger visible errors are invisible problems. Users experience something "not working" and leave without reporting it.

How to check: Do you use Sentry, LogRocket, Bugsnag, or a similar error tracking tool? Can you see errors that happened in the last 7 days?

Point 50: UX metrics are reviewed at least monthly

Data without review is just storage cost. UX metrics should inform product decisions — which means someone needs to look at them regularly.

How to check: When was the last time your team reviewed bounce rate, conversion rate, task completion rate, or Core Web Vitals together? If it's been more than a month, this is a fail.

Scoring and Next Steps

Calculate Your Score

Add up your points across all 50 checks (each scored 0, 1, or 2). Maximum possible: 100.

Prioritize by Impact × Effort

Not all points are equally important. Prioritize fixes using this framework:

Fix first (high impact, low effort):

• Performance issues (points 1–5) — often server or image optimization
• Missing alt text (point 27) — content update, no design change
• Error messages (point 18) — copy change only
• Outdated content (point 39) — quick content refresh

Fix second (high impact, higher effort):

• Mobile experience (points 11–15) — may require responsive redesign
• Navigation structure (points 6–10) — information architecture work
• Form optimization (points 16–20) — design + development changes

Fix third (medium impact, requires planning):

• Accessibility (points 26–30) — systematic code and design updates
• Visual consistency (points 21–25) — design system investment. A full website redesign is often the most efficient path when multiple visual consistency issues cluster together.
• Analytics infrastructure (points 46–50) — tooling and process changes

When to Do This Audit

• Before a redesign — to identify what to fix vs. what to keep
• After a major release — to catch regressions
• Quarterly — as ongoing product health monitoring
• Before fundraising — investors will use your product; make sure it's clean

live

Want to discuss your project?

Share your vision with us, and we'll reach out soon to explore the details and bring your idea to life.

Book a free consultation

Conclusion

A UX audit is a decision tool, not a judgment. A low score doesn't mean your product is bad — it means you now know exactly where it's leaking value.

The most common mistake after an audit is trying to fix everything at once. Don't. Pick the three highest-impact items from your lowest-scoring categories and fix those first. Measure the change. Then pick three more.

Performance and mobile issues are almost always the right starting point — they affect every user on every visit, they directly impact SEO rankings, and many fixes are purely technical (no design debate required).

The second most common mistake is treating the audit as a one-time event. Products accumulate UX debt continuously — every new feature, every content update, every third-party script is a potential regression. Build the audit into your quarterly rhythm, assign ownership for each category, and track your score over time.

If your score landed below 50, a self-audit may not be enough. The structural issues at that level usually require an external perspective — someone who can see the patterns your team has normalized. That's what a professional UX audit provides: not just a list of problems, but a prioritized roadmap for fixing them in the right order.

Whatever your score, you now have a baseline. That's the first step to making your product better — not by opinion, but by evidence.