Decide where the work belongs
Rank the first action delayed
Name the control or decision that waits for the page and identify whether the image is required to understand it. A large hero image that delays a form deserves different treatment from a heavy image below the action. Include whether content remains usable while the image waits.
Group impact by viewport and asset
Compare image cost across narrow and wide layouts, cold and returning cache, and common connection profiles. Group by stable asset, displayed dimensions, and route. Mark confirmed reach separately from lab-only cases, especially when an image is visible only in one layout.
Choose one bounded image queue slice
Select immediate investigation, an asset or loading-order improvement, or evidence collection for one missing viewport. State the visual fidelity and accessibility evidence required to advance. Avoid a broad image cleanup when one above-action asset explains the blocked work.
What to carry forward
Produce a queue decision tied to the delayed action, visual role, confirmed reach, and evidence quality. Include whether the issue is a regression or a scale cost. The next engineer should have one asset and viewport to inspect plus a clear reason its work belongs now.
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