How to do a UX audit of your website in one afternoon
By the Site Roast team · November 13, 2026 · 4 min read
Short answer: a UX audit is a structured review of how easy your website is to use for the people it's meant for. For a small site you can do a useful one in an afternoon: write down the one or two goals visitors should complete, walk those journeys on a phone and a laptop, check each page against a short list (clarity, navigation, calls to action, forms, trust, accessibility, speed), note every problem with a screenshot, then rank fixes by impact and effort. The output is a short list of changes, not a 50-page report.
Before you start: goals and visitors
Write two sentences:
- Who visits (for example, "homeowners in our city with a broken boiler, usually on a phone").
- What they should be able to do ("call us or book a visit within a minute").
Every check below is judged against those sentences.
Step 1: walk the main journeys
Use a real phone, not a resized browser window. Start from where visitors really arrive (search results, an ad, a social post) and try to complete the goal. Time yourself and note every hesitation: "Where's the price?", "Is this the booking button?", "Why did the page jump?". Then repeat on a laptop.
Step 2: check the first screen of key pages
For the home page and your main landing pages:
- Does the headline say what you offer and for whom?
- Is there one obvious primary action, visible without scrolling on a phone?
- Is there a reason to trust you near that action?
See what belongs above the fold.
Step 3: navigation and structure
- Can a first-time visitor find the 3–5 things they come for from the menu?
- Are labels in plain words ("Prices", not "Investment")?
- Do page titles describe each page? Google's SEO Starter Guide recommends titles that are unique to the page, clear and concise, which also helps people with many tabs open.
- Is there a way back to the home page and a visible contact option everywhere?
Step 4: calls to action and forms
- One primary action per page; button text says what happens.
- Forms ask only for what's needed, label every field, show errors clearly next to the field, and work with the phone keyboard (email and phone fields open the right keyboard).
- After sending, people see a clear confirmation and what happens next.
Step 5: content and trust
- Prices, availability, delivery or response times: are they stated where people decide?
- Reviews, logos, guarantees, real photos: present, current and true?
- Is the tone consistent and free of jargon?
Step 6: accessibility basics
Accessibility issues are usability issues for everyone.
- Contrast: the W3C's WCAG asks for at least 4.5:1 contrast for normal text and 3:1 for large text. Light grey on white often fails.
- Text size and tap targets: readable without zooming, buttons large enough to tap.
- Images: meaningful images need alt text.
- Keyboard: can you reach and use every link and button with the Tab key, with a visible focus outline?
Step 7: speed and stability
Slow or jumpy pages feel broken. web.dev's Core Web Vitals give "good" targets: Largest Contentful Paint within 2.5 seconds, Interaction to Next Paint at 200 milliseconds or less, Cumulative Layout Shift at 0.1 or less, measured at the 75th percentile of page loads. Compress big images, limit third-party scripts and reserve space for images and embeds.
Step 8: prioritise
Put every issue in a table and score it:
| Issue | Impact (1–3) | Effort (1–3) | Priority |
|---|---|---|---|
| Book button below the fold on mobile | 3 | 1 | Do now |
| Contact form has 11 fields | 3 | 1 | Do now |
| Hero image 2.4 MB | 2 | 1 | Do now |
| Menu labels unclear | 2 | 2 | Next |
| No reviews on service pages | 2 | 2 | Next |
High impact, low effort first. Then re-test the journeys after each batch of fixes.
Common mistakes
- Auditing only on a laptop.
- Listing opinions instead of problems. "I don't like the font" isn't a finding; "body text is 13 px and hard to read on a phone" is.
- No screenshots. Your designer needs to see exactly what you mean.
- Fixing everything at once. Batch, ship, re-test.
- Skipping real users. Five people trying your main task will find more than any checklist.
FAQ
How long does a UX audit take? For a small site, an afternoon for the review and an hour to prioritise. Larger sites take days.
Do I need tools? A phone, a laptop, your analytics and a spreadsheet are enough. Automated checks help for speed and contrast.
How often should I audit? After big changes and at least once a year.
Start with an automated pass
Site Roast gives you a first pass in a minute: desktop and phone screenshots, a technical check, five scores and the fixes in order. Related: website redesign checklist.
Get your site roasted
Scores, fixes and a redesigned hero for any page. Free in a minute.
Roast my siteSources
- W3C, Understanding SC 1.4.3: Contrast (Minimum) (read 13 Nov 2026)
- web.dev, Web Vitals (read 13 Nov 2026)
- Google Search Central, SEO Starter Guide (read 13 Nov 2026)