Recommendation : 2. Reduce the footprint of static content
Does the form allow the user to disable dynamic functions (ex: auto completion) ?
Aren't the entries in the form requiring unnecessary exchanges?
Certain functions when activated will use computation resources and network exchanges, this is the case of auto-completion systems which can be useful for certain audiences whose written expression is not very fluid but which are irrelevant for more independent users.
Source code checks
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) ?
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 ?