Visualforce Developer Guide

Clouds with binary code floating aboveCloud with binary code floating above

No Results

Search Tips:

  • Please consider misspellings
  • Try different search keywords
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

Control Data Size

Visualforce pages have a 15-MB standard response limit, and smaller pages load faster than larger pages. To minimize load times, limit the amount of data that each page displays.

Filter Query Results

  • Use filters to limit the data that Salesforce Object Query Language (SOQL) calls in and that Apex controllers return. For example, use AND statements in WHERE clauses. You can also remove null query results.
  • When creating Apex controllers, use the with sharing keyword to retrieve only records that the user can access.
  • Filter in SOQL first, then in Apex, and finally in Visualforce.

Use Pagination

  • A page with unbounded data can cause longer load times, hit governor limits, and become unusable as the dataset grows. To prevent a list view from displaying unbounded data, implement pagination with a list controller. By default, a list controller returns 20 records per page, but you can configure list views to display up to 100 records at a time. To control the number of records each page displays, use a controller extension to set the pageSize.
  • Use the SOQL OFFSET clause to write logic that paginates to a specific subset of results within SOQL.