AI-generated Key Takeaways
-
This audit identifies the time users experience delays due to ad scripts blocking the main thread, which negatively impacts loading speed and responsiveness.
-
The primary cause of ad-related blocking is loading too many ads simultaneously, so it is recommended to reduce the number or density of ads.
-
Optimizing ad loading by lazy loading below-the-fold ads and reducing batch sizes for Single Request Architecture can minimize blocking and enhance user experience.
-
Ad-related scripts are identified through ad tags and third-party web classifications, providing insights into specific scripts contributing to blocking.
Overview
This audit measures the amount of blocking time attributable to ad-related scripts. This captures time where the JS thread is blocked by an ad-related script for long enough to be noticeable by users as it can directly affect input delay or content loading.
Recommendations
The most important factor in ad JS blocking time is how many ads are being loaded at once. Our recommendations are:
- Load fewer ads at once or reduce ad density, if feasible
- Lazy load ads below the fold
- Reduce batch sizes if using Single Request Architecture (SRA) in GPT.
More information
To learn how blocking time is defined, see this article on Total Blocking Time
A script is considered to be ad-related if it is either an ad tag or labeled as an "ad" script by Third Party Web.