Critique a screen by what the user must do

Review [SCREENSHOT OR UI DESCRIPTION] against [PRIMARY USER TASK]. Trace where a first-time visitor looks, what action they can identify, what information they need before acting, and how the screen behaves on a phone. If a screenshot or live page is available, list five observations with visual evidence, not taste words. For a text description only, label observations description-supported and list the visual checks still needed. Propose two alternative layouts with control hierarchy, empty state, error state and accessibility notes. Return a small text wireframe and a verification checklist. If no screenshot or live page is provided, mark visual conclusions as unverified rather than implying an inspection. Do not assume attractive colours compensate for a broken journey.