The property page contains numerous high-resolution photos. On the office computer it opens without issue, on a mobile device interested parties wait a long time for the gallery. The team therefore wants to “make all images small”. However, that could also cause the large view to lose the details that are important for the property.
The following procedure is a limited assignment for in-house property pages in Austria and Germany. It does not replace a technical measurement of the actual website. No specific speed value is claimed as a general quality threshold.
Distinguish the different presentations of the image
A motif can occur as a small preview, as an image on the detail page and as an enlarged view. These places do not necessarily have the same requirements. In the fictional example the preview image should make the rooms recognisable; only the opened large view shows a specific equipment area in more detail.

For selected motifs, record which image information is actually needed in which place. The unmodified original file remains available as a working source. A large file alone does not prove a good presentation; a small file alone does not yet prove sufficient informational content.
Determine the source actually delivered
The technical team checks which file the browser actually requests under the specified conditions. Mere optical reduction on the screen does not answer this question.
web.dev explains that `srcset` can provide different image sources and `sizes` information about the presentation. The selection remains up to the browser. For explicitly controlled source selection the guide describes the `picture` element. [Q1] The task therefore does not necessarily consist of replacing every original with a single small file.
In the example the findings show that the preview already requests the same large source as the large view. The support team suggests suitable variants and their assignment. Whether this is the main cause on the real website must be demonstrated by them; the invented example is not a remote diagnosis.
Compare the same motif before and after the change
The acceptance inspects the same property page under documented conditions. These include the browser, display size, selected gallery path and whether already cached files were used. Technical values and visible quality are recorded together.
The editorial team checks the property information: Are room references and important details still recognisable? Does the enlarged view open the intended version? A blanket reduction that makes the floor plan unreadable does not fulfil the reader’s task.
Name the scope of the improvement
A successful check on one motif does not confirm every gallery and every end device. New landscape, portrait or particularly detail-rich images may require further suitable test examples. There is no general specification here for file format, pixel dimensions or number of photos.
The conclusion names the changed image delivery, the observed difference and remaining limits. It does not promise better search ranking or more inquiries. Its concrete objective is smaller and verifiable: the respective presentation requests an appropriate image source and continues to convey the required property information.