WordPress Server Optimization: We Went from 3 Seconds to 0.4 Seconds
Last month an agency called: "Our WordPress site is very slow and customers are complaining." We looked at the site: a 3.2-second load time. 2 days later: 0.4 seconds. Magic? No, the right optimization. In this article we explain how we optimise a WordPress site, which tools we use and what you need to watch out for. Spoiler: we did not buy a single premium plugin.
Why Does WordPress Slow Down?
The reason WordPress is slow is usually not WordPress itself, but poor configuration and unnecessary plugins. In the analysis we carried out in 2024, the common problems of slow WordPress sites were:
- 25+ plugins: Every plugin means extra queries
- Unoptimised images: 5 MB PNG files
- Shared hosting: 200 sites on the same server
- No cache: PHP runs for every visitor
- Old PHP version: Using PHP 7.4 instead of 8.2
WordPress Optimization in 7 Steps
Step 1: Choosing the Right Hosting
The most important decision: the choice of server. Moving from shared hosting to a VPS can deliver a 60% performance gain on its own.
SistemDC WordPress Recommendations:
- Small blog (1,000 visits/day): VPS 4 GB RAM
- Mid-sized site (10,000 visits/day): VPS 8 GB RAM + LiteSpeed
- E-commerce (WooCommerce): Dedicated Server 16 GB+ RAM
Step 2: Installing LiteSpeed + LSCache
Using LiteSpeed instead of Apache delivers the biggest performance gain for WordPress. Why?
- 5x faster than Apache
- Built-in optimization with the LSCache plugin
- HTTP/3 support
- Low RAM usage
# LiteSpeed installation (Ubuntu 24.04)
wget -O - https://repo.litespeed.sh | sudo bash
sudo apt install openlitespeed
# LSCache plugin (from the WordPress admin panel)
# Plugins > Add New > search "LiteSpeed Cache" > Install
Step 3: Redis Object Cache
WordPress sends dozens of queries to the database on every page. Redis caches these queries in RAM.
# Redis installation
sudo apt install redis-server
sudo systemctl enable redis-server
# WordPress plugin
# Install the "Redis Object Cache" plugin
# Add to wp-config.php:
define('WP_REDIS_HOST', '127.0.0.1');
define('WP_REDIS_PORT', 6379);
Conclusion: The number of database queries falls by 70% and page load gets 40% faster.
Step 4: Image Optimization
60-70% of a WordPress site is images. Optimization is a must:
- Use the WebP format: 30% smaller than PNG/JPEG
- Lazy loading: Images that are not in view are not loaded
- Use a CDN: Images are served from a nearby server
- Responsive images: Smaller sizes on mobile
A Real Case: A photographer's portfolio site was loading 50 MB of images. After WebP + lazy loading: 8 MB. Load time fell from 8 seconds to 1.2 seconds.
Step 5: Database Cleanup
The WordPress database bloats over time: post revisions, spam comments, transient data.
# Cleanup with WP-CLI
wp post delete $(wp post list --post_type='revision' --format=ids)
wp comment delete $(wp comment list --status=spam --format=ids)
wp transient delete --all
# Database optimization
wp db optimize
Conclusion: One customer's 2.3 GB database fell to 480 MB. Query speed rose by 50%.
Step 6: PHP 8.2 and OPcache
PHP 8.2 is 30% faster than PHP 7.4. OPcache keeps PHP code in compiled form.
# PHP 8.2 installation
sudo apt install php8.2-fpm php8.2-mysql php8.2-redis
# OPcache settings (php.ini)
opcache.enable=1
opcache.memory_consumption=256
opcache.max_accelerated_files=10000
opcache.revalidate_freq=60
Step 7: CDN Integration
A CDN (Content Delivery Network) serves static files from the server closest to the user.
- Cloudflare (Free): DNS + CDN + SSL
- BunnyCDN: Prices starting from $1 a month
- KeyCDN: Pay-as-you-go model
Setup: Configure the CDN settings in the LSCache plugin and images are served from the CDN automatically.
Real Performance Tests: Before vs After
Test Site: E-commerce (WooCommerce, 2,500 products)
BEFORE (Shared Hosting + Apache):
- Page load: 3.2 seconds
- Server response time (TTFB): 1.8 seconds
- Page size: 8.4 MB
- Requests: 142
- Google PageSpeed: 32/100
AFTER (SistemDC VPS + LiteSpeed + Redis + Optimization):
- Page load: 0.4 seconds
- Server response time (TTFB): 0.08 seconds
- Page size: 1.2 MB
- Requests: 38
- Google PageSpeed: 94/100
Conclusion: 87% faster, 73% less bandwidth, and the conversion rate rose by 23%.
SistemDC WordPress Hosting Plans
We have specialised in WordPress hosting since 2012. An optimised infrastructure with ready-made configuration:
WordPress Starter - 600 TL/mo
- 4 GB RAM, 4 vCore
- 100 GB NVMe SSD
- LiteSpeed + LSCache (pre-installed)
- Redis Object Cache
- PHP 8.2 + OPcache
- Daily automatic backups
- Capacity for 10,000 visits/day
WordPress Professional - 1,500 TL/mo
- 16 GB RAM, 8 vCore
- 300 GB NVMe SSD
- All optimizations + CDN
- Elasticsearch (for WooCommerce)
- Hourly backups
- Capacity for 100,000 visits/day
- Optimised for WooCommerce
Common Mistakes
Mistake 1: Too Many Plugins
We see WordPress sites with 40+ plugins installed. The rule: keep it under 15 and delete the unnecessary ones.
Mistake 2: Using Free Themes
Nulled (pirated) or low-quality themes may contain hidden code. Use a premium theme (GeneratePress and Astra are recommended).
Mistake 3: Not Taking Backups
A site can break during optimization. Always take a backup first.
Monitoring: Keep an Eye on Performance
Optimization is not a one-off job; it needs continuous follow-up:
- Google PageSpeed Insights: Weekly check
- GTmetrix: Detailed analysis
- Query Monitor (plugin): Detecting slow queries
- New Relic / Scout APM: Professional monitoring
Is Your WordPress Site Slow?
Let us run a free speed analysis. We will review your site and show you where the problem is.
Contact:
satis@sistemdc.com
Corporate WhatsApp: +90 224 334 02 42
Conclusion: Speed = Conversion
According to Google's research, when page load time rises from 1 second to 3 seconds, the bounce rate increases by 32%. At 5 seconds it increases by 90%.
In other words, a fast site = more sales, better SEO and happy users.
We have optimised hundreds of WordPress sites over 14 years. Our experience: the right server + the right optimization = a performance gain of 80%+ is possible.
Note: The commands in this article apply to Ubuntu 24.04 and Debian-based systems. The performance tests were carried out with real sites on SistemDC infrastructure. Results may vary depending on the site structure.
Turkey (Türkçe) 
