Checking and enabling website compression in cPanel

Choose a public text page to test and note whether the site uses a caching plugin, LiteSpeed or a CDN. Keep a copy of the current .htaccess file. Compression does not usually help already compressed images or archives, and it does not correct slow application queries.

1. Open browser developer tools, reload the page and inspect its response headers. Look for Content-Encoding, which may already be gzip or br.
2. If cPanel provides Optimize Website, open it and review the current setting. Choose the appropriate compression option for text content supported by the server, then save.
3. Reload an uncached test response and inspect the encoding again. If a CDN serves the response, also confirm the origin setting through your normal support or developer workflow.
4. Leave PHP zlib.output_compression alone unless the application or hosting configuration specifically requires it. Turning on both PHP and server compression without checking their interaction can break output.

From your workstation, request a public text page with curl and ask it to negotiate supported compression. Replace example.com with the website. This command downloads a normal GET response, displays its headers and discards the body locally.

curl --silent --show-error --compressed \
  --connect-timeout 10 --max-time 20 \
  --dump-header - --output /dev/null https://example.com/

Read the result: Look for Content-Encoding such as gzip or br. A CDN or reverse proxy may apply the encoding, so this describes the response received by the client rather than proving a particular cPanel setting is responsible. curl supports only the compression algorithms included in its build.

Compare equivalent requests to the same page before and after a reviewed configuration change. Images and archives may already be compressed and need no additional encoding. If the application deliberately disables compression for a sensitive response, investigate its reason before overriding the setting.

Check the homepage, CSS, scripts, downloads and a form submission. Compare transferred size on equivalent requests, allowing for browser and CDN caches.

If pages become blank, corrupted or repeatedly download incorrectly, revert the compression change and restore the relevant configuration backup. A missing Optimize Website tool can mean the server handles compression elsewhere; ask support rather than pasting arbitrary handler directives.

• Finding and editing .htaccess in cPanel
• Editing a text file in cPanel File Manager
• Selecting a PHP version for a cPanel domain
• Changing or recovering your cPanel password

• cPanel documentation

• curl command reference