• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Resolved Performance Booster - not working Compress gzip

kalombo

Basic Pleskian
Hi,

I have enabled performance Booster on our domain: KALOMBO when testing it on Pingdom Tools, it shows that Compress components with gzip, even when this function is enabled. Could you please advise?
 

Attachments

  • Screenshot_20230912_135728_Chrome.jpg
    Screenshot_20230912_135728_Chrome.jpg
    270 KB · Views: 7
Can you see more details which components are not compressed? Some formats like .jpeg/.jpg, .mpeg and archives like .tar.gz, .gz, .zip etc. may be delivered without additional compression, because such an additional compression on files that are already compressed formats create unnecessary cpu time load.
 
Thanks for your reply. 90% of our images are in webp and some png. In the format you ve mentioned there is none of our format. How can we compress them using performance Booster?
 
Hi,

It could be a problem of false expectations, but Performance Booster does not perform data compression. It configures the server so that the optimal parameters of PHP and the web server are used and that gzip and brotli compression are configured.
 
I have added this directive for nginx

gzip_types text/plain text/css application/javascript application/x-javascript text/xml application/xml application/rss+xml text/javascript image/x-icon image/bmp image/svg+xml image/webp image/png;
 
Remove all custom nginx directives you have added and enable the "Speed up web server compression" checkbox in Performance Booster.

What result have you got?
 
Remove all custom nginx directives you have added and enable the "Speed up web server compression" checkbox in Performance Booster.

What result have you got?
The result I have sent you before is with enable " speed up web server compression "
 
Please, check the configure arguments with the following command:
nginx -V

Are there these arguments?
--with-http_gzip_static_module --add-dynamic-module=mod_brotli
 
Here
Please, check the configure arguments with the following command:
nginx -V

Are there these arguments?
--with-http_gzip_static_module --add-dynamic-module=mod_brotli
Is the outcome for this command
 

Attachments

  • Screenshot_20230912_135728_Chrome.jpg
    Screenshot_20230912_135728_Chrome.jpg
    270 KB · Views: 6
The Pingdom Tools does not support the most modern compression algorithm - brotli. Nginx on your server uses Brotli firstly.

gzip also works if asked explicitly:

curl --compressed -k -vvv https://kalombo.ru

* Trying 49.12.134.105:443...
* Connected to kalombo.ru (49.12.134.105) port 443 (#0)
* ALPN: offers h2,http/1.1
* (304) (OUT), TLS handshake, Client hello (1):
* (304) (IN), TLS handshake, Server hello (2):
* (304) (IN), TLS handshake, Unknown (8):
* (304) (IN), TLS handshake, Certificate (11):
* (304) (IN), TLS handshake, CERT verify (15):
* (304) (IN), TLS handshake, Finished (20):
* (304) (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / AEAD-CHACHA20-POLY1305-SHA256
* ALPN: server accepted h2
* Server certificate:
* subject: CN=kalombo.ru
* start date: Jul 21 17:57:28 2023 GMT
* expire date: Oct 19 17:57:27 2023 GMT
* issuer: C=US; O=Let's Encrypt; CN=R3
* SSL certificate verify ok.
* using HTTP/2
* h2 [:method: GET]
* h2 [:scheme: https]
* h2 [:authority: kalombo.ru]
* h2 [user-agent: curl/8.1.2]
* h2 [accept: */*]
* h2 [accept-encoding: deflate, gzip]
* Using Stream ID: 1 (easy handle 0x13f80bc00)
> GET / HTTP/2
> Host: kalombo.ru
> User-Agent: curl/8.1.2
> Accept: */*
> Accept-Encoding: deflate, gzip
>
< HTTP/2 200
< server: nginx
< date: Tue, 12 Sep 2023 16:26:26 GMT
< content-type: text/html; charset=UTF-8
< x-powered-by: PHP/8.2.10
< pragma: no-cache
< cache-control: max-age=0, must-revalidate, no-cache, no-store
< expires: Mon, 12 Sep 2022 16:16:24 GMT
< x-content-type-options: nosniff
< x-xss-protection: 1; mode=block
< x-frame-options: SAMEORIGIN
< set-cookie: PHPSESSID=2n8j111n57ac5n23lv5i5kg7ig; expires=Fri, 22 Sep 2023 16:26:26 GMT; Max-Age=864000; path=/; domain=kalombo.ru; secure; HttpOnly; SameSite=Lax
< x-permitted-cross-domain-policies: none
< expect-ct: max-age=86400, enforce
< vary: User-Agent
< x-ua-compatible: IE=edge
< access-control-allow-methods: GET,PUT,POST,DELETE,OPTIONS
< access-control-allow-headers: x-requested-with
< x-powered-by: PleskLin
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< content-security-policy: frame-ancestors 'self';
< content-encoding: gzip
 
As per your demonstration and also I checked. Definitely agreed that the tool doesn't support brotli in consequence showing compression issue. In this case, this is not an issue but tool error. Thanks for your time spent on this.
 
Back
Top