이 규칙은 PageSpeed Insights에서 서버 응답 시간이 200 ms 이상임이 감지되면 트리거됩니다.
개요
서버 응답 시간은 서버에서 페이지 렌더링을 시작하기 위해 필요한 HTML을 로드하는 데 걸리는 시간에서 Google과 서버 간 네트워크 지연 시간을 차감하여 측정합니다. 실행할 때마다 변동이 있을 수 있지만 차이는 별로 크지 않습니다. 실제로 변동이 심한 서버 응답 시간은 기반 성능에 문제가 있음을 나타낼 수 있습니다.
권장사항
서버 응답 시간을 200 ms 아래로 줄여야 합니다.
서버의 응답 속도를 저하시키는 요인으로는 느린 애플리케이션 로직, 느린 데이터베이스 쿼리, 느린 라우팅, 프레임워크, 라이브러리, 리소스 CPU 부족 현상 또는 메모리 부족 현상 등 수십 가지가 있습니다. 서버의 응답 시간을 개선하려면 이러한 모든 요인을 고려해야 합니다.
서버 응답 시간이 높은 이유를 밝히기 위한 첫 단계는 측정입니다. 그런 다음 데이터를 갖추고 문제 해결 방법에 관한 적절한 가이드를 참조하세요. 문제를 해결한 후에도 서버 응답 시간을 계속 측정하여 향후 성능 병목 현상을 해결해야 합니다.
기존 성능과 데이터를 수집 및 검사합니다.
사용 가능한 성능과 데이터가 없으면 자동화된 웹 애플리케이션
모니터링 솔루션을 사용하여 평가하거나 맞춤 계측 도구를 추가하세요. 대부분의 플랫폼에서 사용할 수 있는 호스팅된 오픈소스 버전의 솔루션이 있습니다.
상위 성능 병목 현상을 식별 및 해결합니다. 많이 사용되는
웹 프레임워크나 콘텐츠 관리 플랫폼을 사용하는 경우 성능 최적화
권장사항 도움말을 참조하세요.
[null,null,["최종 업데이트: 2025-07-25(UTC)"],[[["\u003cp\u003eThis documentation is outdated and refers to a deprecated version of PageSpeed Insights API (v4).\u003c/p\u003e\n"],["\u003cp\u003eVersion 5 of the API is the latest and offers real-world and lab data for performance analysis.\u003c/p\u003e\n"],["\u003cp\u003eServer response time, the time taken to load HTML for rendering, should be under 200ms.\u003c/p\u003e\n"],["\u003cp\u003eSlow response times can indicate performance issues stemming from various factors, including slow application logic and database queries.\u003c/p\u003e\n"],["\u003cp\u003eOptimization involves measuring, identifying bottlenecks, implementing fixes, and continuous monitoring.\u003c/p\u003e\n"]]],["The core issue addressed is slow server response time, defined as over 200ms, which delays page rendering. To improve, the content advises measuring server response time to identify performance bottlenecks such as slow application logic, queries, or resource starvation. Key actions include gathering performance data, fixing top bottlenecks using framework documentation, and implementing ongoing monitoring with alerts for future performance issues. The document recommends seeking further support via Stack Overflow or a mailing list.\n"],null,["# Improve Server Response Time\n\n| **Deprecated** . This page was written for version 4 of the PageSpeed Insights API, which is deprecated and will be shut down in May 2019. [Version 5](/speed/docs/insights/v5/get-started) is the latest and provides both real-world data from the Chrome User Experience Report and lab data from Lighthouse.\n\n\nThis rule triggers when PageSpeed Insights detects that your server response time is above 200 ms.\n\n### Overview\n\n\nServer response time measures how long it takes to load the necessary HTML to begin rendering the page from your server, subtracting out the network latency between Google and your server. There may be variance from one run to the next, but the differences should not be too large. In fact, highly variable server response time may indicate an underlying performance issue.\n\n### Recommendations\n\n\nYou should reduce your server response time under 200ms.\n\nThere are dozens of potential factors which may slow down the response of your server: slow application logic, slow database queries, slow routing, frameworks, libraries, resource CPU starvation, or memory starvation. You need to consider all of these factors to improve your server's response time.\n\nThe first step to uncovering why server response time is high is to measure. Then, with data in hand, consult the appropriate guides for how to address the problem. Once the issues are resolved, you must continue measuring your server response times and address any future performance bottlenecks.\n\n1. **Gather and inspect** existing performance and data. If none is available, evaluate using an automated web application monitoring solution (there are hosted and open source versions available for most platforms), or add custom instrumentation.\n2. **Identify and fix** top performance bottlenecks. If you are using a popular web framework, or content management platform, consult the documentation for performance optimization best practices.\n3. **Monitor and alert** for any future performance regressions!\n\nFeedback\n--------\n\nWas this page helpful? \nYes Great! Thank you for the feedback. If you have a specific, answerable question about using PageSpeed Insights, ask the question in English on [Stack\n| Overflow](https://stackoverflow.com/questions/tagged/pagespeed-insights). For general questions, feedback, and discussion, start a thread in the [mailing list](https://groups.google.com/forum/#!forum/pagespeed-insights-discuss).\nNo Sorry to hear that. If you have a specific, answerable question about using PageSpeed Insights, ask the question in English on [Stack\n| Overflow](https://stackoverflow.com/questions/tagged/pagespeed-insights). For general questions, feedback, and discussion, start a thread in the [mailing list](https://groups.google.com/forum/#!forum/pagespeed-insights-discuss)."]]
