Recommendation : 2. Reduce the footprint of static content
What images can we avoid (not useful for understanding the service) ?
Are non-valuable images deleted?
The weight of an image, thus its impact, is incomparable with text. The choice to use an image must be justified. An image may be necessary or even contractual (image of a product on an online sales service) or only serve to fill in space in the content. Reducing the number of images decreases the impact of using the service.
13 other criteria related to the recommendation: Reduce the footprint of static content
Have the images been compressed upstream in a format suitable for viewing ?
What images are really meaningful and useful for understanding the service (examples: logo, images, links, contractual images, etc.) ?
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 ?