Visualforce Developer Guide

Introducing Visualforce
Tools for Visualforce Development
Getting a Quick Start with Visualforce
Customizing the Appearance and Output of Visualforce Pages
Standard Controllers
Standard List Controllers
Custom Controllers and Controller Extensions
Advanced Examples
Override Buttons, Links, and Tabs with Visualforce
Using Static Resources
Creating and Using Custom Components
Dynamic Visualforce Bindings
Dynamic Visualforce Components
Integrate Email with Visualforce
Visualforce Charting
Creating Maps with Visualforce
Render Flows with Visualforce
Templating with Visualforce
Developing Salesforce Apps with Visualforce
Adding Visualforce to a Salesforce AppExchange App
Using JavaScript in Visualforce Pages
Communicating Across the DOM with Lightning Message Service
Visualforce Best Practices
Best Practices for Improving Visualforce Performance
Investigate Performance Issues
Follow Visualforce Design Guidelines
Control Data Size
Cache Frequently Accessed Data
Lazy Load Page Components
Handle Multiple Concurrent Requests
Write Efficient Apex and SOQL
Write Efficient Getter Methods
Optimize Lists and Tables
Optimize the View State
Optimize HTML
Optimize CSS
Optimize JavaScript
Optimize Images
Prevent Fields from Dropping Off the Page
Use the immediate Attribute Carefully
Visualforce Performance Case Study
Best Practices for Accessing Component IDs
Best Practices for Static Resources
Best Practices for Controllers and Controller Extensions
Best Practices for Using Component Facets
Best Practices for Page Block Components
Best Practices for Rendering PDF Files
Best Practices for <apex:panelbar>
Documentation Typographical Conventions
Standard Visualforce Component Reference
Appendices
PDF

Optimize Lists and Tables

To improve the performance of Visualforce pages with lists and tables, limit the amount of data displayed per page and reduce the number of editable fields per table. You can also implement pagination or replace an <apex:pageBlockTable> component with a static HTML table.

Avoid Data Grids if Possible

Data grids are tables that display records with editable fields. Data grids frequently expand to thousands of input components on a page and exceed the maximum view state size. Large data grids result in a Visualforce component tree that processes slowly.

If your Visualforce page has a data grid:

  • Use pagination and filters.
  • To reduce the view state size, make data read-only where possible.
  • Only display essential data for a given record. Provide a link to an Ajax-based details box or to a separate details page.

Consider Static HTML Tables

A Visualforce page with an iteration component such as <apex:pageBlockTable> can contain up to 1,000 items, or 10,000 items when the page is executed in read-only mode. However, page performance can sometimes decrease before this limit if <apex:pageBlockTable> contains an <apex:column> component with the rendered attribute explicitly specified.

If your Visualforce page has a large table, we recommend that you implement pagination. Alternatively, you can use a static HTML table instead of an <apex:pageBlockTable> component. Within the HTML table, use the <apex:repeat> component to iterate over an HTML row element. For an example HTML table that uses <apex:repeat>, see the apex:repeat component reference page.

Unlike <apex:pageBlockTable> tables, static HTML tables don’t have standard Salesforce styling.

Note