Recommendation : 7. Limit the use of hardware components or sensors on user terminals
Are the images to be uploaded properly resized and converted to a thin client-side format before transfer ?
Is there a resizing feature corresponding to the intended use of the uploaded image built into the upload feature?
Image transfers introduce peculiarities related to the format of the images, some generate very different file sizes. Image sizes and quality levels very quickly increase the volumes needed to store images. Transcoding and resizing can be carried out before transfers but require processing resources, intermediate storage spaces and create new files which, in the absence of automatic cleanings, can increase the volume of data.
Browser tools/consoles allow to check compliance w/ best practices for images resizing, compression (CHROME: extension greenIT : best practices)
Operational issues related to the project
Rule for assessing the level of compliance of the criterion
Number of images not resized on display / Number of images
8 other criteria related to the recommendation: Limit the use of hardware components or sensors on user terminals
Are the sensors being used as needed, rather than constantly ?
Are the pause functions available ?
Is the inaccessibility of a sensor, linked to the equipment or to the user's choice, treated to allow the service to be functional nonetheless (if possible) ?
Are predictive algorithms in place to avoid the use of physical sensors ?
Do you inform users of the size constraints and accepted file format ?
Technical User Experience
Is the frequency of the animation appropriate for the functionality ?
Do uploads only allow the list of authorized file types ?
Are the exchanged files compressed ?