August 11, 2026 · by CLIQHOST
A slow WordPress site doesn't just frustrate visitors — it directly impacts your Google rankings and conversion rates. Studies consistently show that more than 53% of users abandon a page that takes longer than 3 seconds to load.
Speed is no longer a nice-to-have. In this guide, you'll find every concrete step to make your WordPress site faster, whether you're on shared cPanel hosting or a dedicated NVMe VPS.
You can't improve what you don't measure. Use these free tools:
Record your baseline: TTFB, LCP, and total page weight. After each optimization step, compare against your baseline.
The biggest speed gains often come from infrastructure, not plugins. A WordPress-optimized hosting plan with SSD or NVMe storage dramatically reduces server response time (TTFB).
If your site handles consistent traffic or you're running a WooCommerce store, consider moving to a SSD VPS — dedicated resources, no noisy neighbours.
For high-demand projects, a dedicated server offers the ultimate performance ceiling with full resource control.
Target TTFB: under 200ms. Check it in browser DevTools (Network tab → first request → TTFB).
Caching is the single fastest way to speed up WordPress. Instead of dynamically generating every page on every visit, the server delivers a pre-built HTML file.
| Plugin | Free | cPanel Compatible |
|---|---|---|
| WP Super Cache | ✅ | ✅ |
| W3 Total Cache | ✅ | ✅ |
| LiteSpeed Cache | ✅ | ✅ (LiteSpeed server required) |
| WP Rocket | ❌ (premium) | ✅ |
EN
RO — Română
RU — Русский
Plugins → Add NewSettings → WP Super CacheImages typically account for 60–80% of a page's total weight. There are three angles of attack:
Use ShortPixel, Imagify, or Smush for automatic compression on upload. Set JPEG quality to 80–85% — the visual difference is imperceptible.
WebP is 25–35% smaller than JPEG at equivalent quality. ShortPixel and Imagify convert automatically. All modern browsers (Chrome, Firefox, Safari) support WebP natively.
WordPress 5.5+ applies lazy loading natively — the loading="lazy" attribute is added to all <img> tags automatically.
<!-- WordPress adds this automatically: -->
<img src="photo.jpg" loading="lazy" alt="Description" />
Every CSS and JavaScript file is a separate HTTP request. Minification removes whitespace and comments; combining reduces request count.
Minify tab: enable CSS, JS, and HTML minificationFile Optimization: minify + defer JS execution⚠️ Warning: Combining JS files can break some plugins. Always test on a staging environment before deploying to production.
Server-level compression reduces HTTP response sizes by 60–80%.
.htaccess:<IfModule mod_deflate.c>
AddOutputFilterByType DEFLATE text/html text/plain text/xml
AddOutputFilterByType DEFLATE text/css application/javascript
AddOutputFilterByType DEFLATE application/json application/xml
</IfModule>
Verify compression is active at GiftOfSpeed GZIP Test.
A CDN stores copies of your static files (images, CSS, JS) on servers distributed globally. Each visitor downloads files from the nearest node.
Cloudflare (free plan) is the easiest starting point:
1. Create an account at cloudflare.com
2. Add your domain and update nameservers at your registrar
3. Enable the proxy (orange cloud icon) for your records
4. Set Cache Level: Standard and Browser Cache TTL: 4 hours
For WooCommerce stores with international audiences, a CDN can reduce LCP by 40–60%.
WordPress stores everything in MySQL. Over time, wp_options grows bloated with post revisions, spam comments, and expired transients.
-- Remove auto-drafts
DELETE FROM wp_posts WHERE post_status = 'auto-draft';
-- Remove all revisions
DELETE FROM wp_posts WHERE post_type = 'revision';
-- Clean expired transients
DELETE FROM wp_options WHERE option_name LIKE '%_transient_%';
⚠️ Always take a full backup before any database operations!
Every active plugin adds PHP code that runs on every request. A simple audit:
Golden rule: If you're not actively using a plugin, deactivate it and delete it.
For detailed analysis, Query Monitor clearly shows which database queries and plugins slow down each page.
PHP 8.2 or 8.3 is approximately 40% faster than PHP 7.4. Change your PHP version in cPanel → MultiPHP Manager in a few clicks.
Recommended php.ini settings for WordPress:
memory_limit = 256M
max_execution_time = 60
upload_max_filesize = 64M
post_max_size = 64M
opcache.enable = 1
opcache.memory_consumption = 128
OPcache caches compiled PHP bytecode, eliminating recompilation on every request — a significant CPU load reduction.
HTTP/2 allows request multiplexing — multiple resources delivered over a single TCP connection. All CLIQHOST plans support HTTP/2 by default.
Verify: curl -I --http2 https://yourdomain.com — the response should include HTTP/2 200.
WordPress speed optimization is an iterative process, not a one-time task. Start with the highest-impact factors — hosting, caching, and images — measure the results, then work through the rest of the checklist.
If your site has outgrown shared hosting, the CLIQHOST team can recommend the right solution: from WordPress hosting to a fully powered NVMe VPS. Browse our options or check the CLIQHOST blog for more technical guides — or get in touch directly and we'll help you find the right configuration.
Real reviews from customers who trust CLIQHOST for performance, reliability and expert technical support.
"We moved our online shop from a foreign host and the difference is night and day — pages load instantly and support replies in minutes, in Romanian."
"Migrated 12 client sites to CLIQHOST. Free migration, zero downtime, and the cPanel setup is exactly what my team needed. Highly recommend."
"Our NVMe VPS handles traffic spikes without a sweat. Full root, local datacenter, and billing in MDL — everything we wanted from a provider."
