Print this page

Manage Site limits

Knowledge Article Number 000231129

Increased traffic or load testing can cause your Site Limits to hit. We'll go over what you can do to manage your limits, monitor them and what to do when you hit a limit. You can pro-actively monitor and manage your Site Request Time, Origin Bandwidth and Page View Limits.


Small Alert Icon Before you get started - Salesforce support has the ability only to reset/increase Site Request Time and Origin Bandwidth limits. The Page View Limit cannot be reset/increased by support. Contact your AE to get page view limit increased. 

Information you should have

1. The site ID. 
  • To get the site ID, visit the view of the site/community. 
  • If a domain name has been defined for sites, go to Setup > Develop > Sites 
  • Locate your site/community and click on the site label. You will come to the view. 
  • The Site ID will be on the browser URL. For example,
  • If you have a community and the domain name has not been defined, go to Setup > Build > Communities > All Communities 
  • Click Manage next to your community
  • On the left panel, click Administration | Pages | Click Go to
    - This will take you to the view and you can locate your site id. 

2. Current Limits Usage 
  • As per previous instructions, go to the view of the site/community. 
  • There will be a Related List called 24-Hour Usage History
  • This will show you the Current Usage, Daily Limit and Percent Used for Bandwidth and Request Time 

What to do when limits are approaching or crossed 100% usage

  • Raise a case immediately with Developer support stating your Site limits have been hit and request for a limit reset.

NOTE: Support can reset Site Request and bandwidth limits since they are daily limits. Page View limit is a monthly limit and paid for, so support can't reset it. If we see that the reset has to happen every other day, support can provide a temporary increase. 

Proactively monitor or track the site limit usage

  • Set workflow email alerts to notify you in advance when the limits are approaching to max. 
  • Workflow rules that are created on the "Site" object are evaluated every hour for all sites within the organization, unless your criteria is limited to certain sites. This means that the criteria for checking the Site Request and bandwidth limits run every hour. 
  • Workflow rules that are created on the Organization and User License objects are evaluated every three hours. This means that the criteria to check the Page View limit evaluates every three hour. 
  • Install and use the managed package to track the limits via reports. 
  • Site usage data is aggregated at midnight, GMT, so the current day's page view counts may not be accurately reflected in reports, depending on your time zone. Cache server page views may take a day or more to be reflected in reports.

Load tests and unexpected increase in traffic

  • Prepare in advance. Have a test plan and estimate of limits required.
  • Analyze the trend and usage pattern via the appexchange package reports.  
  • Raise a case with Support at least 2 weeks in advance. We can increase the limit temporarily based on business case and impact.   

Best Practices to manage limits

  • Caching pages. More information here: Caching Sites Pages
  • Review the Site Best Practices document.
  • Recommendations: 
    • Do an analysis and determine which pages are worthy of caching.
    • For static pages, hourly or daily caching would be ideal.
    • If a page has both dynamic and static content, it is worth considering separating the two to different pages.
    • If you have inline CSS, this should be uploaded as static resource.
    • If using apex controller classes, consider optimizations such as pagination of data (instead of showing 1000 records in a page, show 50 per page). Avoid heavy data sets and a complex logic. 

promote demote