What does Eliminate render blocking resources mean?
Before the browser can display (render) a web page, it has to read its HTML. During this process, whenever the browser encounters a reference to a script (JavaScript), or stylesheet (CSS file), it has to stop, request the file, wait for it to download from the server, and execute it before it finally can continue.
The result is a delay in the display of the content to the visitor, during which time the page may appear blank or incomplete.
Eliminating render-blocking resources is essential to minimize this delay so the page can load and display content as soon as possible.
How WP Rocket can help
WP Rocket has options that can help with render-blocking JavaScript and CSS.
Render blocking JavaScript
The Load JavaScript deferred feature in WP Rocket should help eliminate the render-blocking JavaScript on your website by adding the “defer” tag in each script tag.
You’ll find this feature under Dashboard → WP Rocket → Settings → File Optimization → Load JavaScript Deferred.
Render blocking CSS
Using either of the following WP Rocket features should help remove render-blocking CSS:
PageSpeed is still flagging jquery.js on render-blocking.
If jquery.js is being flagged under “Eliminate Render Blocking Resources” it means that the file is being excluded from our Load JavaScript Deferred in this field:
Remove the line and make sure that your website is working fine. If so, the recommendation will be satisfied.
If you don’t find the exclusion there, it means it’s being excluded automatically as part of compatibility. That means that the site would break otherwise.
Not a WP Rocket customer yet?
Read our article about How to eliminate render-blocking resources on WordPress and learn how to address this PageSpeed Insights recommendation with and without a plugin.
Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.
FAQs
Step 10: Test and Monitor Performance
By following the above steps and utilizing the available plugins, you can effectively eliminate render-blocking resources. It will improve your WordPress website's speed, user experience, and overall performance. This will also improve WordPress SEO site ranking.
How does eliminating render-blocking resources affect page performance WordPress? ›
Step 10: Test and Monitor Performance
By following the above steps and utilizing the available plugins, you can effectively eliminate render-blocking resources. It will improve your WordPress website's speed, user experience, and overall performance. This will also improve WordPress SEO site ranking.
How to eliminate render-blocking resources in NextJS? ›
Add compiler:{styledComponents: true} to your next. config. js, install styled-components (yarn add styled-components and when it's done installing, run yarn add -D @types/styled-components ), update the file _document. js to support server side rendering for styled components and you are good to go!
What plugin is used to eliminate render-blocking resources? ›
Jetpack Boost enables you to optimize your site from your WordPress dashboard. With this plugin, you can optimize CSS loading, defer non-essential JavaScript, and implement lazy loading in a few simple steps. This is one of the easiest ways to eliminate render-blocking resources in WordPress.
How do I remove render blocking from WP-Optimize? ›
You can eliminate all render-blocking resources by deferring all non-critical JavaScript and CSS files. You can defer your JavaScript files by going to WP-Optimize > Minify > JavaScript and going to the “Load JavaScript asynchronously” section.
How to identify your render blocking resources? ›
“Render-blocking resources” can also be translated as “resources that block the first paint of your page”, so you should look for the resources that load before the FP/FCP event. You can do that in the Performance tab. Clicking on the “reload” button will start the profiler and automatically reload the page for you.
Is CSS a render blocking resource? ›
This creates an important performance implication: both HTML and CSS are render blocking resources. The HTML is obvious, since without the DOM we would not have anything to render, but the CSS requirement may be less obvious.
How to eliminate render blocking resources in Elementor? ›
To optimize Elementor-generated CSS, and avoid render-blocking issues, you can use plugins like WP Rocket or Autoptimize to minify and combine CSS files. You can inline critical CSS, use asynchronous or deferred loading of CSS files, and remove unused CSS and JavaScript.
Are font files render blocking? ›
Font files load async (not render blocking). So putting @font-face directly in your <head /> won't necessarily prevent a FOUT. The DOM will continue to render while the HTTP request for those font files (ex woff2, ttf, etc) is running async.
Why is JavaScript render blocking? ›
A few common causes of render-blocking on a website are unoptimized scripts and stylesheets, blocking elements in the intro of the page, external resources, or insufficient server resources.
From the dropdown menu, select the template that contains the section that you want to edit. Click a section to load the content into the preview window and access the options available to you. Click the eye icon to hide or unhide a section or block. Click Remove to delete a block or section.
What does render-blocking mean? ›
What are render-blocking resources? Render-blocking resources are portions of code in website files, usually CSS and JavaScript, that prevent a web page from loading quickly. These resources take a relatively long time for the browser to process, but may not be necessary for the immediate user experience.
