Check whether the outcome improved
Replay cold and cached image loads
Use the original route, viewport, connection, account state, and asset conditions. Record request bytes, response completion, decode, paint, first useful content, and control readiness for cold and returning runs. Keep image count and order visible so one removed request is not mistaken for an optimization.
Inspect visual and layout integrity
Compare crop, sharpness, focal content, aspect ratio, reserved space, text contrast, and layout movement with the baseline. Check alternative text and decorative treatment in assistive output. Exercise narrow and wide layouts because a reduction appropriate for one viewport may harm another.
Exercise the first action and failure path
Use the delayed control while images load, fail, or arrive late. Confirm the action remains understandable, errors are recoverable, and missing imagery does not leave an unexplained blank. Check caching and repeated navigation for duplicate downloads or a layout shift introduced by the new asset path.
What to carry forward
Classify the image change as improved, regressed, unchanged, or inconclusive with byte, timing, visual, and accessibility evidence attached. It passes only when the intended action is usable sooner and the image retains its required meaning across the tested viewports and cache states.
Keep the decision with the work.
Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.
Create an account See the product workflow