廣告請求刊登序列
透過集合功能整理內容
你可以依據偏好儲存及分類內容。
總覽
報表會列出發出第一個廣告請求前要求的資源。這些資源會延遲第一個廣告請求,因此請盡量減少資源數量,以加快廣告載入速度。
建議
這項稽核僅供參考,不代表網頁可能會通過或失敗。請使用提供的資訊來縮短發出第一個廣告請求的時間,方法如下:
- 透過移除、延後、標示為非同步等方式減少資源數量。
- 合併資源以減少要求數量。
- 在要求廣告之前,只請求重要資源,藉此將資源載入順序最佳化。
上述任何一項最佳化方式都能提升廣告速度。
關鍵要求鏈結
可縮短網頁延遲時間的代碼最佳做法
除非另有註明,否則本頁面中的內容是採用創用 CC 姓名標示 4.0 授權,程式碼範例則為阿帕契 2.0 授權。詳情請參閱《Google Developers 網站政策》。Java 是 Oracle 和/或其關聯企業的註冊商標。
上次更新時間:2025-07-25 (世界標準時間)。
[null,null,["上次更新時間: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"]]