Large images can dominate a small website's page transfer. A photograph that looks attractive in a design file may be far larger than the space it occupies on a phone. An image budget gives the team a practical target and a way to review tradeoffs. There is no single file-size limit that fits every image and audience.
Start with the purpose of the image
Ask what the image helps the visitor understand. A product detail may need a zoomable high-resolution version; a decorative background usually does not. Remove images that add download weight without adding useful information. Keep meaningful alternative text where appropriate and do not put essential copy only inside a picture.
Match dimensions to the layout
Check the largest displayed size and provide suitable variants for different screens when the site supports them. Uploading a very large source file and merely displaying it smaller does not necessarily reduce the downloaded bytes. Preserve a master copy separately, then create delivery versions rather than repeatedly compressing the only original.
Compare quality at the actual display size
Try an appropriate modern format and compression setting, then inspect the result on real page backgrounds. Look at text, sharp edges and faces rather than judging only by file size. Some assets are better served as vectors, while photographs typically need raster formats. Use the smallest version that preserves the necessary detail for its job.
Estimate the traffic implication
If a page transfers an average of 1.5 MB and receives 10,000 views, a simple estimate is 15 decimal GB before any planning margin. That is a model of browser transfer, not necessarily the hosting bill. Caching, third-party assets, repeat visits and bots can change the relationship. Use our page transfer estimator for scenarios and compare with observed usage later.
Test the complete page
Measure the page after images, scripts and fonts are included. A single optimised image cannot compensate for unnecessary video or repeated large assets. Check mobile behavior and avoid loading below-the-fold media earlier than needed when the implementation allows it. Confirm that delayed images do not make the layout jump unexpectedly.
Make the budget part of publishing
Write a short upload checklist: dimensions checked, delivery format chosen, visible quality reviewed and alternative text considered. Recheck the page after publication. Store originals securely outside public content when they contain unnecessary metadata or are not intended for download. A repeatable publishing habit is more useful than a one-time optimisation exercise.