이 규칙은 PageSpeed Insights에서 압축 가능한 리소스가 gzip 압축 없이 제공된 것을 감지하면 트리거됩니다.
개요
모든 최신 브라우저는 모든 HTTP 요청에서 gzip 압축을 지원하고 자동으로 협상합니다. gzip 압축을 사용 설정하면 전송되는 응답의 크기를 최대 90%까지 줄일 수 있으므로 리소스 다운로드 시간을 크게 줄이고 클라이언트의 데이터 사용량을 줄이며 페이지의 첫 번째 렌더링 시간을 개선할 수 있습니다.
자세한 내용은
GZIP을 사용한 텍스트 압축을 참고하세요.
권장사항
웹 서버에서 gzip 압축 지원을 사용 설정하고 테스트하세요. HTML5 상용구 프로젝트에는
가장 많이 사용되는 모든 서버의 샘플 구성 파일이
각 구성 플래그 및 설정에 관한 자세한 설명과 함께 포함되어 있습니다.
목록에서 원하는 서버를 찾아 gzip 섹션을 찾아 서버가 권장 설정으로 구성되었는지
확인하세요.
압축을 사용 설정하는 방법은 웹 서버 문서를 참고하세요.
gzip 압축을 사용하여 파일을 전송하도록 웹 서버를 구성했는데,
PageSpeed Insights에서 많은 정적 콘텐츠 파일을 gzip으로 압축해야 한다고 보고합니다.
PageSpeed Insights에서 압축을 인식하지 못하는 이유가 무엇인가요?
프록시 서버 및 바이러스 백신 소프트웨어는 클라이언트 시스템에 파일을 다운로드할 때 압축을 사용 중지할 수
있습니다. PageSpeed Insights의 결과는 클라이언트에 실제로 반환된 헤더를
기반으로 하므로, 바이러스 백신 소프트웨어를 사용하거나 중간 프록시 서버 뒤에 있는 클라이언트
시스템에서 분석하는 경우 이러한 문제가 생길 수 있습니다. 많은 프록시는 투명하기 때문에 클라이언트와
웹 서버 사이에 프록시가 있음을 인식하지 못할 수 있습니다.
[null,null,["최종 업데이트: 2025-07-25(UTC)"],[[["\u003cp\u003eThis documentation applies to a deprecated version of PageSpeed Insights (v4) and will be shut down soon; users should refer to the latest version (v5).\u003c/p\u003e\n"],["\u003cp\u003eThe primary focus of this document is to explain how enabling GZIP compression can significantly improve website performance by reducing file sizes.\u003c/p\u003e\n"],["\u003cp\u003ePageSpeed Insights may report compression issues due to interference from proxy servers or anti-virus software affecting the headers returned to the client.\u003c/p\u003e\n"],["\u003cp\u003eModern browsers inherently support GZIP compression, so enabling it on your web server is crucial for optimization.\u003c/p\u003e\n"],["\u003cp\u003eThis page offers guidance and links to resources on how to enable GZIP compression for various web servers like Apache, Nginx, and IIS.\u003c/p\u003e\n"]]],["PageSpeed Insights flags resources served without `gzip` compression, which can reduce response size by up to 90%. Modern browsers support `gzip`, improving download time and data usage. To resolve this, enable and test `gzip` on your server, using tools like `mod_deflate` for Apache, `ngx_http_gzip_module` for Nginx, or configure HTTP compression in IIS. Proxy servers or anti-virus software can interfere with compression, impacting PageSpeed Insights' results.\n"],null,["# Enable Compression\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.\nThis rule triggers when PageSpeed Insights detects that compressible resources were served without `gzip` compression.\n\n### Overview\n\nAll modern browsers support and automatically negotiate `gzip` compression for all HTTP requests. Enabling `gzip` compression can reduce the size of the transferred response by up to 90%, which can significantly reduce the amount of time to download the resource, reduce data usage for the client, and improve the time to first render of your pages. See [text compression with GZIP](/web/fundamentals/performance/optimizing-content-efficiency/optimize-encoding-and-transfer#text-compression-with-gzip) to learn more.\n\n### Recommendations\n\nEnable and test gzip compression support on your web server. The HTML5 Boilerplate project contains [sample configuration files](https://github.com/h5bp/server-configs) for all the most popular servers with detailed comments for each configuration flag and setting: find your favorite server in the list, look for the `gzip` section, and confirm that your server is configured with recommended settings. Alternatively, consult the documentation for your web server on how to enable compression:\n\n- Apache: Use [mod_deflate](http://httpd.apache.org/docs/current/mod/mod_deflate.html)\n- Nginx: Use [ngx_http_gzip_module](http://nginx.org/en/docs/http/ngx_http_gzip_module.html)\n- IIS: [Configure HTTP Compression](http://technet.microsoft.com/en-us/library/cc771003(v=WS.10).aspx)\n\nFAQ\n---\n\nPageSpeed Insights reports that many of my static content files need to be gzipped,\nbut I have configured my web server to serve these files using gzip compression.\nWhy is PageSpeed Insights not recognizing the compression?\n:\n Proxy servers and anti-virus software can disable compression when files are downloaded to a\n client machine. PageSpeed Insights' results are based on headers that were actually returned\n to your client, so if you are running the analysis on a client machine that is using such\n anti-virus software, or that sits behind an intermediate proxy server (many proxies are\n transparent, and you may not even be aware of a proxy intervening between your client and\n web server), they may be the cause of this issue.\n\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)."]]
