Optimize WordPress Performance on Ubuntu Server

Updated 6 November 2026 · Standard formula, shown below

This guide walks you through the key steps to speed up a WordPress site running on an Ubuntu server. You’ll learn how to configure caching, optimize PHP, enable compression, and tune your web server for better performance. By the end, your site should load noticeably faster for visitors.

What You’ll Need

An Ubuntu server (20.04 or newer) with WordPress already installed.
Root or sudo access to the server.
SSH access to the server.
Basic familiarity with the command line.

Step-by-Step

Update your system and packages. Run sudo apt update && sudo apt upgrade -y to ensure your server has the latest security and performance patches.
Install a caching plugin. In your WordPress admin, install a caching plugin like W3 Total Cache or WP Super Cache. Activate it and enable page caching, browser caching, and object caching (if available). This alone can dramatically reduce server load.
Configure PHP-FPM for better performance. Edit your PHP-FPM pool configuration (usually at /etc/php/8.1/fpm/pool.d/www.conf). Adjust the pm setting to ondemand or dynamic and set pm.max_children based on your server’s RAM. For example, with 2GB RAM, set pm.max_children = 20. Restart PHP-FPM after changes.
Enable opcode caching. Ensure the PHP OPcache extension is enabled. Edit /etc/php/8.1/cli/conf.d/10-opcache.ini and set opcache.enable=1, opcache.memory_consumption=128, and opcache.max_accelerated_files=10000. Restart PHP-FPM.
Install and configure Redis for object caching. Install Redis with sudo apt install redis-server. Then install the Redis object cache plugin in WordPress (e.g., Redis Object Cache). Configure it to connect to 127.0.0.1 and enable it. This offloads database queries to memory.
Enable Gzip compression. If using Apache, enable mod_deflate: sudo a2enmod deflate and add compression rules to your .htaccess file. For Nginx, add gzip on; and gzip_types text/plain text/css application/json application/javascript text/xml application/xml application/xml+rss text/javascript; to your server block.
Set up browser caching. Add cache-control headers for static assets. In Apache, use mod_expires: sudo a2enmod expires and add rules to .htaccess to cache images, CSS, and JS for a month. In Nginx, add location ~* \.(jpg|jpeg|png|gif|ico|css|js)$ { expires 30d; }.
Optimize your database. Use a plugin like WP-Optimize or run manual SQL commands to clean up post revisions, spam comments, and transient options. Also, consider switching to InnoDB for all tables.
Configure a CDN. Sign up for a CDN service (e.g., Cloudflare, StackPath) and integrate it with your caching plugin. Serve static assets from the CDN to reduce load on your server and improve global latency.
Monitor and test. Use tools like GTmetrix or Google PageSpeed Insights to measure your site’s speed before and after changes. Also, check server resources with htop to ensure you’re not overloading the CPU or RAM.

Common Mistakes

Over-caching dynamic content. Caching everything can cause stale pages for logged-in users or dynamic elements. Ensure your caching plugin excludes pages with cart, checkout, or user-specific content.
Ignoring PHP version. Using an outdated PHP version (e.g., 5.6) can severely limit performance. Always use a supported, modern version like PHP 8.1 or 8.2.
Setting max_children too high. If you set PHP-FPM’s pm.max_children too high, you can exhaust memory and cause crashes. Calculate based on average PHP process size (usually 30-50MB) and available RAM.
Not enabling OPcache. OPcache is often disabled by default. Without it, PHP recompiles scripts on every request, wasting CPU.
Skipping database optimization. A bloated database with thousands of revisions can slow down queries. Regularly clean it.

Tips

Use a lightweight theme and avoid heavy page builders if possible. They add extra JavaScript and CSS that slow down rendering.
Lazy-load images and videos to reduce initial page weight.
Minify CSS and JavaScript files. Most caching plugins have this feature built-in.
Consider using a faster web server like Nginx instead of Apache for better concurrency and lower memory usage.
Regularly review your plugins and remove any that are not essential. Each plugin adds PHP execution time and potential database queries.

Troubleshooting

Site becomes slower after enabling a caching plugin. This can happen if the plugin’s settings are too aggressive or conflict with your server setup. Disable the plugin, then re-enable it with default settings and gradually adjust.
Redis connection fails. Check that Redis is running with sudo systemctl status redis-server. Ensure the WordPress plugin is configured with the correct host and port (default: 127.0.0.1:6379). If you set a password, add it to the plugin settings.
Gzip not working. Verify that the module is enabled and the configuration is correct. Test with curl -H "Accept-Encoding: gzip" -I http://yoursite.com and look for Content-Encoding: gzip in the response headers.
PHP-FPM fails to restart. Check the syntax of your pool configuration with sudo php-fpm -t. If there’s an error, it will tell you the line number to fix.
CDN not loading assets. Ensure your caching plugin’s CDN settings are correct, and that you’ve purged the CDN cache after making changes. Also, check that the CDN URLs are properly rewritten in the HTML source.

Frequently Asked Questions

Do I really need a caching plugin?

Yes, especially if you’re on a shared or low-resource VPS. Caching plugins generate static HTML pages, reducing PHP execution and database queries dramatically.

What’s the difference between page caching and object caching?

Page caching stores the fully rendered HTML output. Object caching stores database query results in memory (like Redis or Memcached) to speed up repeated queries.

Can I use both Redis and a page caching plugin?

Yes, they complement each other. Page caching handles the front-end, while Redis object caching speeds up the backend, especially for logged-in users and dynamic content.

How do I know if my server can handle more PHP-FPM workers?

Monitor memory usage with free -h. If you have plenty of free RAM and your site is slow, increase pm.max_children gradually. If memory usage is high, reduce it.

Is it worth switching from Apache to Nginx?

For high-traffic sites, Nginx generally uses less memory and handles concurrent connections better. However, if your site is small, the difference may be minimal. If you switch, ensure your .htaccess rules are translated to Nginx config.

Why is my site still slow after following all these steps?

Check the size of your images and the number of external scripts (trackers, fonts). Also, run a performance test to see which resources take the longest to load. Sometimes the bottleneck is on the client side, not the server.

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.