Quick answer: The complete tuning pass in one list — measure, cache at every layer, tune PHP and the database, slim the payload, re-measure. Each line links to the full guide. A VPS that ticks every box serves cached pages in tens of milliseconds and uncached ones comfortably under a second.
Overview
This is the condensed counterpart to improving WordPress speed — useful when commissioning a new site or hunting a regression. Order matters: measuring brackets the work, caching gives the biggest wins, micro-optimizations come last.
Before you start
- A measuring habit: PageSpeed Insights / WebPageTest for the visitor view,
htop+ Query Monitor for the server view. - Baseline numbers recorded — you can’t improve what you didn’t measure.
Step-by-step guide
Measure:
- ☐ Baseline TTFB, LCP and admin responsiveness noted.
Cache:
- ☐ Exactly one full-page cache active and verified by response header (guide).
- ☐ WooCommerce: cart/checkout/account excluded (details).
- ☐ Redis object cache connected, hit ratio checked (setup).
- ☐ OPcache enabled with adequate memory (PHP tuning).
- ☐ Browser caching: 30-day expires on static assets.
Tune:
- ☐ PHP 8.3; FPM pool sized to RAM (formula).
- ☐ InnoDB buffer pool sized; slow-query log reviewed (database guide).
- ☐ Autoloaded options under ~800 KB; expired transients purged.
- ☐ WP-cron replaced by system cron on busy/commerce sites.
Slim:
- ☐ Images WebP + lazy loading; no multi-MB heroes.
- ☐ Unused plugins deactivated and deleted; heavy ones justified by Query Monitor data.
- ☐ Theme lean, or builder output cached aggressively.
Re-measure:
- ☐ Same tests as the baseline; numbers recorded. Cache-hit TTFB still slow? The plan is undersized — consider NVMe/Power VPS.
Common issues
- Optimizing without measuring: effort lands on the wrong layer — always bracket with tests.
- Plugin stacking: three optimization plugins fight each other — one page cache, one image tool, one object cache.
- Testing only the front page: archives, search and checkout are where regressions hide.
When to contact support
All boxes ticked and the site still slow at the platform level (steady CPU saturation, IO wait)? Open a ticket with your measurements to right-size an upgrade.
Frequently asked questions
What order should I apply performance fixes in?
Measure first, then page cache, object cache and OPcache, then PHP/database tuning, then media and plugin cleanup — and re-measure after each layer to see what actually helped.
How fast should a well-tuned WordPress site be?
Cached pages should show TTFB in the tens of milliseconds from a nearby region; uncached pages (checkout, admin) should stay comfortably under one second on adequate hardware.
When is it time to upgrade the VPS instead of optimizing more?
When cache hits are confirmed fast but uncached requests stay slow with CPU or disk saturated — tuning cannot conjure resources the plan does not have.
Related articles
- How to improve WordPress speed on a VPS
- How to configure Redis object cache
- How to optimize PHP for WordPress
- How to optimize MariaDB for WordPress
Ready to get started? Order a WordPress VPS at Cloud2Y →
