Do not explicitly set options that use the default setting. Minimizing the number of options used in your form will maximize the performance of your Webform Server application and improve the user experience by reducing load times.
During the form design process, it’s possible to add options to a form that are not necessary, and do not impact the functionality of the form itself. In effect, these option are redundant because they have no effect on the form. Unfortunately, they can still impact load times.
Almost all options have default settings. Default settings are the basic automatic settings provided by the Designer. For example, the default background color of a form is white and the default text color is black. Using these defaults will improve the performance of your form.
If you choose not to use the Designer to create your forms and prefer to use a text editor, make sure you do not explicitly add options with default settings to your form.
The following list describes some scenarios where the form may contain redundant options:
- If an item does not use the label option, ensure that none of the label-related options are set. This includes labelbgcolor, labelfont, and so on.
- If an item does not print, ensure that none of the print-related options are set. This includes printbgcolor, printfontcolor, and so on.
- If an option is explicitly set to the default value, remove it from the form. The item will still use the default value for that option. (If you are creating the form in the Designer, the default setting is indicated by a blue dot next to the option in the Properties view. However, if you have been doing hand-coding, you may need to inspect the form in a text editor to determine if options are explicitly set.)
- If an item inherits settings from the page or the form, make sure those settings are not duplicated in the item itself.
No example provided.
Exceptions to this practice
There are no exceptions to this practice.