Recommendation : 2. Reduce the footprint of static content
Have the images been compressed upstream in a format suitable for viewing ?
Does each image use a standard web format and offer an alternative for certain optimized formats that would not be available in all environments?
The transmission of compressed data is essential to reduce the impact of exchanges. However, compression algorithms consume technical processing resources and intermediate storage. When compressions are made on each swap request, its benefit may disappear or even increase the impact.
Browser tools/consoles allow to check compliance w/ best practices (CHROME: extension greenIT : best practices)
RGAA / standard or certificate (14062?)
13 other criteria related to the recommendation: Reduce the footprint of static content
What images are really meaningful and useful for understanding the service (examples: logo, images, links, contractual images, etc.) ?
What images can we avoid (not useful for understanding the service) ?
Can text replace certain types of images (icons, picto ...) ?
Is an alternative to images always available ?
Is the information overlay removed ?
Has the impact of internationalisation (multi-languages, etc.) been assessed ?
Is there a limit to the number of different fonts ?
Do you prefer system fonts ?
Is the configuration of the form minimal (so as not to overload the code for unhelpful styles) ?
Does the form allow the user to disable dynamic functions (ex: auto completion) ?
Are the forms useful (example: not creating an account for the purchase of a product / service - e-commerce) ?
Are robots banned and unsolicited access treated by inexpensive solutions (captcha vs "addition", ....) ?
When selection lists are available, are they limited to values relevant to the service user ?