--- schema_version: "1" id: d7cdf0ccc115a6835e247d0dfdec0414e33478e6e78993467ae6ff7eea2eac2d title: Progressive Rendering Overview collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/experience/264-0-0/community_builder_prioritization_overview.md canonical_url: https://help.salesforce.com/s/articleView?id=experience.community_builder_prioritization_overview.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: d351c027bf6bf9cefcc3357d4bb2dc3abf668e27871674bce6b6316f4b52fdd0 description: Progressive Rendering prioritizes the display order of your page components. With proper planning and testing, it can improve display time performance and polish your site’s experience to better engage customers. products: - Experiences release: "264" --- # Progressive Rendering Overview Progressive Rendering prioritizes the display order of your page components. With proper planning and testing, it can improve display time performance and polish your site’s experience to better engage customers. ### Required Editions
Available in: Enterprise, Performance, Unlimited, and Developer Editions
Progressive Rendering improves the performance of your page by fetching and rendering page components in a parallel and prioritized manner. If you notice that your site pages take a long time to load before you see the components rendered on the screen, then progressive rendering can help improve your site’s performance. Assign one of three priorities to any top-level component. Component Priority Levels | Priority | Description | | --- | --- | | Highest | Highest priority components are displayed first. This priority is recommended for key content that you want to display first or content that appears above the fold on longer pages. | | High | High priority components are displayed after all components in the Highest group. | | Neutral | Neutral priority components are displayed after all other components that have a higher priority. By default, all components begin with a Neutral priority. | ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-experience-communities-264-0-0-production-enus/bf7df212-91a1-4fa3-a007-4d6f3e3b470b/images/icon_note.png) Note Only top-level components in the content area of your pages can have a priority. You can’t assign a priority to a nested component. As an example, assign **Highest** (first) to the few components that you want to be viewed first. Specify **High** (second) for those components that can load later without affecting your customer’s experience. Unassigned components are treated as **Neutral** by default and are displayed last. There’s no right choice for assignments, but a lack of planning can degrade performance and diminish positive experiences on your site. For instance, sometimes you want a critical notice to appear first, prioritized as highest, and then fill in some of your highlighted content, prioritized as high. All other components, visible and below the fold, load after critical notices are rendered. Whether explicitly prioritized as neutral or not, they’retreated as neutral. ![Abstract image of progressive rendering depicting load order](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-experience-communities-264-0-0-production-enus/bf7df212-91a1-4fa3-a007-4d6f3e3b470b/communities/images/communites_builder_progrendabstract.png) ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-experience-communities-264-0-0-production-enus/bf7df212-91a1-4fa3-a007-4d6f3e3b470b/images/icon_note.png) Note All unassigned components are set to **Neutral** priority. For new sites, the default priorities for components can vary based on the site template. Because Progressive Rendering requires careful planning and testing, it’s off by default. Turn it on from the **Advanced** section of your Experience Builder Settings. Using this feature requires time and effort. But don’t worry, we provide some ideas to help you get started in the [Progressive Rendering Guidelines](https://help.salesforce.com/s/articleView?id=experience.community_builder_prioritization_guidelines.htm&release=264.0.0&type=5 "Here are some guidelines for how to get the most out of Progressive Rendering.") So, what happens while Progressive Rendering is doing its thing? Your page layout is roughly rendered and then components are added in order of decreasing priority. Generally, this type of rendering doesn’t cause any visual issues. However, sometimes components rearrange as the page displays, depending on which components you prioritized and how quickly it loads. That’s another good reason to test, test, and retest when you decide to take advantage of this advanced feature. Assign a priority to a component in the actions menu of the Property Editor. ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-experience-communities-264-0-0-production-enus/bf7df212-91a1-4fa3-a007-4d6f3e3b470b/images/icon_note.png) Note After you set the priorities, adding, deleting, or duplicating a component or changing themes or layouts doesn’t change your priority settings, but it invalidates your assumptions and testing. To ensure that your choices remain effective, you can expect any changes made to kick off a new round of testing. We try to notify you when you make those kinds of changes, but you still have to do the testing. Always make testing a part of your change plan. Turning off Progressive Rendering removes prioritized behavior, but your settings remain. If you turn on Progressive Rendering again later, the original priority settings go back into force. While the continuity makes testing easier, the results can surprise you if you don’t watch for it. - **[Progressive Rendering Guidelines](https://help.salesforce.com/s/articleView?id=experience.community_builder_prioritization_guidelines.htm&release=264.0.0&type=5)** Here are some guidelines for how to get the most out of Progressive Rendering. - **[Prioritize Component Display Order with Progressive Rendering](https://help.salesforce.com/s/articleView?id=experience.community_builder_prioritization_howto.htm&release=264.0.0&type=5)** Quickly set the display order of components on your Experience Builder pages with Progressive Rendering. By carefully optimizing how your pages display, you can enhance the experience of your site and better engage your community. #### See Also - [Salesforce Community Page Optimizer analyzer](https://salesforce.quip.com/eXICApPXVIaN) - [Prioritize Component Display Order with Progressive Rendering](https://help.salesforce.com/s/articleView?id=experience.community_builder_prioritization_howto.htm&release=264.0.0&type=5 "Quickly set the display order of components on your Experience Builder pages with Progressive Rendering. By carefully optimizing how your pages display, you can enhance the experience of your site and better engage your community.") - [Assign an Audience to a Component](https://help.salesforce.com/s/articleView?id=experience.networks_audience_component.htm&release=264.0.0&type=5 "When you assign an audience to a page component, all users see the same page, but the components that are visible on the page differ among user segments. For example, you have a page that’s visible to site members and guest users, and you want your members to be able to post questions and comments. You can add the Feed Publisher component to the page and assign this component to an audience for site members only. Your members can see the component, and guest users can’t.")