How to Improve WordPress Performance

kim

Currently, my website is hosted on a Hostinger VPS with Enhance panel installed manually. When I open the Elementor editor for pages that include Tabs, the editor becomes extremely slow. My computer CPU temperature quickly rises above 90°C, and Google Chrome consumes a huge amount of memory.

However, when I migrate the same website to Hostinger Shared Hosting, with the same PHP and WordPress configuration, the Elementor editor works smoothly without any performance issues.

It seems that the problem is related to the VPS server environment or configuration, but I cannot find the proper settings to optimize PHP-FPM, OPcache, or MariaDB in the Enhance panel. Could you please help me optimize the VPS environment for Elementor to improve editor performance?

sebastianahumada

Hello! Maybe it’s a server issue, and in many cases it happens because the VPS is very limited or the host is oversold.

Optimizing a server requires knowledge and detailed hardware information in order to properly fine-tune MariaDB and PHP.

If you’re just starting with Enhance, I recommend using Apache — it’s your best friend at the beginning. Also, use PHP 8.2+ for WordPress and set the PHP memory limit to 512 MB or more.

At the start, you don’t really need to touch MariaDB. As long as the server isn’t overloaded, WordPress with Elementor should run smoothly.

To be able to help you further, it would be great if you could share more info about your VPS: how many CPU cores and how much RAM it has. Please also run a YABS test to see the performance and help us configure MariaDB correctly.
👉 Run this command via SSH:

curl -sL https://yabs.sh | bash -s -- -i

(No need to test the network, so this version skips it. It will take just a few minutes.)

Once you have this data, come back here and I’ll help you with the configurations.

For reference, I manage an e-commerce site with over 8,000 users on WooCommerce, and I run it with Apache + Redis on a well-optimized server — and it works perfectly fine. 🙂

MarkNLD

kim To help you debug the issue you will need to run the command that sebastianahumada mentioned. The problem that you are experiencing is most likely caused by Hostinger VPS being oversold (that's why they are so cheap).

kim

sebastianahumada Wed Sep 17 08:08:00 UTC 2025

Basic System Information:

Uptime : 1 days, 18 hours, 13 minutes
Processor : AMD EPYC 9354P 32-Core Processor
CPU cores : 4 @ 3245.124 MHz
AES-NI : ✔ Enabled
VM-x/AMD-V : ❌ Disabled
RAM : 15.6 GiB
Swap : 0.0 KiB
Disk : 193.7 GiB
Distro : Ubuntu 24.04.3 LTS
Kernel : 6.8.0-79-generic
VM Type : KVM
IPv4/IPv6 : ✔ Online / ✔ Online

IPv6 Network Information:

ISP : HOSTINGER MY
ASN : AS47583 Hostinger International Limited
Host : Hostinger International Ltd.
Location : Kuala Lumpur, Kuala Lumpur (14)
Country : Malaysia

kim

Thanks for your reply! This problem has been bothering me for many days.
My vps: 4cpu 16G

I recorded the video.

Website Problem Screen Recording
https://e.pcloud.link/publink/show?code=XZTkGOZEiDbJc93aVj1bRR8zsyrzQWBfH0y

webdig

From what you’ve shared, the problem doesn’t seem to be with Elementor itself, but rather with the VPS environment.

Your instance shows 0 KiB of SWAP, and that’s critical: when editing with Elementor, there are spikes in RAM/CPU usage and without swap, the server chokes and the editor becomes sluggish.

Some quick optimizations you can apply:

Create swap (e.g. 8 GB) – this immediately helps with memory spikes.
Use PHP 8.2 or 8.3 with memory_limit = 512M and max_input_vars = 7000.
Redis Object Cache helps a lot in /wp-admin and in the editor.
If you’re using OpenLiteSpeed, limit PHP processes (PHP_LSAPI_CHILDREN=20–30). If you prefer Apache + FPM, set pm.max_children according to your RAM.
Tune MariaDB for your VPS (with 16 GB you can set innodb_buffer_pool_size=8G).

After these changes, restart the services (PHP, MariaDB, Redis) and test the editor again.

In summary: create swap, raise PHP limits, and enable Redis. That alone should make Elementor much more responsive on the VPS.
If you’re unsure how to do it, feel free to ask for help here in the community.

bluelinq-computers

webdig I second this about the VPS environment.

Also, a note about object cache. Yes, Redis Object Cache is great, but Object Cache Pro will give you the best performance hands down.

I highly recommend pairing either Redis Object Cache/Object Cache Pro with LiteSpeed Cache.

sebastianahumada

Hi! It’s me again. I noticed you shared part of the YABS output, but not the full test. I need to see the disk and CPU performance results in order to give you proper guidance.

Regarding swap, on all my servers I usually set it to 2G, and in some cases 4G—never more than that. Anything beyond is just wasted disk space.

From what I can see, the VPS processor looks very good. However, without the full test I can’t tell if the server is performing properly or if it’s heavily oversold. Also, let me know your location relative to the VPS data center, and try running a ping test so we can check the connection latency (ms).

For PHP input vars, set them to 10,000—no higher than that.

I also watched the video, and let me say this: you should consider testing your own internet connection as well, just in case. I’ve seen cases where the issue was actually caused by the ISP in relation to the server’s location.

Please come back with the full YABS disk and CPU results, and I’ll take care of guiding you further.

sebastianahumada

sebastianahumada I see you’re using the LiteSpeed Cache plugin. If your server is running Apache, clear the cache and then disable the plugin—just in case, as this could also be the cause of the issue.