Preparing website images means balancing visual usefulness with the amount of data a visitor must download. Start with the role of the image: a product detail, a tutorial screenshot, and a decorative background need different treatment.
Keep an untouched original. Work on a copy so a later design change does not force you to enlarge an already reduced image.
Choose the content before the compression
Check whether the image contributes something. A screenshot should show the relevant controls clearly. A product photo should represent the actual item. A decorative image should not crowd out the information the visitor came to read.
Confirm permission to use the image and record its source. Download availability alone does not establish reuse rights.
Crop for the intended placement
Use the layout’s intended shape as a starting point. Keep important details away from edges that may be cropped on smaller screens.
For an illustrative article header, test both a wide desktop view and the narrower mobile presentation. A face, label, or key control at the extreme edge may disappear.
Do not crop a chart so that its scale or explanatory labels become misleading.
Resize to a sensible delivery size
Inspect how large the image is displayed in the actual layout. Prepare an appropriately sized version rather than sending a full camera-resolution file for a small content area.
Responsive image delivery can offer different files for different conditions. Google’s web.dev image course explains formats, compression, and responsive delivery in more detail.
Do not assume the visible size alone tells you which file the browser downloads. Test the actual page.
Compare compression visually
Export a candidate, compare it with the original at its intended display size, and inspect important edges and text.
Look for blurred labels, banding in smooth backgrounds, and damaged fine detail. A small file is not useful if readers cannot understand it.
Choose the format based on the image and the tools serving it. Keep transparency where it matters, and check that the chosen format works in the actual publishing workflow.
Name and describe the image accurately
Use a descriptive filename before uploading, such as “website-plan-notebook.jpg,” rather than a long camera identifier.
Write alt text according to the image’s purpose in context. For a meaningful photo, describe the relevant visible information. For a decorative image, an empty alternative may be appropriate. Avoid inserting keywords that do not describe the image.
A screenshot with important instructions may need a nearby text explanation as well.
Verify after upload
Open the page on a phone and a larger screen. Check crop, clarity, dimensions, caption, and loading behavior.
If an optimization plugin creates additional files, verify that it has not changed colors, removed needed transparency, or made screenshots unreadable.
Record the source file and preparation choices for important reusable images. Your goal is an image that communicates clearly in the finished page, not simply one that achieves the smallest possible byte count.
