Guide6 min readUpdated
UX Audit Checklist: Review Your App or Website Yourself
Use this UX audit checklist to review your website or app yourself: first impression, navigation, forms, speed, trust and accessibility, in plain language.
By Tithi Mondal, UI/UX Designer
What a UX audit is
A UX audit is a careful review of how easy your product is to use. The aim is to find the places where real people get confused, slow down or leave, and to list them in order of importance.
Professionals often use a method called heuristic evaluation, which means checking the product against well-known rules of good usability, such as "the user should always know where they are" and "error messages should explain how to fix the problem". You can borrow the same idea without any training. The checklist below turns those rules into plain questions.
A self-run audit will not replace testing with real users, but it finds many obvious problems for free. If your product is an app, this works as an app UX audit. If it is a site, it works as a website usability audit. The questions are mostly the same.
Before you begin
Set yourself up properly. It takes ten minutes and changes what you notice.
- Pick your top three journeys. For example: a new visitor becomes an enquiry; a customer places an order; a seller lists a product.
- Use a real phone. Preferably a mid-range Android on mobile data, not your office laptop on fast wifi.
- Pretend to be new. Log out, clear history if you can, and try as someone who has never seen the product.
- Keep a list. For each problem write: where, what, and how bad.
The UX review checklist, area by area
There are six areas. Spend the most time on the ones closest to money.
Area 1: First impression
The first five seconds decide whether people stay.
- Can a stranger say what you do within five seconds of landing?
- Is there one clear main action, such as "Book a call" or "Order now"?
- Is the language simple, and is it the language your customers use?
- Does the page load something useful before everything finishes loading?
- Is there anything that looks broken, such as overlapping text or missing images?
Area 2: Navigation and structure
People should always know where they are and how to get back.
- Can you reach the most important pages in two or three taps?
- Are menu labels words your customers use, not internal terms?
- Is there a visible way to go back, and does the back button on the phone behave sensibly?
- Is search available where it is needed, and does it handle spelling mistakes and Hinglish?
- On a website, is the same menu on every page?
- If you have different user roles, does each one see only what is relevant?
Area 3: Content and wording
Good wording removes more friction than good graphics.
- Are button labels specific? "Pay 499 rupees" is clearer than "Submit".
- Are headings clear about what is below them?
- Is any text longer than it needs to be?
- Do regional language versions look correct, with no cut-off text or mixed scripts?
- Are prices clear, with taxes and delivery shown before the last step?
- Do empty screens explain what to do next?
Area 4: Forms, signup and checkout
This is where money is usually lost, so spend the most time here.
- Count the fields. Remove every field you do not truly need.
- Check the keyboard. Phone number fields should open the number pad, email fields should open the email keyboard.
- Is OTP handling smooth? Can the code be pasted or read automatically, and is there a clear resend option?
- Are error messages placed next to the problem and written in plain language?
- Is UPI offered early and easily at payment, since most Indian customers expect it?
- Does the user keep their data if they go back or the connection drops?
- After payment or submission, is there a clear confirmation?
- Can someone complete the journey without creating an account, if that makes sense for your product?
Area 5: Speed and mobile experience
Most Indian traffic is on mobile, and many users have budget phones and patchy signals.
- Does the first screen appear quickly on mobile data?
- Are images compressed, so they are not heavy for nothing?
- Are tap targets large enough for a thumb, and spaced so that you do not hit the wrong one?
- Is text readable without zooming?
- Does anything jump around while the page loads?
- Does the product behave sensibly with a weak signal or offline?
- Is anything fixed to the screen, like a banner, covering important content?
Area 6: Trust and accessibility
People need to feel safe, and everyone should be able to use the product.
- Is your business name, address or contact information easy to find?
- Are there real photos, real reviews or real examples, not only stock images?
- Are refund, privacy and delivery policies written in plain language and easy to reach?
- Is the text contrast strong enough to read in sunlight?
- Is font size comfortable?
- Do images that carry meaning have text descriptions, and does colour never carry meaning alone? A red error should also have words.
- Can the product be used with large text settings turned on in the phone?
For more on designing for local users, my article on designing apps for Indian users goes deeper on language, payments and devices.
How to rank what you find
You will find more problems than you can fix. Rank each one using two questions.
| Question | Why it matters |
|---|---|
| Does it block an important journey? | Blockers come first |
| How many users does it affect? | Common problems beat rare ones |
| How easy is it to fix? | Quick wins build momentum |
Then sort into three piles: fix this week, fix this month, and later. A good first target is the blockers in forms and checkout.
What a self-audit cannot do
Be honest about the limits. You know your product too well, so some problems will be invisible to you. You may also defend decisions you made yourself. To balance that, ask two or three people who have never used the product to attempt your top journey while you watch. My guide to usability testing on a small budget gives a script for doing that.
If the audit shows deep structural problems, the product may need a redesign instead of small fixes. Signs your website needs a redesign can help you decide.
When to ask a designer
Ask for help when you have audited and fixed the obvious issues but conversions are still weak, when a problem repeats across many screens, or when you plan a larger redesign. A designer can turn your list into screens and a clear plan.
If you would like a second pair of eyes on a website or app, you can see how I work on UI/UX design, or write to me through the contact section.
Frequently asked questions
What is the difference between a UX audit and usability testing?
A UX audit is an expert-style review of the product against good practice, done without users. Usability testing watches real people use it. The two work best together.
How long does a UX audit take?
A self-run audit of your top three journeys can take a few hours. A thorough audit of a large product takes longer because there are more screens and roles to check.
What is a heuristic evaluation?
It is a method where a reviewer checks a product against recognised usability principles, such as clear navigation, helpful error messages and consistency. The checklist above is a plain-language version of it.
How often should I audit my website or app?
Run a light check every few months and after any big change. Also audit before a redesign, so you know what to keep and what to fix.