Plesk Performance Optimisation

The Problem

Sites on your Plesk server feel sluggish, and the default settings Plesk ships with are rarely tuned for the amount of RAM, CPU or traffic you actually have.

About this problem

Plesk's defaults are deliberately conservative so a fresh install works on almost any VPS size, which means a server with real RAM and CPU to spare is often running PHP-FPM pools, caching and database settings sized for a much smaller box. The slowdown isn't usually one dramatic misconfiguration — it's several modest ones compounding across every site on the server.

This usually surfaces once traffic grows past what the site felt like when it first launched, or after moving several sites onto one Plesk server without revisiting the defaults.

What's Included

• Reviewing PHP-FPM pool settings and memory limits per site
• Tuning the web server (Nginx/Apache) and enabling caching where useful
• Checking database (MySQL/MariaDB) configuration against available resources
• Before/after performance comparison

What's NOT Included

• Upgrading your VPS plan — that's a decision for you and your host
• Application-level code optimisation
• CDN setup (can be scoped separately)

How It Works

1. Review PHP-FPM pool settings (max children, memory limits) against actual available RAM and site count.
2. Check Nginx/Apache configuration for caching headers and gzip/brotli compression status.
3. Review MySQL/MariaDB buffer and connection settings against the server's resources.
4. Enable or tune available caching layers appropriate to each site's platform.
5. Run before/after load time measurements on the affected site(s) to confirm a real improvement.

In practice: you buy the service, send over whatever access or details the job needs, I investigate and do the work, and you confirm it's resolved before we call it done.

Frequently Asked Questions

Why is my website slow even though my VPS has plenty of resources?

Plesk's default PHP, web server and database settings are sized conservatively and rarely match what a server with real RAM and CPU can actually handle — the resources are there but not being used.

Will upgrading my VPS plan fix slow Plesk sites?

Sometimes, but often the bigger gain comes from tuning settings to actually use the resources you already have — upgrading first without tuning can mask the real issue.

Does Plesk have built-in caching?

Depends on the extension set installed — options like Nginx caching, Redis, and Memcached are available but not enabled by default on most installs.

Can performance tuning break a working site?

It's low-risk when changes are tested incrementally with before/after measurements, which is the approach used here rather than changing everything at once.

How do I know if PHP-FPM is the bottleneck?

If pages queue or time out under moderate traffic while CPU/RAM still have headroom, PHP-FPM worker limits are usually the cause — checking the pool logs confirms this quickly.

Does this include optimising my site's actual code?

No — this is server and configuration-level tuning. Code-level optimisation (slow database queries, inefficient plugins) is a separate, more involved piece of work.