UX audit report · example.com · 26 Oct 2026

Experience audit

Your page is in good shape. We checked 31 things and found 4 to change. None of them is critical.

31Things checked10 more need a person to look at them

4Issues found27 checks passed

Critical0Fix now

Major1Fix soon

Minor2Fix when you can

Cosmetic1Nice to fix

Your score

87/100

Goodexample.com

Fix these first

4 fixes, in the order they are worth doing

Ranked by how serious each one is, whether a visitor would notice it, and how much your goal cares about its area.

01No navigation region on the pageInformation architecture & navigationUnder an hourMajor
02Target size below minimumAccessibilityUnder an hourCosmetic
03Missing or duplicate h1Information architecture & navigationMinutesMinor
04Landmark regions missingInformation architecture & navigationMinutesMinor

01MajorIssue 1 of 4

MeasuredPrimary navigation is present and distinctApple HIG and Material navigation patterns1 placeUnder an hour to fix

Issue: The page offers no navigation region.
Impact: Without navigation, every page is a dead end and the only way on is the browser’s back button.
Solution: Wrap the primary destinations in <nav aria-label="Main">. Keep it in the same place on every page.

02CosmeticIssue 2 of 4

MeasuredTargets are big enough to hitWCAG 2.2 AA 2.5.8 (44pt iOS / 48dp Android as platform norms)1 placeUnder an hour to fix

Issue: 80×21px, against at least 44×44px (recommended).
Impact: Small targets cause mis-taps, and mis-taps on a destructive or commercial control cost money.
Solution: Increase to min 44x44 via padding (not margin), keeping the visual icon size unchanged.

03MinorIssue 3 of 4

MeasuredThe heading outline is logicalWCAG 2.2 AA 1.3.11 placeMinutes to fix

Issue: 0 h1 on the page, against exactly 1 h1.
Impact: Screen-reader users navigate by heading. A broken outline makes the page impossible to skim.
Solution: Promote body > p:nth-of-type(1) to h1 with text matching the page's primary purpose.

04MinorIssue 4 of 4

MeasuredLandmarks and a skip link are presentWCAG 2.2 AA 2.4.11 placeMinutes to fix

Issue: No <main> or role="main", against one <main> landmark.
Impact: Without them, every keyboard user tabs through the whole menu before reaching the content, on every page.
Solution: Wrap primary content in <main id="main">, navigation in <nav>, and use <header>/<footer> for their regions.