Recommendation : 2. Reduce the footprint of static content
When selection lists are available, are they limited to values relevant to the service user ?
Do you have unnecessary elements (for example AUSTRALIA for a Franco-French service) in the lists (for example countries) ?
When entering data from lists, the volume of the lists can provide entries that are of no interest and generate totally unnecessary volume: for example, a list of countries from Afghanistan to Zimbabwe for a Franco-French service for which the country is not a critical datum, while example choices such as "France, Europe, Other" would suffice.
Source code checks / Browser / navigation tests
Operational issues related to the project
Rule for assessing the level of compliance of the criterion
Number of selection lists analyzed / Number of selection lists
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.) ?
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", ....) ?