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不足或内存不足等。您需要考虑所有这些因素,才能改善服务器的响应时间。要找到服务器响应时间过长的原因,首先要进行测量。然后,准备好相关数据,并参阅有关如何解决该问题的相应指导。问题解决后,您必须继续测量服务器响应时间,并解决将来出现的性能瓶颈问题。

  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. 监测并提醒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.