Effectively manage third-party scripts

[Jahangir147]

Third-party scripts, such as analytics or social sharing widgets, are common render blockers. If possible, load these scripts using DEFER or ASYNC .

Some non-essential third-party scripts may also be loaded after the page has fully rendered, using event receivers such as window onload.

1.3. Lazy loading of non-critical scripts with Intersection Observer
For scripts that are only needed once the user interacts or scrolls to a certain section (e.g., chat widgets or embedded videos), you can load them differently using the Intersection Observer API.

This tells the browser to load these scripts only when the relevant rcs data thailand elements appear on the screen, thus reducing the initial load for the browser.

Optimize CSS for faster rendering
CSS tells your browser how to style your page, but it can also slow down the display of that page. Let's take a look at how to make your CSS work with you, not against you, when it comes to performance.

2.1. Include essential CSS style sheets for above-the-fold content
Browsers block rendering until they've processed the CSS. To speed up first-time rendering, Google suggests identifying your " critical CSS " (the styles needed for above-the-fold content) and embedding them directly into your HTML.

This eliminates the need for the browser to wait for external style sheets before displaying above-the-fold content.

The easiest way to identify and integrate critical CSS is to use tools like the Chrome Coverage Tool to see what styles are loading during the initial render.