This rule is triggered when PageSpeed Insights detects that your server response time exceeds 200 milliseconds.

Overview

Server response time represents the time needed to load the necessary HTML to start rendering the web page hosted by the server, minus the network latency between Google and the server. The time taken for each run may vary, but the difference should not be too great. In fact, if the server response time varies greatly, it may indicate that there may be a performance problem.

Recommendations

您應將服務器響應時間控制在200毫秒以內。有很多潛在因素都可能會延緩服務器響應，例如應用邏輯緩慢、數據庫查詢緩慢、路由緩慢、框架、庫、資源CPU不足或內存不足等。您需要考慮所有這些因素，才能改善服務器的響應時間。要找到服務器響應時間過長的原因，首先要進行測量。然后，準備好相關數據，并參閱有關如何解決該問題的相應指導。問題解決后，您必須繼續(xù)測量服務器響應時間，并解決將來出現(xiàn)的性能瓶頸問題。

1. 收集并檢查Existing performance and data. If there is no content available, use an automated Web application monitoring solution (some hosted open source versions are available in the market, which are suitable for most platforms) for evaluation, or add a custom method.
2. Identify and repairThe primary performance bottleneck problem. If you are using a popular web page framework or content management platform, see the documentation on best practices for performance tuning.
3. 監(jiān)測并提醒Any future performance degradation problems!

?

Except as other written, the content of this page is licensed under theCreative Commons Attribution 3.0 License, and code samples are licensed under the?Apache 2.0 License. For details, see our?Site Policies.