避免出現瓶頸要求
透過集合功能整理內容
你可以依據偏好儲存及分類內容。
總覽
這項稽核會找出阻礙第一個廣告請求的長時間執行要求。這些要求是在第一個廣告請求提出前所發出，且在發出第一個廣告請求前收到回應。減少這些封鎖請求的數量和持續時間，就能縮短第一個廣告請求的延遲時間，進而加快廣告載入速度。
建議
這項稽核的詳細資料包含前 5 大造成阻斷的要求 (依費用)。目標是移除或縮短這些要求的持續時間，以加快廣告載入速度。以下提供幾個訣竅：
- 排除不必要的要求。
- 先延遲非關鍵要求，直到廣告載入完畢後再進行。
- 同時 (而非依序) 發出要求。
- 透過 HTTP/2 等最佳化後端服務，藉此改善回應時間
這項稽核會依據費用顯示前 5 大瓶頸要求。要求的成本計算方式如下：
request duration + (request self-time * 3)
其中， request self-time 等於要求時間長度減去其他要求的封鎖時間。只有自身時間超過 250 毫秒或時間大於 1 的要求，才會納入計算。
除非另有註明，否則本頁面中的內容是採用創用 CC 姓名標示 4.0 授權，程式碼範例則為阿帕契 2.0 授權。詳情請參閱《Google Developers 網站政策》。Java 是 Oracle 和/或其關聯企業的註冊商標。
上次更新時間：2025-07-25 (世界標準時間)。
[null,null,["上次更新時間：2025-07-25 (世界標準時間)。"],[[["\u003cp\u003eThis audit focuses on identifying and mitigating long-running requests that delay the initial ad request, ultimately hindering ad loading speed.\u003c/p\u003e\n"],["\u003cp\u003eBy reducing or removing these "blocking requests," publishers can significantly improve the latency of their first ad request.\u003c/p\u003e\n"],["\u003cp\u003eOptimization strategies include eliminating unnecessary requests, deferring non-critical requests, parallelizing request execution, and enhancing backend service response times.\u003c/p\u003e\n"],["\u003cp\u003eThe audit highlights the top 5 most impactful blocking requests based on a calculated "cost" that factors in request duration and self-time.\u003c/p\u003e\n"],["\u003cp\u003eRequests with self-times exceeding 250ms or durations longer than 1s are flagged for potential optimization to improve ad loading performance.\u003c/p\u003e\n"]]],["The audit identifies long-running requests that delay the first ad request. It highlights the top five blocking requests based on their calculated cost. Actions to reduce delays include eliminating or deferring non-critical requests, issuing requests in parallel, and improving response times. The cost of a request is its duration plus three times its self-time (duration minus blocked time). Only requests with self-time above 250ms or duration above 1s are considered.\n"],null,["# Avoid bottleneck requests\n\nOverview\n--------\n\nThis audit identifies long-running requests that are blocking the first ad\nrequest. These are requests that were initiated and which also received a\nresponse before the first ad request was made. Reducing the number and duration\nof these blocking requests will reduce the latency of the first ad request,\nspeeding up ad loading.\n\nRecommendations\n---------------\n\nThe details of this audit contain the top 5 blocking requests\n([by cost](#more_information)). The goal here is to remove or reduce the\nduration of these requests to speed up ad loading. Some tips for doing this\ninclude:\n\n- Eliminating unnecessary requests.\n- Deferring non-critical requests until after ads are loaded.\n- Issuing requests in parallel rather than serially.\n- Improving response times by optimizing backend services, using HTTP/2, etc.\n\nMore information\n----------------\n\nThis audit displays the top 5 bottleneck requests by cost. The cost of a request\nis computed as follows:\n\n`request duration + (request self-time * 3)`\n\nWhere request self-time is equal to duration minus time spent blocked by other\nrequests. Only requests with a self-time greater than 250ms or a duration\ngreater than 1s are considered. \n[View audit source](https://github.com/googleads/publisher-ads-lighthouse-plugin/tree/HEAD/lighthouse-plugin-publisher-ads/audits/bottleneck-requests.js) [Improve this article](https://github.com/googleads/publisher-ads-lighthouse-plugin/tree/HEAD/docs/audits/bottleneck-requests.md) [Report an issue](https://github.com/googleads/publisher-ads-lighthouse-plugin/issues/new?labels=documentation&template=documentation-feedback.md&title=Documentation+feedback%3A+bottleneck-requests.md)\n\n\u003cbr /\u003e"]]
