---
title: "UX audit checklist: process, severity ratings and cost"
description: "A UX audit checklist in seven tables: heuristics, funnels, recordings, 5-user tests, WCAG, content and speed, plus prioritization and published prices."
url: "https://dardo.studio/en/blog/ux-audit-checklist/"
language: "en"
updated: "2026-10-17T23:35:11.514Z"
---

[Blog](https://dardo.studio/en/blog/)

# UX audit checklist: what to review, how to rank findings and what an audit costs

A UX audit checklist by area, from NN/g's 10 heuristics to funnels, five-user tests and WCAG 2.2, plus how to rank findings and published audit prices.

By [Nicolás Cerón](https://dardo.studio/en/nicolas-ceron/) ·October 17, 2026

![A lamplit hedge maze at blue hour with a single crimson ribbon tracing a route that ends at a dead end.](https://dardo.studio/_astro/01M563FZDEGHVYR75B30D2373K_ZobKrk.webp)

## Key takeaways

- A complete UX audit combines seven checks run against named tasks: a heuristic review, funnel analysis, recordings and heatmaps, usability tests, and accessibility, content and performance checks.
- Nielsen Norman Group recommends three to five evaluators reviewing independently for a heuristic evaluation, and says it can't replace research with real users.
- Nielsen's model has five users finding about 85% of usability problems; three rounds of five improve a design more than one round of 15, while tracked metrics need about 40 participants.
- Rank findings by severity on NN/g's 0–4 scale × the share of sessions that reach the step × the task's business value, taking frequency from analytics so it isn't counted twice.
- Published UX audit prices on 17 October 2026 ranged from a USD 27 automated report to USD 500–1,500 on Upwork and from USD 60,000 at Nielsen Norman Group; a DIY round of five tests costs about USD 500 before incentives.

## The short answer

A UX audit checks whether people can complete the tasks that matter on your site or product, and explains why they fail. A complete one combines seven checks: a heuristic review against Nielsen Norman Group's 10 heuristics by three to five people working separately, funnel analysis in your analytics, session recordings and heatmaps, usability tests with about five people per round, and checks of accessibility, content and speed. Each finding gets a severity, a reach and a business value, which sorts the list into what to fix now.

Published prices we read on 17 October 2026 run from a free automated report to USD 500–1,500 for a basic audit on Upwork and from USD 60,000 for a Nielsen Norman Group design review. A small team can run the do-it-yourself version below for about USD 500 in tools and recruiting, plus participant incentives and its own time.

## Scope it before you check anything

An audit that reviews "the website" finds a long list of small problems and misses the one that costs money. Scope it around tasks instead.

1. **Name the user groups**: for example, first-time visitors, trial users and admins. Groups that behave differently are tested separately.
2. **List three to six tasks per group** in the user's words: "find out what it costs", "book a demo", "invite a teammate", "export last month's report".
3. **Gather what you already know**: analytics, support tickets, the questions sales hears, survey answers and past research.
4. **Fix devices and browsers**: if most traffic is on phones, the review and the tests happen on phones.
5. **Pick the evaluators**: three to five people, ideally including someone who didn't design the screens.

The checklist below follows that scope. Each table can be copied into a spreadsheet, one row per check per task.

## The UX audit checklist, area by area

### 1\. Heuristic review

Nielsen Norman Group's [10 usability heuristics](https://www.nngroup.com/articles/ten-usability-heuristics/), first published in 1994 and last reviewed in January 2024, are "broad rules of thumb", not a checklist of features. Walk through each task and ask the questions in the middle column.

| Heuristic                                                   | Check on each task                                                          | Typical failure                                                          |
| ----------------------------------------------------------- | --------------------------------------------------------------------------- | ------------------------------------------------------------------------ |
| 1\. Visibility of system status                             | Does every action show a result: loading, saved, sent, failed?              | A form that clears without confirming it was sent                        |
| 2\. Match between the system and the real world             | Are labels in the visitor's words, not the company's?                       | Navigation named after internal teams or product codenames               |
| 3\. User control and freedom                                | Can people undo, go back or leave a flow without losing work?               | A modal with no close button; a checkout that empties the cart on "back" |
| 4\. Consistency and standards                               | Do the same things look and behave the same everywhere?                     | "Plan", "tier" and "package" used for the same thing                     |
| 5\. Error prevention                                        | Does the design stop mistakes before they happen?                           | A date field that accepts any text, then rejects it on submit            |
| 6\. Recognition rather than recall                          | Are options visible, rather than remembered from an earlier step?           | A comparison that makes people memorize prices across tabs               |
| 7\. Flexibility and efficiency of use                       | Can returning users go faster: shortcuts, saved details, bulk actions?      | Repeating the same five-step setup for every new project                 |
| 8\. Aesthetic and minimalist design                         | Does each screen show only what the task needs?                             | A pricing page where the plan details sit under three banners            |
| 9\. Help users recognize, diagnose, and recover from errors | Do error messages say what went wrong and how to fix it, next to the field? | "Something went wrong" at the top of a long form                         |
| 10\. Help and documentation                                 | Is help findable at the point of need, and task-focused?                    | A help center that answers questions nobody asks                         |

Run it the way NN/g describes in its guide to [conducting a heuristic evaluation](https://www.nngroup.com/articles/how-to-conduct-a-heuristic-evaluation/): ideally three to five evaluators, each reviewing independently before anyone compares notes, because each person misses problems the others catch. NN/g is also clear that a heuristic evaluation can't replace user research, so treat findings that rest on an assumption as questions for the tests.

### 2\. Task and funnel analysis

Analytics tells you where people drop out and how many; it doesn't tell you why. Build one funnel per task, for example with GA4's [funnel exploration](https://support.google.com/analytics/answer/9327974), which shows how many users complete or abandon each step.

| Check                              | Where to look                  | Red flag                                                               |
| ---------------------------------- | ------------------------------ | ---------------------------------------------------------------------- |
| Drop-off at each step of each task | Funnel report, split by device | One step loses far more people on mobile than on desktop               |
| Entry pages for each task          | Landing pages report           | High-intent pages, such as pricing, with short visits and no next step |
| Internal site search               | Search terms report            | Repeated searches for things that exist but aren't findable            |
| Form abandonment                   | Field-level events, if tracked | People start a form but few submit it                                  |
| Errors                             | Error and exception events     | Validation errors clustered on one field                               |
| New versus returning               | Segment comparison             | Returning users fail a task new users complete, or the reverse         |
| Tracking quality                   | Event audit                    | Missing or duplicated events; conversions that can't be trusted        |

If tracking is missing or wrong, fix it before you draw conclusions; our comparison of [GA4 and PostHog](https://dardo.studio/en/blog/ga4-vs-posthog/) covers which tool records what.

### 3\. Session recordings and heatmaps

Recordings show behavior at the steps the funnel flagged. Watch sessions that reached the worst step, not a random sample, and note what people did just before they left.

| Check                       | What to look for                                                  |
| --------------------------- | ----------------------------------------------------------------- |
| Rage clicks and dead clicks | Repeated clicks on elements that look clickable but aren't        |
| Scroll depth on key pages   | Whether the main call to action sits below where most people stop |
| U-turns                     | Visitors who open a page and come straight back                   |
| Form hesitation             | Long pauses, deletions and re-typing on specific fields           |
| Mobile taps                 | Missed taps on small or crowded controls                          |
| Errors in context           | What the visitor saw when an error event fired                    |

Check privacy settings before you record. [PostHog](https://posthog.com/docs/session-replay/privacy) and [Microsoft Clarity](https://learn.microsoft.com/en-us/clarity/faq) both mask content you mark as sensitive, and a recording tool may need the visitor's consent where your privacy law requires it.

### 4\. Usability testing with five users

Nothing else in the audit shows you why people fail. Nielsen's model estimates that a test with five users finds about 85% of a design's usability problems, and he argues that three rounds of five, fixing between rounds, improve a design more than one round of 15 ([NN/g](https://www.nngroup.com/articles/why-you-only-need-to-test-with-5-users/)). With two distinct user groups, NN/g suggests three or four people from each; with three or more groups, three from each.

| Check                           | Done when                                                                                                   |
| ------------------------------- | ----------------------------------------------------------------------------------------------------------- |
| Participants match a user group | A short screener filters by role, experience and device                                                     |
| Tasks are written as scenarios  | No interface words: "You want to know what the team plan costs for five people" rather than "Click Pricing" |
| A pilot session ran first       | One run-through fixed confusing tasks before the real sessions                                              |
| Participants think aloud        | They narrate as they go; the moderator doesn't help or hint                                                 |
| Every session is recorded       | Screen and voice, with consent                                                                              |
| Results are logged per task     | Success or failure, where they got stuck, and their own words                                               |

Five-user tests find problems; they don't measure how often they happen. For a success rate or a time-on-task you can track, NN/g's [summary of quantitative sample sizes](https://www.nngroup.com/articles/summary-quant-sample-sizes/) puts the appropriate number for most studies at 40 participants.

### 5\. Accessibility, where it overlaps with UX

A UX audit isn't an accessibility audit, but the audited tasks should pass the WCAG checks that affect everyone. [WCAG 2.2](https://www.w3.org/TR/WCAG22/), a W3C Recommendation since 5 October 2023, added [nine success criteria](https://www.w3.org/WAI/standards-guidelines/wcag/new-in-22/), several of them on this list.

| Criterion                                 | Level | Check on each task                                                                                                      |
| ----------------------------------------- | ----- | ----------------------------------------------------------------------------------------------------------------------- |
| 2.1.1 Keyboard                            | A     | Every step works with a keyboard alone                                                                                  |
| 2.4.7 Focus Visible                       | AA    | You can always see where keyboard focus is                                                                              |
| 2.4.11 Focus Not Obscured (Minimum)       | AA    | Sticky headers, chat widgets and cookie banners never fully hide the focused element                                    |
| 2.5.8 Target Size (Minimum)               | AA    | Tap targets are at least 24 by 24 CSS pixels, or spaced enough                                                          |
| 1.4.3 Contrast (Minimum)                  | AA    | Body text meets 4.5:1 against its background                                                                            |
| 3.3.1 Error Identification                | A     | Errors are described in text, not only by color                                                                         |
| 3.3.2 Labels or Instructions              | A     | Every field has a visible label                                                                                         |
| 3.2.6 Consistent Help                     | A     | Help links or contact details sit in the same place on every page                                                       |
| 3.3.7 Redundant Entry                     | A     | People aren't asked to retype what they already entered in the same flow                                                |
| 3.3.8 Accessible Authentication (Minimum) | AA    | Sign-in doesn't depend on memorizing or transcribing a code without an alternative, such as paste or a password manager |

Automated scanners help, but the W3C says evaluation tools [can't determine accessibility](https://www.w3.org/WAI/test-evaluate/tools/selecting/), only assist, so test the tasks with a keyboard and a screen reader. Our free [WCAG 2.2 checklist](https://dardo.studio/en/tools/wcag-2-2-checklist/) lists every Level A and AA criterion; for full conformance, see what an [accessibility audit costs](https://dardo.studio/en/blog/website-accessibility-audit-cost/).

### 6\. Content and copy

Most failed tasks on marketing sites are content failures: the visitor can't tell what you offer, what it costs or what happens next.

| Check                                                              | Red flag                                                               |
| ------------------------------------------------------------------ | ---------------------------------------------------------------------- |
| The first screen says what it is, who it's for and what to do next | A slogan that could belong to any company                              |
| Navigation labels match what visitors search for and say           | Internal jargon; labels that only make sense once you know the product |
| Prices, or how pricing works, are findable from the task's start   | "Contact us" as the only answer to "how much"                          |
| Calls to action say what happens                                   | "Submit" and "Learn more" everywhere                                   |
| Terms stay consistent between pages, emails and the product        | The same feature with three names                                      |
| The questions support and sales hear are answered on the page      | The same question in every week's tickets                              |
| Error, empty and confirmation messages say what to do next         | Dead ends after a form, a search or a failed payment                   |

### 7\. Performance

Slow pages fail tasks before anyone reads them. Check field data for the templates the tasks use against Google's [Core Web Vitals](https://web.dev/articles/vitals) thresholds, at the 75th percentile of visits:

- **Largest Contentful Paint** within 2.5 seconds
- **Interaction to Next Paint** of 200 milliseconds or less
- **Cumulative Layout Shift** of 0.1 or less

If a template fails, our playbook on [improving Core Web Vitals](https://dardo.studio/en/blog/pass-core-web-vitals/) covers the fixes, and our [platform speed report](https://dardo.studio/en/tools/website-platform-speed-report/) shows how sites on each platform score with real users.

## How to prioritize the findings

A raw findings list is a to-do list nobody finishes. Score each finding on three things, and keep them separate so you don't count the same thing twice.

**Severity** uses NN/g's 0 to 4 scale from [severity ratings for usability problems](https://www.nngroup.com/articles/how-to-rate-the-severity-of-usability-problems/):

- 0: not a usability problem
- 1: cosmetic, fix only if time allows
- 2: minor, low priority
- 3: major, high priority
- 4: catastrophe, fix before release

NN/g builds severity from a problem's frequency, its impact and its persistence, plus its market impact. Because analytics measures frequency directly, rate severity on impact and persistence, and take frequency from the data.

**Reach** is the share of sessions or accounts that get to the step, from your funnel. **Value** is what the task is worth to the business: an illustrative scale is 3 for a revenue task (checkout, demo request), 2 for activation or retention, 1 for everything else.

Priority = severity × reach × value. Here's how four hypothetical findings sort:

| Finding                                                       | Severity | Reach | Value | Score |
| ------------------------------------------------------------- | -------- | ----- | ----- | ----- |
| Card errors on checkout are shown only at the top of the page | 4        | 30%   | 3     | 3.6   |
| Pricing hidden two clicks from the homepage                   | 3        | 60%   | 3     | 5.4   |
| Teammate invite needs the exact email domain                  | 3        | 15%   | 2     | 0.9   |
| Inconsistent button styles on blog pages                      | 1        | 40%   | 1     | 0.4   |

Then add an effort estimate and sort high-score, low-effort items to the top. A severity-4 problem in a release-critical flow gets fixed regardless of its score.

## What a UX audit should deliver

- **The scope**: user groups, tasks, devices and methods, agreed before the work started
- **A findings log**: one row per finding, with where it happens, the evidence (clip timestamp, funnel numbers or the heuristic it breaks), severity, reach, value and a recommended change
- **Annotated screens** showing each problem and the proposed fix
- **Highlight clips** from the usability tests, a few minutes each, for the people who weren't there
- **A prioritized plan**: fix now, next and later, with effort estimates
- **A readout** with the team that will make the changes
- **The raw material**: recordings, notes and analytics exports, so the next audit can compare

Push back on a report that lists generic best practices without evidence from your own users, or scores screens without saying which tasks were tested.

## What UX audits cost: published prices

Few providers publish a price for a UX audit; most quote after a call. These are the published prices we could read on 17 October 2026.

| Provider                                                                                       | What's sold                                                           | Published price                                                                                                                   |
| ---------------------------------------------------------------------------------------------- | --------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------- |
| [Convertica](https://www.convertica.org/pricing/)                                              | Automated conversion audit of a page in its app                       | Free audit; USD 27 for the full report                                                                                            |
| [Upwork](https://web.archive.org/web/20260710143037/https://www.upwork.com/hire/ux-designers/) | Typical marketplace ranges it publishes (as archived on 10 July 2026) | Basic UX audit, heuristic evaluation and written report: USD 500–1,500 a project; UX designers typically charge USD 25–39 an hour |
| [Baymard Institute](https://baymard.com/pricing)                                               | Ecommerce UX research for self-assessment                             | USD 2,400 a year (Foundation) or USD 4,200 a year (Expansion), for 3 users                                                        |
| [Baymard Institute](https://baymard.com/solutions/ux-audit-deepdive)                           | Manual heuristic audit of an ecommerce site                           | Not published; the report arrives in about 15 days                                                                                |
| [Nielsen Norman Group](https://www.nngroup.com/consulting/expert-review/)                      | Expert design review                                                  | From USD 60,000 for one site or app, USD 70,000 for several, USD 80,000 for a competitive review against three competitors        |

The spread reflects scope more than skill. An automated report reads one page; a marketplace audit is usually one person's heuristic review; NN/g's price buys senior researchers, several products or competitors, and a full report. None of these prices includes usability testing with recruited participants unless the provider says so.

What moves a quote: the number of tasks and user groups, whether there are test rounds and how many, recruiting and incentives, whether the product sits behind a login with roles and test data, and the languages. Dardo's [UX audit](https://dardo.studio/en/services/ux-audit/) is quoted per scope, without a published starting price.

## A do-it-yourself UX audit for a small team

The cash cost is small; most of the effort goes into recruiting, sessions and analysis. These are the tools and recruiting services, at prices published on 17 October 2026.

| Need                           | Option                                                                       | Published price                                                                                             |
| ------------------------------ | ---------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------- |
| Heatmaps and recordings        | [Microsoft Clarity](https://learn.microsoft.com/en-us/clarity/faq)           | Free, with no traffic limits                                                                                |
| Heatmaps and recordings        | [PostHog](https://posthog.com/pricing)                                       | 5,000 recordings a month free; free-plan recordings kept for one month                                      |
| Heatmaps and recordings        | [Hotjar, now sold through Contentsquare](https://contentsquare.com/pricing/) | Free plan with up to 200k monthly sessions and one month of data; Growth from USD 39 a month, billed yearly |
| Recruiting participants        | [Respondent](https://www.respondent.io/pricing)                              | USD 40 per consumer session, USD 80 per B2B session, pay as you go; incentives extra                        |
| Recruiting participants        | [User Interviews](https://www.userinterviews.com/pricing)                    | From USD 49 per session, pay as you go; incentives extra, plus a 3% fee if it pays them out                 |
| Moderated sessions             | [Lookback](https://www.lookback.com/pricing)                                 | USD 299 a year for 10 sessions; bring your own participants free, or recruit through it for USD 49 each     |
| Unmoderated tests with a panel | [Userbrain](https://www.userbrain.com/pricing)                               | USD 49 a month for 3 testers; USD 249 a month for 10                                                        |

A worked budget for one round of five moderated consumer sessions: Clarity at no cost, five sessions recruited through Respondent at 5 × USD 40 = USD 200, and Lookback's USD 299 plan, which also covers a second round. That's USD 499 before incentives, which you set yourself. A second round of five adds USD 200 in recruiting, for USD 699 in total. If your own customers will join a call, recruiting costs nothing but your time.

The steps:

1. Agree the user groups and three to six tasks, using the scoping list above.
2. Build one funnel per task and note the worst step for each.
3. Three people run the heuristic review separately, then merge their findings; NN/g's article on heuristic evaluation links a fillable workbook.
4. Watch recordings of sessions that reached each worst step.
5. Run five usability sessions, fix what's clearly broken, then run five more.
6. Check the tasks against the accessibility, content and performance tables.
7. Log every finding with its evidence, score it and agree the top five fixes with whoever will build them.
8. Re-test the fixed tasks, and compare the funnel a month later.

The weak point of a DIY audit is distance: the people who designed the screens are the least able to see their problems. Bring in at least one evaluator from outside the team, even a colleague from sales or support.

## When to bring someone in

Hire help when nobody on the team is independent of the design, when the product sits behind a login with several roles, when the audience is hard to recruit, such as clinicians or procurement managers, or when you need the findings to settle an internal argument. If you already know what's broken and have the traffic to test changes, [conversion rate optimization](https://dardo.studio/en/services/conversion-rate-optimization/) is the better spend; if the findings point to a missing flow rather than a fix, that's [product design](https://dardo.studio/en/services/product-design/) work.

To run it yourself, start with the scoping list and the seven tables above. If you'd rather have Dardo run it, our [UX audit](https://dardo.studio/en/services/ux-audit/) page explains how we scope and test, and a [website redesign checklist](https://dardo.studio/en/blog/website-redesign-checklist/) helps when the audit points to a bigger change.

## Common questions

**What is included in a UX audit?**

A scoped list of user groups and tasks, then a heuristic review by several evaluators, funnel analysis in your analytics, session recordings and heatmaps, usability tests with about five people per round, and checks of accessibility, content and page speed on those tasks. The output is a findings log with evidence, severity and a recommended change for each problem, annotated screens and a prioritized plan.

**What is the UX audit process?**

Agree the user groups and the three to six tasks that matter most for each. Build a funnel per task to find the worst steps, run an independent heuristic review with three to five people, watch recordings of sessions at those steps and test the tasks with real users. Then log each finding with its evidence, score it by severity, reach and value, fix the top items and re-test.

**How much does a UX audit cost?**

Published prices we read on 17 October 2026 ranged from a free automated audit with a USD 27 full report at Convertica, to USD 500 to 1,500 for a basic audit in Upwork's published ranges, to USD 60,000 and up for a Nielsen Norman Group design review. The price follows the number of tasks and user groups, test rounds, recruiting and whether the product sits behind a login. A small team can run its own round of five tests for about USD 500 in tools and recruiting, plus incentives.

**How many users do you need to test in a UX audit?**

About five per round for one user group, following Nielsen Norman Group's guidance: Nielsen's model estimates five users find about 85% of usability problems, and three rounds of five beat one round of 15. With two distinct groups, test three or four people from each. If you need a metric such as a task success rate, NN/g puts the appropriate number for most quantitative studies at 40.

**What is the difference between a UX audit and a heuristic evaluation?**

A heuristic evaluation is one method inside a UX audit: experts judge the interface against usability principles such as NN/g's 10 heuristics. A UX audit adds evidence from real behavior, analytics, recordings and usability tests, plus accessibility, content and performance checks. NN/g says a heuristic evaluation can't replace user research, which is why an audit combines them.

**Is a UX audit the same as an accessibility audit?**

No. A UX audit checks whether people can complete key tasks and includes the accessibility checks that affect those tasks, such as keyboard use, focus and target size. An accessibility audit tests every template against each WCAG success criterion to establish conformance, which a UX audit doesn't. If you need conformance for a contract, policy or complaint, scope an accessibility audit separately.

## Sources & further reading

Sources behind this page, with further detail from the original publishers.

- [Nielsen Norman Group: 10 Usability Heuristics for User Interface Design](https://www.nngroup.com/articles/ten-usability-heuristics/) · nngroup.com
- [Nielsen Norman Group: How to Conduct a Heuristic Evaluation](https://www.nngroup.com/articles/how-to-conduct-a-heuristic-evaluation/) · nngroup.com
- [Nielsen Norman Group: Why You Only Need to Test with 5 Users](https://www.nngroup.com/articles/why-you-only-need-to-test-with-5-users/) · nngroup.com
- [Nielsen Norman Group: How Many Participants for Quantitative Usability Studies](https://www.nngroup.com/articles/summary-quant-sample-sizes/) · nngroup.com
- [Nielsen Norman Group: Severity Ratings for Usability Problems](https://www.nngroup.com/articles/how-to-rate-the-severity-of-usability-problems/) · nngroup.com
- [Nielsen Norman Group: Expert Review consulting and pricing](https://www.nngroup.com/consulting/expert-review/) · nngroup.com
- [W3C: Web Content Accessibility Guidelines (WCAG) 2.2](https://www.w3.org/TR/WCAG22/) · w3.org
- [W3C WAI: What's New in WCAG 2.2](https://www.w3.org/WAI/standards-guidelines/wcag/new-in-22/) · w3.org
- [web.dev: Web Vitals](https://web.dev/articles/vitals) · web.dev
- [PostHog: Pricing](https://posthog.com/pricing) · posthog.com
- [Microsoft Learn: Clarity FAQ](https://learn.microsoft.com/en-us/clarity/faq) · learn.microsoft.com
- [Contentsquare: Pricing (Hotjar plans)](https://contentsquare.com/pricing/) · contentsquare.com
- [Respondent: Pricing](https://www.respondent.io/pricing) · respondent.io
- [User Interviews: Pricing](https://www.userinterviews.com/pricing) · userinterviews.com
- [Lookback: Pricing](https://www.lookback.com/pricing) · lookback.com
- [Userbrain: Pricing](https://www.userbrain.com/pricing) · userbrain.com
- [Baymard Institute: Pricing](https://baymard.com/pricing) · baymard.com
- [Baymard Institute: UX Audit Deepdive](https://baymard.com/solutions/ux-audit-deepdive) · baymard.com
- [Upwork: Hire UX designers, typical costs (archived 10 July 2026)](https://web.archive.org/web/20260710143037/https://www.upwork.com/hire/ux-designers/) · web.archive.org
- [Convertica: Conversion rate optimization pricing](https://www.convertica.org/pricing/) · convertica.org

[Nicolás Cerón](https://dardo.studio/en/nicolas-ceron/)

Nicolás Cerón is the founder of Dardo, a brand, web design and development studio in Bogotá, Colombia.

## Related articles

- [**How much does a website accessibility audit cost? Published prices, cost drivers and how to compare quotes**Vendors that publish prices put most accessibility audits between USD 1,250 and 8,000. What moves the quote, the 2026 ADA dates and how to compare proposals.](https://dardo.studio/en/blog/website-accessibility-audit-cost/)
- [**PostHog vs Google Analytics: which one a marketing site or SaaS product needs, and when to run both**GA4 links to Google Ads and Search Console; PostHog adds replay, feature flags and experiments. Which one you need, what each costs and how to run both.](https://dardo.studio/en/blog/ga4-vs-posthog/)
- [**How to improve Core Web Vitals: a field-data-first playbook for marketing sites**Find the failing metric and template in Search Console, fix LCP, INP and CLS by their cause, then confirm the result in field data about 28 days later.](https://dardo.studio/en/blog/pass-core-web-vitals/)
- [**How much does it cost to build a web app in 2026? Published prices, hourly rates and a worked estimate**A first web app costs from about USD 8,000 for one workflow to USD 50,000+ for an MVP with accounts and payments. Published prices, rates and the arithmetic.](https://dardo.studio/en/blog/web-app-development-cost/)

## Keep exploring.

- [Service · **UX audit: find what stops visitors and users, ranked by impact**](https://dardo.studio/en/services/ux-audit/)

- [Your project · **Start a conversation**](https://dardo.studio/en/contact/)
