The playbook
Website Image Optimization: Checklist
Use this website image optimization checklist before a new release, a handoff, or a scheduled review. Its purpose is to verify the decisions that affect image weight on important pages. Check an actual page or interaction record; a box marked complete without evidence does not show that the customer journey works.
Put the task in context
Export screenshots near the sizes at which they will display and verify that interface text remains legible. Reserve dimensions in the layout. Compression that removes useful detail may reduce file size while making the image fail its explanatory purpose.
Before you use the checklist
Name the exact item being checked and its purpose. Gather asset, display size, file size, format. If one of those details is unknown, mark it as unknown and assign a way to resolve it. An invented value makes the checklist look complete while weakening every later decision.
Working checklist
| Check | Evidence to keep | Responsible role |
|---|---|---|
| Choose suitable dimensions formats and compression | A dated observation showing how asset was verified | website lead |
| Reserve image space to avoid visible layout movement | A dated observation showing how display size was verified | designer or developer |
| Check clarity at actual display sizes | A dated observation showing how file size was verified | site owner |
Check the failure path
- Look specifically for this failure: uploading huge source images to small thumbnail slots.
- Export responsive sizes and inspect visual quality on devices. Record the actual correction, not just the intention to make it.
- Repeat the affected task after the correction and check format.
- Make sure the next owner can find the decision and supporting evidence.
Use three outcomes for each check
Mark an item as complete only when the expected behavior or information has been observed. Mark it as incomplete when a required condition is absent. Use not applicable when the condition genuinely does not belong to the chosen scope, and write a short reason. These states keep a review useful without forcing every process into an identical mold.
For example, if the check is “Choose suitable dimensions formats and compression,” a meeting about the subject is not the evidence itself. Retain the relevant asset and display size, the decision made from them, and the result of checking that decision. The record should allow someone who missed the meeting to understand what changed.
Decide what must be resolved first
An incomplete item that prevents deliver useful visual assets without unnecessary weight or layout disruption deserves attention before a cosmetic improvement. Assign an owner and a next action to that issue. Keep optional refinements visible, but do not let them obscure a failure in the core process.
Close the review
Recheck corrected items and note anything still uncertain. The checklist is finished when the next owner understands what was verified and what remains open. Follow image weight on important pages using a consistent definition so later reviews can connect execution quality with useful results.
Keep the page’s main task visible when adding helpful detail. Supporting information should reduce uncertainty at the decision point. If a section introduces a second unrelated offer, decide whether it belongs on another page.
Skip the manual steps. Let AgentixHUB run this for every client.
Start now