A developer is creating a page in App Builder that will be used in the Salesforce mobile app. Which two practices should the developer follow to ensure the page operates with optimal performance? Choose 2 answers
A.
Limit five visible components on the page.
B.
Limit 25 fields on the record detail page.
C.
Limit the number of Tabs and Accordion components.
D.
Analyze the page with Performance Analysis for App Builder.
Answer:
B, D
Explanation:
User Votes:
A 3 votes
50%
B 3 votes
50%
C 2 votes
50%
D 5 votes
50%
Discussions
0/ 1000
isirbu
1 year, 3 months ago
CD https://help.salesforce.com/s/articleView?id=sf.lightning_page_performance.htm&type=5
vanglik
1 year ago
BD
If a page has more than 5 related lists or more than 25 fields in the record detail, users can encounter performance issues when viewing the page in the Salesforce mobile app. In the Performance Analysis for App Builder tool: Components that are restricted to the desktop form factor via a visibility rule aren’t included in the phone form factor performance assessment. Analysis of page performance on a phone is available only on pages whose template supports the phone form factor. Components aren't the only factors influencing page load time, so the numbers in the component impact chart don't add up to 100% of the predicted page load time. Analysis of pages for the desktop form factor is measured in seconds. For the phone form factor, the page is scored based on the components that are visible when the page loads on a phone. User metrics are org-specific or page-specific data. Previously activated pages display metrics from visits to that page. New pages display metrics from visits
Want to join our community?
Please log in or signup in order to use this feature
CD https://help.salesforce.com/s/articleView?id=sf.lightning_page_performance.htm&type=5
BD
If a page has more than 5 related lists or more than 25 fields in the record detail, users can encounter performance issues when viewing the page in the Salesforce mobile app.
In the Performance Analysis for App Builder tool:
Components that are restricted to the desktop form factor via a visibility rule aren’t included in the phone form factor performance assessment.
Analysis of page performance on a phone is available only on pages whose template supports the phone form factor.
Components aren't the only factors influencing page load time, so the numbers in the component impact chart don't add up to 100% of the predicted page load time.
Analysis of pages for the desktop form factor is measured in seconds. For the phone form factor, the page is scored based on the components that are visible when the page loads on a phone.
User metrics are org-specific or page-specific data. Previously activated pages display metrics from visits to that page. New pages display metrics from visits