{"id":15453,"date":"2022-02-21T07:48:16","date_gmt":"2022-02-21T07:48:16","guid":{"rendered":"https:\/\/mailinvest.blog\/index.php\/2022\/02\/21\/how-to-identify-and-reduce-render-blocking-resources\/"},"modified":"2022-02-21T07:48:16","modified_gmt":"2022-02-21T07:48:16","slug":"how-to-identify-and-reduce-render-blocking-resources","status":"publish","type":"post","link":"https:\/\/mailinvest.blog\/index.php\/2022\/02\/21\/how-to-identify-and-reduce-render-blocking-resources\/","title":{"rendered":"How To Identify And Reduce Render-Blocking Resources"},"content":{"rendered":"

<\/a>\n<\/p>\n

\n

Identifying and reducing resources responsible for blocking the rendering of your web page is a critical optimization point that can make or break your page speed.<\/p>\n

It can be so critical that it can pay dividends to your site\u2019s page experience metrics<\/a> (and your user\u2019s satisfaction) as a result.<\/p>\n

In 2021, the average time it took to fully render a mobile web page was 22 seconds<\/a>. In 2018, it was 15 seconds<\/a>.<\/p>\n

Clearly, this is a substantially higher number than Google\u2019s recommended time of 2-3 seconds. It\u2019s also substantially higher than it used to be.<\/p>\n

What could be causing these issues with render-blocking resources?<\/p>\n

What is driving this increase in overall page render speed?<\/p>\n

One interesting trend to note is that there has been an increasing reliance on third-party fonts<\/a> compared to system fonts. Using third-party fonts as a resource tends to interfere<\/a> with the processing and rendering of a page.<\/p>\n

With system fonts, the browser does not have to load anything extra, so it doesn\u2019t have that additional processing step as a result.<\/p>\n

\"ThisScreenshot from Web Almanac, January 2022<\/em><\/span>