How to do a UX audit: a checklist and real examples

Run a UX audit, also called a user experience audit, when you need to know where a product’s pages make a visitor work harder than they should: before a redesign, before a launch, when a page that matters underperforms and your analytics do not say why, or after many small changes have piled up on one page. It works on a rival’s site too: the same checklist shows how a competitor leads a visitor to a first step, which you can set beside your own pages. Keep the audit to a few pages and one question, such as whether a new visitor can find the price and start a trial, so every finding answers something you will act on. For one landing page, how to do a landing page teardown reads the page in four roles.

A coExploro product teardown does steps 2 to 4 on a site’s public pages. Give it an address, yours or a rival’s: in 2–4 minutes it captures that page with its date, then the site’s pricing and features pages when it finds them. It gives them one UX score across the six dimensions of the checklist below, each dimension with one sentence that names the page element behind its score, and an AI UX analyst writes findings with an impact level, beside PM, Marketing and Designer analysts reading the same captured pages. The website UX audit page shows what a run returns. You can try one run a day per network without an account, a free account includes 3 teardowns a month, and paid plans start at $16 a month billed yearly. It does not sign in, test the site with people or read your analytics.

Check each page against the same six questions, and write down the page element behind each answer, so another reader can check it. A dimension the page does not show, such as loading states in a still screenshot, gets no score rather than a guessed one: on 23 of coExploro’s 27 public samples, the capture could not show all six.

coExploro’s 27 public samples are 27 well-known products, not a sample of the market, captured between 8 August 2026 and 29 October 2026. Each sample shows one finding per analyst, chosen for publication from that analyst’s findings, so each holds one UX finding, and we sorted those 27 findings by the part of the page they are about. Pricing tables and plan grids came first, with 8 of 27: how much a table or a row of plan cards asks a reader to compare, such as four plans side by side or cells marked only with a check or a minus sign. The header and navigation came next with 5, then the hero’s first action with 5 and the pricing FAQ with 4; on the hero, a free start sat beside a demo request or a sign-up beside a download. A run reads a site’s homepage, pricing and features pages, so pricing pages weigh heavily here. A count says where these published findings sit, not which site is better or what every UX audit finds.

Three findings from the samples show what one line of a UX audit looks like. In the Notion sample, captured on 29 October 2026, the pricing page opened its questions with how Notion AI uses your data, ahead of invoices and payment methods. On Supabase’s pricing page, captured the same day, many cells of the plan comparison held a green check mark or a grey minus sign rather than words. On Crayon’s, the pricing page was a ten-field form with no plan or price. Later that day, after the captures, the Notion and Crayon pages still opened the same way, as the observations below show. Each card below names the analyst, the capture date and, where the finding has one, the quote it rests on, marked on the capture.

• 

  Notion · UX · Captured Oct 29, 2026

  Seventeen questions sit under the pricing table

  The pricing FAQ, 'Questions & answers', sits below the 'Plans and features' table and lists seventeen questions. It opens with 'How does Notion AI use my data?' and only then asks 'Where can I find my invoices?' and 'What are your accepted payment methods?'

  Evidence: How does Notion AI use my data? · Seen on www.notion.so/pricing, FAQ below the plan tables, first question · Captured Oct 29, 2026 · Indirect evidence

• 

  Supabase · UX · Captured Oct 29, 2026

  Comparison cells use green check marks and grey minus signs

  In the plan comparison table further down the pricing page, many cells hold a green circle with a check mark or a grey circle with a minus sign rather than words. Other cells carry values such as '7 days', 'Never' or 'Custom'.

  Evidence: Advanced disk config · Seen on supabase.com/pricing, pricing page comparison table, Database group, row label beside a grey minus sign for Free and green check marks for the paid plans · Captured Oct 29, 2026 · Indirect evidence

• 

  Crayon · UX · Captured Oct 29, 2026

  The pricing page is a ten-field estimate form

  The pricing page shows a 'Request an Estimate' form and no plan or price. All ten field labels end in an asterisk, from 'First Name*' to 'Message*', and '# Employees*' is a drop-down reading '- Please Select -'. The button below reads 'Send Inquiry'.

  Evidence: Request an Estimate · Seen on www.crayon.co/pricing, pricing page, heading of the form · Captured Oct 29, 2026 · Indirect evidence

• Observed by us

  The first question under ‘Questions & answers’ on Notion’s pricing page read ‘How does Notion AI use my data?’.

  verified Oct 29, 2026 · Source: notion.so/pricing (opens in a new tab)

• Observed by us

  Crayon’s pricing address led to a page headed ‘Request an Estimate’, with a ‘Send Inquiry’ button under its form.

  verified Oct 29, 2026 · Source: crayon.co/pricing (opens in a new tab)

A UX audit report states its scope first: the pages read, the date and screen width of each capture, and the question the audit answers. Then come the scores per dimension and the findings, each with the part of the page it came from, its impact and what to change or test. It ends with what the audit did not cover, such as signed-in screens, mobile layouts or live behaviour. In coExploro, a teardown holds the UX score with its six dimensions, the four analysts’ findings with their recommendations, and the capture they were read from, with the screenshot behind a finding when one is attached. coExploro’s methodology states what a capture can and cannot show.

A heuristic evaluation is one method inside a UX audit: evaluators check an interface against a short list of usability principles, such as Jakob Nielsen’s ten usability heuristics, and note each place it breaks one. A UX audit is the wider review. It can include a heuristic evaluation, and it can add analytics, accessibility checks, a review of the content and notes from user research. It ends in a list of problems in the order to fix them. Use a heuristic evaluation to check one interface against known principles, and a UX audit when you need to decide what to fix first across several pages. The six dimensions above sit between the two: a fixed checklist, scored for the pages a run reads, with the evidence for each score.

An agency or a consultant can do what a capture of public pages cannot: test the product with real users, read your analytics, review signed-in flows and accessibility in depth, and walk your team through a report. That work is scoped and priced per project. A self-serve AI audit reads public pages from one address and returns findings in minutes, so it suits a first pass, a rival’s site or a check after a change. coExploro is not an agency and does no human audit: AI analysts draft its findings from a dated capture. The two answer different questions: a quick reading shows where to look, and people show why visitors struggle there.

• Seventeen questions sit under the pricing table · Notion

  Evidence: How does Notion AI use my data? · Seen on www.notion.so/pricing, FAQ below the plan tables, first question · Captured Oct 29, 2026 · Indirect evidence

• Pro starts at $25 a month and Team at $599 · Supabase

  Evidence: Add features such as SSO, control over backups, and industry certifications. · Seen on supabase.com/pricing, pricing page, TEAM plan card, line under the plan name · Captured Oct 29, 2026 · Indirect evidence

• UX audit template, with a filled-in report example
• How to do a pricing page teardown
• Product teardown template, blank and filled in