If your Plesk managed website or server is seemingly slow, there are several things to check and consider. Here are 22 Ways To Speed-Up A Plesk Website:
Check Time To First Byte (TTFB) value for static (e.g. .html files) and dynamic (e.g. .php files) content. If the value is more than one second, follow the steps from this article to troubleshoot the web server further:
Another reason can be due to exceeded FcgidMaxProcesses processes. Increasing FcgidMaxProcesses limit:
If you’ve reached the pm.max_children PHP-FPM limit, this will cause slowdowns, timeouts, or errors. Increasing the pm.max_children limit:
Also, basic checking for a possible DDoS attack can be performed:
Plesk offers some DDoS protection extensions:
Updated CMS, plugins, and themes periodically require higher PHP version. Switch PHP to highest possible version in Domains > example.com > Hosting Settings
In some cases, a newer version of PHP must be installed on the server:
PHP 8 allows opcache to speedup websites:
The slow query log can be used to find queries that take a long time to execute and are therefore candidates for optimization. Activate MySQL slow query log and make sure that there are no entries:
Contact website developer if slow queries are found.
The article: “How to troubleshoot slow performance of MySQL on a Plesk server?” – can help to investigate MySQL performance issue:
Try to open the website from a workstation in the other physical location (webpagetest.org or tools.pingdom.com). If from the other location/network it opens fine, contact your system administrator to test network connection bandwidth (iperf) and stability (mtr):
If you’re short on bandwidth and use your Plesk server as your own name server, consider using a third-party DNS.
If the website is “heavy”, optimize its size by compressing images, for example:
To analyze the code for optimization (decrease execution time for scripts) contact your website developer. Optimized code is handled by web browsers faster.
To reduce the size of transmitted data GZip compression can be enabled:
You can improve the work of Apache by using nginx, a supplementary high-performance web server which is typically used as a reverse proxy server. As opposed to Apache, nginx is much more efficient when it comes to handling a large number of concurrent connections. Another advantage is that nginx has a significantly smaller memory footprint per client connection.
Enabling nginx reverse proxy:
Configure nginx caching for website to speed delivery to clients and reduce the load on the server:
Look for errors or warnings in domain’s logs that could be consuming valuable resources and time:
Consider checking out the Speed Kit extension:
Use Plesk’s new “Performance Booster” to automatically enhance your website’s performance:
Enable a content delivery network (CDN) to provide faster website loading speeds to visitors worldwide. CloudFlare offers a free option for their basic CDN.
Update your server. Plesk manages two types of updates: system updates and Plesk updates. System updates use the operating system’s default package manager to update system packages (i.e. apt in Ubuntu). Plesk updates maintain updates to the third-party components shipped with Plesk (i.e. Apache, Dovecot). Be sure to update both for optimal performance.
System updates are available in Plesk under Tools & Settings > System Updates.
Plesk updates are available in Plesk under Tools & Settings > Updates.
Upgrade your server. If your websites are hefty enough or get enough traffic, you may need to consider upgrading for more resources: RAM, CPU, and disk space. This may mean upgrading a cloud server, manually adding resources to server hardware, or migrating to a larger server.
Consider a better host. If you are limited by your host’s server or bandwidth limitations, you should browse the market for something reliable, fast, and not overly-expensive from a company with a legitimate history.