Recommendation : 7. Limit the use of hardware components or sensors on user terminals
Are the exchanged files compressed ?
Is compression effective?
The volume of data transferred increases the environmental footprint of the service, because the data is also stored, secured with duplication, backed up. Some data formats can be compressed to reduce their size, since the compression operation requires computation and intermediate storage resources, it is more efficient for the data to be available in compressed form.
Browser tools/consoles allow to check data transfer, size & frequency (CHROME: console / network)
Opquast 108 / pidila-437 / greenIT 107
Rule for assessing the level of compliance of the criterion
Number of compressed file transfer / Number of file transfer
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 images to be uploaded properly resized and converted to a thin client-side format before transfer ?