[Violation] Forced reflow while executing JavaScript took 830ms. The page in question is generated from user content, so I don't really have much influence over the size of the DOM. Viewing 15 replies - 1 through 15 (of 15 total), [Violation] setTimeout handler took 85ms | auto optimize JS CACHE, https://locksmithunit.es/wp-content/cache/autoptimize/js/autoptimize_0faae6e14c06ce5fda142895e39a52f6.js, https://www.keycdn.com/support/wordpress-cache-enabler-plugin#advanced-configuration, https://wordpress.org/support/topic/violation-settimeout-handler-took-99ms/, https://wordpress.org/support/topic/you-destroy-the-plugin-or-what-plugin-performance-is-terrible-3-last-updates/, https://wordpress.org/support/topic/no-support-i-post-3-posts-no-body-answer/, https://wordpress.org/support/topic/x-cache-handler-php-and-not-wp/, This reply was modified 2 years, 4 months ago by, This reply was modified 2 years, 3 months ago by. (is help and good the only problem is the last 3 updates). Specifically, one of the following: 2 Ways to Use Your Own Docker Image in Github Actions. He's written more than 1,000 articles for SitePoint and you can find him @craigbuckler. My problem was in a Material-UI app (early stages). Great answer, voltrevo! For instance code snippet 2: Code snippet 2, while solving the forced reflow, is not so useful. This refers to the re-calculation of positions and dimensions of all elements, which leads to re-rendering part or all of the document. Repeat. ( on your attention ), mod_headers/ cache control only ensure browsers know they can keep static resources (css/ js/ images/ ) in browser cache, but it does not create a server-side cache Zo and it is most certainly not related to the setTimeout issue youre looking into , I found that Elements hidden with display: none; will not cause a repaint or reflow when they are changed. It then allows you to sort the users by their ID or name. Violation: 'setTimeout' handler took
what is forced reflow while executing javascript