WP-Optimize
by TeamUpdraft
Database cleanup, revision control and a competent page cache.
This link may earn us a commission. It does not affect the score. Last tested 27 August 2026.
Measured result
WP-Optimize on bench-01
Performance score
Measured on a 2 vCPU reference host
- LCP
- 1.58 s
- CLS
- 0.02
- TTFB
- 214 ms
- Page
- 596 KB
- Requests
- 32
- Impact
- Medium
Median of 3 cold-cache runs, 27 August 2026.
How we tested
Where WP-Optimize ranks elsewhere
| Publisher | List | Position |
|---|---|---|
| Elegant Themes | Best WordPress Plugins | #11 of 40 |
Positions are read from the published articles themselves, so they reflect that publisher's order rather than ours. Lists get re-ordered over time, so follow the link if you want the current version.
What changed in the latest version
- FIX: CSS exclusions added via Minify -> Advanced -> Exclude are now saved on separate lines, preventing invalid exclusion entries
- FIX: Fixed compatibility issue with the WooCommerce multi-currency plugin
- FIX: Incorrect WebP browser detection for Firefox users
- FIX: Misaligned UI issue in minify admin pages
- FIX: Mobile UI issues
- FIX: Prevent caching pages when a WooCommerce cart has content
- FIX: UI freezes when restoring a compressed image
- REFACTOR: Use WP_Optimize_Utils::get_url_without_cache_purge_params() for admin bar links
- FEATURE: Premium - Automatically preloads the page's Largest Contentful Paint (LCP) element to improve initial load speed and perceived performance
- FIX: Cache - Fixed an issue related to cache setting saving
- FIX: Fixed a UI issue in WooCommerce variation products when Automatically preload content after it is purged is enabled
- FIX: Fixed browser caching issue where admin pages were cached
- FIX: Mobile UI issue
- FIX: Notice Dismissal issue
- FIX: Usage of htmlspecialchars()
- REFACTOR: Code from can_purge_cache() method moved to WP_Optimize_Utils::current_user_can_purge_cache()
- TWEAK: Update the bundled common-libs version
Release notes are the developer's own words, published on WordPress.org. Read the full changelog
Pros & cons
- Removes revisions, transients and orphaned metadata
- Cache, images and database in one plugin
- Scheduled cleanups with a retention window
- Cleanup on a large database can lock tables
- Cache module is competent rather than best in class
The full review
Database weight is a quiet cause of slow admin screens and slow uncached pages. On a five-year-old reference site, removing 41,000 revisions and 6,800 expired transients cut the database from 1.4 GB to 380 MB and TTFB by 71 ms.
Always back up before the first run, and keep a retention window of at least two revisions per post.
Compared with close alternatives
| Plugin | Score | LCP | Price |
|---|---|---|---|
| WP-Optimize | 83 | 1.58 s | Freemium |
| Advanced Database Cleaner | 80 | 1.63 s | Freemium |
| Perfmatters | 95 | 1.18 s | $29/yr |
Frequently asked
How often should cleanups run?
Weekly is plenty for most publishing sites. Daily only makes sense on stores that generate large volumes of transient data.
Related