Source code for Avoid an excessive DOM size audit.Only until certain dependencies have changed if you are using the Effect Of DOM nodes created if you are rendering many repeated elements on the page. If you're rendering large lists, use virtual scrolling with the Component Dev Kit (CDK). See Google's Reduce the Scope and Complexity of Style Calculationsįor more information. Subtree Modification DOM Change BreakpointsĬan help you pinpoint when nodes get created.Īnother approach for improving rendering performance is simplifying your CSS selectors. Perhaps you can remove the undisplayed nodes from the initially loaded documentĪnd only create them after a relevant user interaction, Try loading your page and manually noting which nodes are displayed. If you're currently shipping a large DOM tree, In general, look for ways to create DOM nodes only when needed,Īnd destroy nodes when they're no longer needed. How your page's overall performance score is calculated. Lighthouse performance scoring post to learn
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |