Inspect the control in context
Open the page and locate the button, link or field. Establish what a reasonable action should do: navigate, reveal content, submit or change a selection. A click without navigation can be correct for a tab or an expand button.
Review the observed response
Look at the next page and safe interaction metadata. Repeated clicks may indicate a mismatch, but can also be ordinary selection behavior or impatience during a slow response. Verify the implementation before calling a control broken.
Separate form stages
Check whether visitors reach the form, change fields and encounter invalid states. A field touched near the end of a visit is worth investigating only with enough context. Typed values are not needed to compare safe progression signals.
Check privacy and coverage
Private regions should be masked or excluded. Third-party iframes and external authentication flows may not be visible. A missing event can mean missing coverage rather than a visitor failure. Verify the instrumentation before proposing UX changes.
Write a narrow hypothesis
Example: “Readers may miss the installation link after the quick start.” Test a clearer next-step link. Do not state “Readers are confused” unless you have separate evidence. Name the observation, possible explanation, proposed change and measurable outcome.
Continue the workflow
Inspect your own website’s behavior.
Connect your site, confirm incoming visits, and choose a goal worth measuring.
Start tracking your site