广告请求瀑布流
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
概览
在发出首个广告请求之前请求的资源的报告。这些资源会延迟第一个广告请求,因此尽量减少其数量可加快广告加载速度。
建议
此项审核纯粹是为了提供参考,并不涉及网页通过或失败的情况。可利用提供的信息通过以下方式缩短发出第一个广告请求的时间:
- 通过移除、推迟资源、将其标记为异步等方式来减少资源数量。
- 合并资源以减少请求数量。
- 在请求广告之前仅请求关键资源,以优化资源的加载顺序。
上述任何优化措施都会对广告速度产生积极影响。
关键请求链
遵循代码最佳做法,以尽可能缩短网页延迟时间
如未另行说明,那么本页面中的内容已根据知识共享署名 4.0 许可获得了许可,并且代码示例已根据 Apache 2.0 许可获得了许可。有关详情,请参阅 Google 开发者网站政策。Java 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC):2025-07-25。
[null,null,["最后更新时间 (UTC):2025-07-25。"],[[["\u003cp\u003eThe audit reveals resources that are requested before the first ad request, potentially delaying ad loading.\u003c/p\u003e\n"],["\u003cp\u003eOptimizing the loading process of these resources improves ad speed and user experience.\u003c/p\u003e\n"],["\u003cp\u003eReduce the number, defer loading, or combine resources to minimize delays before the first ad request.\u003c/p\u003e\n"],["\u003cp\u003ePrioritize loading critical resources before requesting ads to optimize resource order and improve ad speed.\u003c/p\u003e\n"]]],["The content focuses on optimizing ad loading speed by minimizing resources requested before the first ad request. Key actions include reducing the number of resources by removing, deferring, or asynchronously loading them; combining resources; and prioritizing the loading order of critical resources. These steps aim to decrease the time to the first ad request, positively impacting ad speed. The report provides informative data to aid in these optimizations.\n"],null,["# Ad request waterfall\n\nOverview\n--------\n\nA report of the resources requested before the first ad request is made. These\nresources delay the first ad request, so minimizing their number will speed up\nad loading.\n\nRecommendations\n---------------\n\nThis audit is purely informative and not something a page can pass or fail. Use\nthe information provided to reduce the time to first ad request by:\n\n- Reducing the number of resources by removing them, deferring them, marking them async, etc.\n- Combining resources to reduce the number of requests.\n- Optimizing the order in which resources are loaded by requesting only critical resources prior to requesting ads.\n\nAny of the above optimizations will have a positive impact on ad speed.\n\nMore information\n----------------\n\n[Critical Request Chains](https://developers.google.com/web/tools/lighthouse/audits/critical-request-chains) \n\n[Tagging best practices to minimize page latency](https://support.google.com/admanager/answer/7485975) \n[View audit source](https://github.com/googleads/publisher-ads-lighthouse-plugin/tree/HEAD/lighthouse-plugin-publisher-ads/audits/ad-request-critical-path.js) [Improve this article](https://github.com/googleads/publisher-ads-lighthouse-plugin/tree/HEAD/docs/audits/ad-request-critical-path.md) [Report an issue](https://github.com/googleads/publisher-ads-lighthouse-plugin/issues/new?labels=documentation&template=documentation-feedback.md&title=Documentation+feedback%3A+ad-request-critical-path.md)\n\n\u003cbr /\u003e"]]