Apex Page Rules

The following table shows the list of Salesforce Apex Trigger rules that are checked by Quality Clouds.

Description	Issue Severity	Impact Area
Component id must be unique	High	Scalability
Action Pollers should not use short polling intervals	High	Performance
Avoid using more than one <apex:form> tag per page	Medium	Manageability
Avoid using data grids	Medium	Performance
Avoid importing multiple CSS files individually	Medium	Performance
Avoid importing multiple JavaScript files individually	Medium	Performance
Avoid using <apex:includeScript>	Medium	Manageability
Static Resources should be used to serve JavaScript, CSS and images	Medium	Performance
Avoid using HTML tags which will be removed by the VisualForce page	Medium	Performance
Avoid displaying the results of unbounded queries on a page	Medium	Performance
Avoid using an excessive number of images	Medium	Performance
Avoid importing css and javascript files from sources other than static resources	Medium	Performance
Avoid importing images from sources other than static resources	Medium	Manageability
Include JavaScript code from Static Resources	Medium	Manageability
Avoid using the File Download Servlet to reference static resources	Medium	Manageability
Use custom components to lazy load data in APEX pages	Low	Performance
Page names should always begin with an upper case character	Low	Manageability

Updated on March 21, 2025

Rules