Title: WP-Optimize – Cache, Compress images, Minify & Clean database to boost page speed & performance
Author: David Anderson / Team Updraft
Published: <strong>Ṣẹrẹ 21, 2009</strong>
Last modified: Ògún  13, 2026

---

Ṣàwárí àwọn plugin

![](https://ps.w.org/wp-optimize/assets/banner-772x250.png?rev=2125385)

![](https://ps.w.org/wp-optimize/assets/icon-256x256.png?rev=1552899)

# WP-Optimize – Cache, Compress images, Minify & Clean database to boost page speed & performance

 Láti ọwọ́ [David Anderson / Team Updraft](https://profiles.wordpress.org/davidanderson/)

[Ṣe ìgbàsílẹ̀](https://downloads.wordpress.org/plugin/wp-optimize.4.6.1.zip)

 * [Àwọn àlàyé](https://yor.wordpress.org/plugins/wp-optimize/#description)
 * [Àwọn àgbéyẹ̀wò](https://yor.wordpress.org/plugins/wp-optimize/#reviews)
 *  [Ìgbéwọlẹ̀](https://yor.wordpress.org/plugins/wp-optimize/#installation)
 * [Ìdàgbàsókè](https://yor.wordpress.org/plugins/wp-optimize/#developers)

 [Ìrànlọ́wọ́](https://wordpress.org/support/plugin/wp-optimize/)

## Àpèjúwe

MORE THAN A CACHING PLUGIN

**[WP-Optimize](https://www.teamupdraft.com/wp-optimize?utm_source=wpo-wp-dir&utm_medium=referral&utm_campaign=plugin-dir&utm_content=wp_optimize&utm_creative_format=description)
is trusted by more than 1 million WordPress website** owners to **boost performance**
and **reduce page load times** to improve your siteÌtumọ̀ Yorùbá: ’s **user experiences**
and **SERP rankings in Google.**

It does this in four clever ways:

**1. It caches your site**

Caching is the process of storing a temporary HTML version of your site on the server
so it can be retrieved more quickly for the user.

ItÌtumọ̀ Yorùbá: ’s a sure-fire way to ensure web pages load at lightning-fast speed.
Turn it on in just one click.

**2. It compresses images**

Large images can really impact page speed load times. WP-Optimize makes it easy 
to identify and compress images to your preferred lossy / lossless settings in a
couple of clicks.

**3. It cleans the database**

Your WordPress database stores everything that you need, plus some things that you
donÌtumọ̀ Yorùbá: ’t. WP-Optimize cleans and optimizes the database to speed up 
your site and save server resources.

**4. It minifies**

On top of its three main features, WP-Optimize Cache also has the more advanced 
minification feature.

Together with caching, minification dramatically improves performance and page speed
load time.

### 1. CACHE YOUR SITE

**Turn on caching in just one click:**

WP-Optimize automatically and optimally configures itself for your WordPress site.
Turn it on in one-click or refine its settings if you prefer.

**More cache features:**

 * **Cache preloading:** This feature emulates a visit to your site, meaning cached
   files are served straight away, speeding up your site from the very first visit.
 * **GZIP Compression:** When the server isnÌtumọ̀ Yorùbá: ’t configured to do so,
   WP-Optimize delivers HTML, CSS and JS files to the userÌtumọ̀ Yorùbá: ’s browser
   as smaller, compressed files, reducing the size of pages and style sheets by 
   up to 90%!
 * **Preload key requests:** Recommended by Google to improve page speed times. 
   Critical resources (things like font files) get loaded first, so the page loads
   much faster **[Premium]**.

**Use cache settings to:**

 * **Serve cached content to logged in users:** Turn this on if content stays the
   same for logged in users (or turn on and exclude URLs where content does change
   e.g. my account areas).
 * **Exclude content from cache:** Exclude by URL, conditional tags, browser agent
   strings or list cookies that should prevent caching when set (advanced user settings).
 * **Deliver device-specific cache:** Serve separate cache files to desktop and 
   mobile devices . This ensures that responsive features e.g. desktop and mobile
   menus are cached separately and served correctly.
 * **User per role cache:** Useful if your website delivers different content to
   different user roles. e.g. an e-commerce site that displays different content
   to resellers or consumers **[Premium]**.
 * **User specific cache:** Serves separate cache files to individual users. Useful
   for websites with personalised content e.g. Learning management systems **[Premium]**.
 * **Cache purging permissions:** Select which user roles are allowed to purge the
   cache e.g. admin only or perhaps a ‘teacher’ role in an LMS setting only **[Premium]**.

### 2. COMPRESS IMAGES

 * **Lossy or lossless compression options:** Choose between maximum space saving,
   best image quality or somewhere in-between.
 * **WebP conversion:** Recommended by Google, WebP can achieve up to 34% smaller
   file sizes compared to JPEG and up to 26% compared to PNG.
 * **Auto-compress:** Check a box and every new image you upload will automatically
   be compressed to your preferred lossy / lossless settings.
 * **Bulk compression:** Compress every existing image on your site with the press
   of a button.
 * **Restore original:** Gone too far? Revert images back to their original in one
   click.
 * **Retain EXIF image data:** Check a box to retain EXIF image data during compression.
 * **Lazy Load:** Webpages load much faster by loading web parts gradually, when
   theyÌtumọ̀ Yorùbá: ’re needed vs simultaneous loading of everything, all at once**[
   Premium]**.
 * **Delete orphaned images:** Identify and delete unused images from your WordPress
   website, saving disk space **[Premium]**.
 * **Delete unused image sizes:** WordPress creates multiple sizes for every uploaded
   image causing the uploads folder to become bloated. Scan for image sizes not 
   in use and remove them to save further disk space **[Premium]**.

### 3. CLEAN AND OPTIMIZE THE DATABASE

Cleans-up database tables, post revisions, auto draft posts, trashed posts, spam,
trashed comments and more. Choose what to optimize or itÌtumọ̀ Yorùbá: ’s one click
to clean out the lot.

 * **Schedule clean-ups:** So you can set and forget. Choose from daily, weekly,
   fortnightly or monthly.
 * **Flexible clean-up schedules:** You may wish to optimize database tables more
   frequently than you remove unapproved comments (for example). Choose the specific
   time and day when tasks should run **[Premium]**.
 * **Retain a set number of weeks’ data during clean-ups:** Just in case you need
   to retrieve something.
 * **Back up before clean-ups:** If you delete something you shouldnÌtumọ̀ Yorùbá:’
   t, restore it in a couple of clicks with UpdraftPlus.
 * **Power tweak Ìtumọ̀ Yorùbá: – Turbo boost for WooCommerce:** Unique to WP-Optimize,
   this power tweak boosts performance by replacing a slow query in WooCommerce 
   with two much more efficient queries. E-commerce sites transacting high numbers
   of orders stand to gain here **[Premium]**.
 * **Power tweak Ìtumọ̀ Yorùbá: – Boost performance by indexing the postmeta table:**
   This unique power tweak works by allowing the WordPress postmeta table to be 
   indexed, improving performance **[Premium]**.

### 4. MINIFY AND COMBINE HTML, CSS AND JAVASCRIPT

 * **Minify in just one click:** Minifies HTML, JavaScript and CSS. Toggle on or
   off or customise each one under ‘settings’.
 * **Customise minification:** Minify only (removing unnecessary code e.g line breaks
   and white spacing) or minify and merge. Apply the same or different settings 
   to HTML, CSS and JavaScript.
 * **Asynchronous loading:** Choose non-critical CSS and JavaScript files to load
   in the background and independently of other resources e.g. analytics or pixel
   scripts. Loading asynchronously eliminates render blocking and improves page 
   speed.
 * **Exclude files from being minified:** Specify CSS and JavaScript files to exclude
   from minification.
 * **Optimize fonts:** Optimize Font Awesome and Google Fonts. Inline the font files,
   inherit from CSS settings or load CSS / Javascript asynchronously instead.
 * **Preload assets:** WP-Optimize visits each web page on your site so the code
   is minified and preloaded for real life users, right from their very first visit.
 * **Preload key requests:** Recommended by Google to improve page speed times. 
   Critical resources (things like font files) get loaded first, so the page loads
   much faster.

### WHY WP-OPTIMIZE?

 * ItÌtumọ̀ Yorùbá: ’s brought to you by [TeamUpdraft](https://www.teamupdraft.com?utm_source=wpo-wp-dir&utm_medium=referral&utm_campaign=plugin-dir&utm_content=teamupdraft&utm_creative_format=description),
   the team behind the worldÌtumọ̀ Yorùbá: ’s most trusted backup, migration and
   restoration plugin.
 * ItÌtumọ̀ Yorùbá: ’s easy to use.
 * It packs a punch for a free plugin.

WP-Optimize brings the best cache and optimization technology together into one 
single, seamless plugin to make your WordPress site fast, lean and efficient.

### PREMIUM FEATURES AT A GLANCE

Our free version of WP-Optimize Cache is great, but we also have an even more powerful
[Premium version](https://www.teamupdraft.com/wp-optimize/pricing?utm_source=wpo-wp-dir&utm_medium=referral&utm_campaign=plugin-dir&utm_content=premium_version&utm_creative_format=description)
with extra features that offer the ultimate in freedom and flexibility:

 * **Multisite Support:** extends database optimisations so they function for multiple
   WordPress sites at a time. If you manage more than one website, you will need
   WP-Optimize Cache Premium.
 * **Flexibility and Control:** gives you the power to optimize select individual
   tables or a particular combination of tables on one or more WordPress websites,
   rather than having to optimize all database tables.
 * **Deleting unused and unwanted images:** removes orphaned images from your WordPress
   site, plus images of a certain, pre-defined size.
 * **Sophisticated Scheduling:** offers a wide range of options for scheduling automatic
   optimization. Specify an exact time and run clean-ups daily, weekly, fortnightly
   or monthly and perform any number of additional once off optimizations.
 * **Seamless Graphical User Interface:** for superb clarity in scheduling and managing
   of multi-site optimizations.
 * **WP-CLI support:** provides a way to manage optimizations from command-line 
   interface if you have lots of sites
 * **Lazy Loading:** load only the images and part of a web-page when it is visible
   to the user so they can see something very quickly.
 * **Optimization Preview:** gives users the ability to preview, select and remove
   data and records available for optimization from the database.
 * **Preload key requests:** preload assets such as web fonts and icon fonts, as
   recommended by Google PageSpeed Insights.
 * **Premium support** Ìtumọ̀ Yorùbá: – caching is one of the most complex things
   you can do for a website, so premium support offers you peace of mind thereÌtumọ̀
   Yorùbá: ’s someone to talk quickly to if you need any technical answers or help
   configuring the optimizations of cache settings for your website.

#### Translations

Translators are welcome to contribute to the plugin. Please use the [WordPress translation website](https://translate.wordpress.org/projects/wp-plugins/wp-optimize).

## Àwọn àwòrán ìbòjú

[⌊Cache - plugins comparison benchmark⌉⌊Cache - plugins comparison benchmark⌉[

Cache Ìtumọ̀ Yorùbá: – plugins comparison benchmark

[⌊Database optimization⌉⌊Database optimization⌉[

Database optimization

[⌊UpdraftPlus running a backup before an optimization proceeds⌉⌊UpdraftPlus running
a backup before an optimization proceeds⌉[

UpdraftPlus running a backup before an optimization proceeds

[⌊Table Report⌉⌊Table Report⌉[

Table Report

[⌊Image compression⌉⌊Image compression⌉[

Image compression

[⌊Main cache screen⌉⌊Main cache screen⌉[

Main cache screen

## Ìgbéwọlẹ̀

There are 3 different ways to install WP-Optimize Cache, as with any other wordpress.
org plugin.

#### Using the WordPress dashboard

 1. Navigate to the ‘Add New’ in the plugins dashboard
 2. Search for ‘WP-Optimize’
 3. Click ‘Install Now’
 4. Activate the plugin on the Plugin dashboard

#### Uploading in WordPress Dashboard

 1. Download the latest version of this plugin from https://wordpress.org/plugins/wp-
    optimize/
 2. Navigate to the ‘Add New’ in the plugins dashboard
 3. Navigate to the ‘Upload’ area
 4. Select the zip file (from step 1.) from your computer
 5. Click ‘Install Now’
 6. Activate the plugin in the Plugin dashboard

#### Using FTP

 1. Download the latest version of this plugin from https://wordpress.org/plugins/wp-
    optimize/
 2. Unzip the zip file, which will extract the wp-optimize directory to your computer
 3. Upload the wp-optimize directory to the /wp-content/plugins/ directory in your 
    web space
 4. Activate the plugin in the Plugin dashboard

## FAQ

### IsnÌtumọ̀ Yorùbá: ’t it better to use a dedicated caching plugin to cache my site?

WeÌtumọ̀ Yorùbá: ’ve built WP-Optimize Cache around the most advanced and powerful
caching technology. Our caching tests and feedback from real-world users show that
the caching feature alone can make your site faster than any other cache plugin 
or optimization. [See these speed test results.](https://ps.w.org/wp-optimize/assets/screenshot-1.png?rev=2125386)

### Is optimizing my database safe?

Yes; optimizing does not involve any “tricks” or poking around in dangerous ways.
It involves running routine clean-up operations using well-defined, common MySQL
commands. **Nevertheless, we always recommend backups**, which cover every possibility;
not just database malfunctions, but hackers, human errors, etc. We recommend [UpdraftPlus](https://wordpress.org/plugins/updraftplus/).

### What savings can I expect to make?

This is a “how long is string?” sort of question. It depends completely on your 
site Ìtumọ̀ Yorùbá: – how big it is, how many users interact on it, how long it 
has been running, and when you last optimised it. However, the savings and speed-
ups can be substantial; it is always worth making sure that your database is optimised.

### How do I get support?

In our support forum, here: https://wordpress.org/support/plugin/wp-optimize/

### WP-Optimize does not make large savings on my database

This is rare; itÌtumọ̀ Yorùbá: ’s probably because youÌtumọ̀ Yorùbá: ’re with a 
shared web hosting company that doesnÌtumọ̀ Yorùbá: ’t allow scripts to run an optimize
command via SQL statements (SQL “OPTIMIZE” instruction). Please consult your web
hosting company on this matter.

### Is the plugin tried and tested?

Yes Ìtumọ̀ Yorùbá: – WP-Optimize Cache is WordPressÌtumọ̀ Yorùbá: ’s #1 most-installed
optimisation plugin, with over 800,000 users and a pedigree going back over 8 years.

### Does WP-Optimize support InnoDB tables?

WP-Optimize will disable some features if it detects InnoDB tables. Optimization
of the database tables on-disk is not available, but other clean up features would
work.

### Can you help me restore my database?

Not unless you have an existing backup. Please ensure that you make a backup of 
your entire database before using WP-Optimize for the first time, and when you upgrade
to a major new version of it. We recommend [UpdraftPlus](https://wordpress.org/plugins/updraftplus/).

### Are there any bugs in this plugin?

The plugin is an ongoing work; that means that it is impossible to rule out unforeseen
situations and bugs. So I would recommend you to test it out on your local system
or make a backup of your database (just to be extra careful).

### How do I stop transient options from coming back automatically each time I clear them?

When WordPress uses a particular transient, that specific transient is re-created
automatically. So, itÌtumọ̀ Yorùbá: ’s normally for ones which are in active use
to gradually re-appear. The best way to keep things optimal is to clear the transient
options on a scheduled basis. For example, WordPress may create 50 transient option
in a week. If you schedule WP-Optimize Cache to clear these options on a weekly 
basis, youÌtumọ̀ Yorùbá: ’ll have far fewer building up.

### The table size shows wrong / Not optimizing

Please check your database for corrupted tables. That can happen, usually your web
hosting company can run the repair command on the db.

### Which WordPress and PHP versions are supported?

To use all features in the plugin, a minimum of version WordPress 4.9 with PHP 7.2
are required. But we do recommend to use the latest version of WordPress. Using 
PHP 7.2+ is also highly recommended, as our caching feature will work even faster.

### Which optimisation will make the biggest difference?

This depends on your setup (theme, number and quality of plugins used, etc…), but
generally, caching will make the biggest visible difference to your websiteÌtumọ̀
Yorùbá: ’s performance. Indeed, the cache functionality bypasses most of WordPress
code to serve your pre-optimised cached pages directly to your visitor, significantly
increasing the speed.

### What is caching, or page caching?

_“Caching”, from Wikipedia:_ “In computing, a cache is a hardware or software component
that stores data so that future requests for that data can be served faster; the
data stored in a cache might be the result of an earlier computation or a copy of
data stored elsewhere. A cache hit occurs when the requested data can be found in
a cache, while a cache miss occurs when it cannot.” — WP-Optimize cache does this
by saving the page computed by WordPress on the disk. When a user visits a page,
WP-Optimize will serve the cached page before WordPress is loaded. If the page wasnÌtumọ̀
Yorùbá: ’t cached before, it will be computed by WordPress, and WP-Optimize will
then save the result to the cache.

### Why should I use a caching plugin on my website?

You think your site is fast without caching? A caching plugin will make your website
even faster. A faster cached website will increase SEO, it will improve your visitors
experience. Caching will also save your serverÌtumọ̀ Yorùbá: ’s resources.

### Is the WP-Optimize page cache compatible with Gutenberg and WordPress 5.0+?

Yes, your Gutenberg pages will be cached, as well as those created with page builder
plugins such as Elementor.

### How do I know my webpage is being cached (or why it isnÌtumọ̀ Yorùbá: ’t)?

If cache is enabled, and in order to see if your page is cached, use the “View Source”
function in your web browser to view the page source. To find caching information,
scroll down to the bottom, and you should see a line added by the cache: `<!-- Cached
by WP Optimize - https://teamupdraft.com/wp-optimize/ - Last modified: Sat, 20 Jul
2019 21:17:19 GMT ->`
 However, note that if you are using a further service that
minifies HTML (e.g. Cloudflare), then this line may have been removed. Another method
is to inspect the contents of the directory wpo-cache inside your wp-content directory.
<a href=”https://teamupdraft.com/documentation/wp-optimize/topics/caching/faqs/how-
do-i-know-my-webpage-is-being-cached/>Further information can be read here Also 
note that if you do not preload the cache, a page or post will have to be visited
once for the cache file to be generated.

### How do I configure the page cache?

Go to WP-Optimize -> Cache and enable caching. For most people, that will be enough.
If you run an e-commerce, have a custom login page or any page that has dynamic 
content, you might want to exclude certain urls from the cache. Visit [documentation](https://www.teamupdraft.com/documentation/wp-optimize?utm_source=wpo-wp-dir&utm_medium=referral&utm_campaign=plugin-dir&utm_content=documentation&utm_creative_format=faqs)
for help.

### Is the caching feature compatible with e-commerce plugins?

Yes, caching with WP-Optimize Cache allows you to safely cache your products, with
plugins like WooCommerce or Easy Digital Downloads, or any e-commerce that uses `
DONOTCACHEPAGE` to exclude sensitive pages from caching (e.g. my account, cart or
checkout pages).

### Is the caching feature compatible with multilingual plugins?

Yes, WP-Optimize works with popular multilingual plugins like WPML or Polylang. 
However, itÌtumọ̀ Yorùbá: ’s important to note that when using WP-Optimize with 
multilingual plugins, the URL format for different languages should not include 
any query parameters, for example `https://example.com/?lang=en`. Instead, it should
be in a pretty permalink format, such as `https://example.com/en`.

### Do I need a special setup to use the caching feature?

No, if WordPress works properly, WP-Optimize will be able to cache your pages and
posts.

### Can I use the page caching feature together with another cache plugin?

No, because both cache plugins would need to use the drop-in plugin `advanced-cache.
php`. If you turn off caching on WP-Optimize Cache, you can use any other caching
plugin and still use the other features of WP-Optimize. But we do recommend using
our caching solution.

### Is WP-Optimize caching compatible with Cloudflare?

Yes! No special cache configuration is needed. Page caching on the WP site (that
done by WP-Optimize Cache) is independent of proxy caching (e.g. Cloudflare) – you
can use both, or neither, and they will complement each other and not interfere.

Just one thing to note – Cloudflare will strip out the special HTML comment at the
bottom of the source of a page that is helpful to confirm that page caching is working,
so, donÌtumọ̀ Yorùbá: ’t be confused by that – itÌtumọ̀ Yorùbá: ’s absence doesnÌtumọ̀
Yorùbá: ’t indicate the cache is not working.

### Can I empty the cache automatically when performing a custom action?

Yes, you can trigger a cache purge action using WP-Optimize Cache public functions.
If you want to clear the whole cache, use the function `wpo_cache_flush()`. If you
want to clear the cache files for a specific page or post, use `WPO_Page_Cache::
delete_single_post_cache($post_id);`. Those cache options are available after WP
action `plugins_loaded`.

### Will the comments work even when page caching is enabled?

Yes, when using WordPress’ commenting system, your users will still be able to post
comments. Every time a comment is approved, the cache for that page or post will
be cleared, allowing the next visitor to see an up to date list of comments.

### What is “cache preloading”?

Usually, a page is cached when a user visits it. So the first user visiting wonÌtumọ̀
Yorùbá: ’t be served a cached version of the page, and will wait longer than the
next users. The cache preloading functionality will go through all your pages and
posts, and simulate a visit by a user, allowing WP-Optimize to cache the pages before
anyone visits them. Your first visitor will thus be served a cached version of the
page, increasing its performance.

### What frequency should I choose for the cache preloading schedule?

Choosing a frequency for the cache preloading schedule will depend on factors such
as the frequency at which the website content is updated, the number of pages in
the cache, the resources of the server and more.
 For example a site with hundreds
of pages will require more resources to preload its cache. So choosing a high frequency
will mean that the cache will be recreated often, and the resource usage will be
higher. On a website where updates arenÌtumọ̀ Yorùbá: ’t as frequent, you can even
disable the cache preloading schedule, or set a high cache lifespan and set the 
cache preloading schedule to follow it.

### How do I cache only the home page?

Add /.+ to the cache option “URLs to exclude from cache” on the advanced settings
tab.

### How do I prevent WP-Optimize Cache from caching a certain page

To prevent a page from being cached, you can add the URL to the field “URLs to exclude
from cache” in the cache “Advanced settings” tab. If you are developing a plugin
and want to prevent a page from being cached, you can define the “DONOTCACHEPAGE”
constant on the pages you need. Any request where “DONOTCACHEPAGE” is defined will
not be cached.

### Is the caching feature of WP-Optimize free?

Yes the caching feature is free. You will always be able to cache your website for
free using WP-Optimize and we are constantly working on improving the existing cache
feature. We will add more caching options to the free version and develop more specific
caching options in the premium version to enable you to taylor the caching functionality
to your needs.

### Where does WP-Optimize Cache store the cached files?

The cached files are stored in the common “wp-content/cache” folder, inside a “wpo-
cache” folder. Removing the “cache” folder will delete all of WP-OptimizeÌtumọ̀ 
Yorùbá: ’s cache, as well as those from other plugins.
 Deleting the “cache” folder
is generally safe, as those cached files will be regenerated.

### How do I disable caching?

Go to WP-Optimize settings > Cache and toggle the “Enable page caching” option to
on/off.

### Will caching slow down my server?

No, caching will actually reduce the load on your server, by reducing the amount
of PHP and mysql used. You might see a peak in resource usage when using the cache
preloader, as this functionality will create the cache files for all your pages 
in a short amount of time. But once this is done, performance should increase and
the load on your server will decrease. Every single major site uses caching to serve
cached pages faster by using fewer resources.

### Can I make certain parts of the page stay dynamic when cache is enabled?

The cached page is sent to the user before most of WordPress was loaded. The plugins
arenÌtumọ̀ Yorùbá: ’t loaded yet, making it impossible for them to change the cached
content at every request.
 So at the moment if you want to keep parts of your page
dynamic (e.g. adverts, widgets, shopping cart…) AND keep it cached, you will have
to use custom solutions using javascript and AJAX to fetch those dynamic parts from
the server.

### How do I delete the WP_CACHE define from wp-config.php?

WP-Optimize Cache will remove the “WP_CACHE” constant from wp-config.php when you
disable page caching, or when you deactivate the cache plugin. If you need to remove
it manually, you can use FTP to edit wp-config.php and delete the line define (‘
WP_CACHE’, true );
 If page caching is still enabled in the settings, WP-Optimize
Cache will attempt to add the line again, as it is required for the caching functionality
to work.

### My filesystem is not writable to increase security. What do I need to do to make it compatible with the caching functionality?

WP-Optimize caching feature needs write access to the ‘wp-content/cache’ folder,
as this is where the cache files will be stored. It also needs to define the constant‘
WP_CACHE’ in ‘wp-config.php’, it will need access once to ‘wp-content/advanced-cache.
php’, as well as to the folder ‘wp-content/wpo-cache’ to write the cache settings.

### How do I change file permissions?

If you need to change file permissions to enable caching, you can follow the instructions
on this page https://wordpress.org/support/article/changing-file-permissions/

### What is the maximum number of pages I can cache?

There is no limit to the number of pages you can cache. The only limit is the space
on your server and the maximum number of subdirectories allowed by your server, 
as caching will write files in subdirectories following the permalink structure.

If you were to reach a caching limit, it probably means that your server is not 
fit for the size of your website and caching needs.

### How do I serve cached pages to people using a phone or tablet?

You can generate a separate cache by selecting “Generate separate files for mobile
devices” in the page cache settings. This cache setting is only necessary if you
use a specific theme for mobile devices, or for certain AMP plugins.

### Does WP-Optimize Cache work with Nginx?

Yes, the cache feature works with Nginx. Should you want to enable browser caching
or GZIP compression, you will have to do this yourself directly on the server settings.

### Does caching work with Windows Server (IIS) ?

Yes, the cache feature works with IIS. As with Nginx, if you need to enable browser
caching or GZIP compression, you will have to do this yourself on the server.

### Does the WP-Optimize page cache work with non-pretty (query parameter-based) permalinks?

No. ItÌtumọ̀ Yorùbá: ’s necessary to have pretty permalinks of the type http://xxxxx.
com/my-post/ rather than http://xxxxx.com/?p=1234 for cache to work. Pretty permalinks
are the WordPress default setting, and there is no good reason to turn them off,
so you should not have a problem with this.
 Note that cache will work with permalinks
including /index.php/. It is only those based upon query parameters (?…) where cache
wonÌtumọ̀ Yorùbá: ’t work.

### When does WP-Optimize clear the page cache?

 * When you publish new content or update/edit existing content, the cache for that
   post/page will be cleared.
 * Changing/updating current themes and parent themes (of child themes) will purge
   the cache.
 * When turning off the cache feature in WP-Optimize

### Will pages in the WP admin dashboard be cached?

No, WP dashboard pages are not cached. The cache functionality is only meant to 
cache frontend pages.

### What is cache lifespan?

The cache lifespan is the time a cached file will be kept before being regenerated.

One of the main reason for setting a lifespan to your cache is that some plugins
and themes use nonces, which are printed in the source code of the page ([Read more about nonces here](https://developer.wordpress.org/plugins/security/nonces/)).
These nonces cannot be reused and are valid for 12 hours by default (developers 
can change that value). The cache plugin will store the nonce in the page, and this
one will become invalid after that perdiod of time, which can affect certain functionalities
of your plugins and themes. Setting a cache lifespan to under 10 hours ensures the
cache is flushed automatically before the nonce expires. This way you can use WP-
OptimizeÌtumọ̀ Yorùbá: ’s cache feature on sites which use nonces. An other reason
is that you may want your pages to reflect some changes without having to clear 
the whole cache. Indeed if you have many pages and posts, you might not want to 
clear every cache file with every change, but rather set an interval at which they
will expire and be regenerated.

### What value should the cache lifespan be?

A lower cache lifespan value will result in more frequent cache update activity 
on your server, and thus more preload processes, if activated.
 If your site does
not use nonces, and your siteÌtumọ̀ Yorùbá: ’s cache doesnÌtumọ̀ Yorùbá: ’t need
to be updated often, you can set the cache lifespan to a high value or to 0 to give
it an infinite lifespan. The cache lifespan option is set to 10 hours by default,
but you may go down to 8 or even less. If you notice any issues due to high server
load, set a higher interval for the preloader.

### Can WP-Optimize Cache minify JavaScript, CSS and HTML?

Yes, the newly added Minify enables you to minify JavaScript and CSS. It also enables
you to minify HTML.

### Why minify my WordPress site?

WP-Optimize CacheÌtumọ̀ Yorùbá: ’s Minify feature is all about increasing the speed
of your WordPress site for your users.
 One way Minify does this is by reducing 
the size of your HTML, CSS and JavaScript files by removing unnecessary spaces and
lines from the files and shortening long names internally within the code. Another
way is that your files are merged into as few files as possible. This reduces the
amount of load on your web server and can be quicker to load fewer files. You can
also defer the loading of any CSS or JavaScript file. This means any large or extraneous
CSS or JavaScript file can be loaded independently from the core of your WordPress
site; giving your users quicker access to your site.

### What does “Reset the minified files” actually do?

Pressing the “Reset the minified files” does:
 * delete the temporary files used
when generating the minified assets * delete old minified files (more than 30 days
old) * add a folder for the new minified files, which will be generated when visiting
a page The previously minified CSS files will remain on the server until they expire,
or until theyÌtumọ̀ Yorùbá: ’re deleted using the button “Delete all the files generated
by minify”.

### Can I defer CSS and JavaScript using WP-Optimize Cache?

Yes, the newly added minification feature (a.k.a. Minify) allows you to defer parsing
of JavaScript and CSS.

### GoogleÌtumọ̀ Yorùbá: ’s PageSpeed Insights says to leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Can WP-Optimize Cache do that?

Leveraging the font-display CSS feature is currently possible when using Google 
Fonts. The default parameter is “swap”, but can be changed using the WordPress filter“
wpo_minify_gfont_display_type”.

### When enabling minify, my siteÌtumọ̀ Yorùbá: ’s layout is broken. How can I fix it?

This usually means one or more of your CSS files are incompatible with the minification
or merging process. It can also be caused by errors in the CSSÌtumọ̀ Yorùbá: ’s 
syntax.
 You can check the CSSÌtumọ̀ Yorùbá: ’s syntax by using an online CSS syntax
checker such as csslint.net. If your syntax is not causing the issue, or you cannot
change the file with an issue, you can either exclude the problematic CSS files 
from the minification and merging process. To exclude individual CSS files from 
the minification and merging process, you can go to WP-Optimize > Minify > CSS and
go to the “Exclude the following CSS files from processing” section.

### When enabling minify, some functionality is broken. How can I fix it?

This usually means one or more of your JavaScript files are incompatible with the
minification or merging process. It can also be caused by errors in the JavaScriptÌtumọ̀
Yorùbá: ’s syntax.
 The first thing to try is to enable the setting “Contain each
included file in its own block” in the JavaScript options (WP-Optimize > Minify 
> Javascript > JavaScript options). This could “catch” an error, and prevent the
rest of the code to be broken. If the first option didnÌtumọ̀ Yorùbá: ’t work, try
disabling merging of JavaScript files. If none of the above works, disable processing
of JavaScript files in the minify settings, and [open a support thread](https://wordpress.org/support/plugin/wp-optimize)
with details about your issue. WeÌtumọ̀ Yorùbá: ’ll do our best to help you troubleshoot
the issue.

## Àwọn àgbéyẹ̀wò

![](https://secure.gravatar.com/avatar/303518c80f6f6085242214a06a4fadfee403716e4606b4e220c8af7fdb0fd594?
s=60&d=retro&r=g)

### 󠀁[Full of helpful features but not too complicated to use](https://wordpress.org/support/topic/full-of-helpful-features-but-not-too-complicated-to-use/)󠁿

 [hommealone](https://profiles.wordpress.org/hommealone/) Ọwẹ́wẹ̀ 4, 2026

With a little fine-tuning, itÌtumọ̀ Yorùbá: ’s not too hard to get a lean clean 
site that loads nearly instantly.

![](https://secure.gravatar.com/avatar/12f46cc3f57dac035b6c0eecffd2c620b9e115deaf9278bbdfe321ba978962e0?
s=60&d=retro&r=g)

### 󠀁[WPO image caching plugin](https://wordpress.org/support/topic/wpo-image-caching-plugin/)󠁿

 [prosat](https://profiles.wordpress.org/prosat/) Ọwẹ́wẹ̀ 1, 2026

Works really well on images, optimizing them, making the site loading faster. Would
recommend it. Will buy the PRO version eventually.

![](https://secure.gravatar.com/avatar/e65aedd3966adb762eb36d95725bb344d0912fdbcc87e2738c8dcee6a14bed0d?
s=60&d=retro&r=g)

### 󠀁[The best Cache and optimization Plugin](https://wordpress.org/support/topic/the-best-cache-and-optimization-plugin-2/)󠁿

 [Mohamed Mahfouz Mostafa Ibrahim](https://profiles.wordpress.org/mohamedmm1975/)
Ògún 25, 2026

It really enhanced my Performance on Page Speed Insights

![](https://secure.gravatar.com/avatar/55e12969b0ced6eea0d257c699ddca8e3cffeaf1005651adb078a5b20939a235?
s=60&d=retro&r=g)

### 󠀁[ItÌtumọ̀ Yorùbá: ’s a must!](https://wordpress.org/support/topic/its-a-must-18/)󠁿

 [Prolet](https://profiles.wordpress.org/prolet/) Ògún 24, 2026

Thank you for creating this plugin!ItÌtumọ̀ Yorùbá: ’s a must! It does the job as
it says, and itÌtumọ̀ Yorùbá: ’s easy to use.

![](https://secure.gravatar.com/avatar/3b3e1bc6762d1bb6645960ac9b3a1cd07097b3684af0217d035fd0e76a8e7048?
s=60&d=retro&r=g)

### 󠀁[nice work](https://wordpress.org/support/topic/nice-work-605/)󠁿

 [khoobnet99](https://profiles.wordpress.org/khoobnet99/) Ògún 16, 2026

doing a great job

![](https://secure.gravatar.com/avatar/74595097c786af7fae76399199abf85ea7aa201f567883b4937de64ae1f878a3?
s=60&d=retro&r=g)

### 󠀁[Works well](https://wordpress.org/support/topic/works-well-3190/)󠁿

 [studiovene](https://profiles.wordpress.org/studiovene/) Ògún 14, 2026

The plugin does what I need Ìtumọ̀ Yorùbá: – easy.

 [ Ka gbogbo àwọn àgbéyẹ̀wò 2,608 ](https://wordpress.org/support/plugin/wp-optimize/reviews/)

## Àwọn Olùkópa & Olùgbéejáde

“WP-Optimize – Cache, Compress images, Minify & Clean database to boost page speed&
performance” jẹ́ ètò ìṣàmúlò orísun ṣíṣí sílẹ̀. Àwọn ènìyàn wọ̀nyí ti ṣe ìkópa sí
plugin yìí.

Àwọn Olùkópa

 *   [ David Anderson / Team Updraft ](https://profiles.wordpress.org/davidanderson/)
 *   [ ruhanirabin ](https://profiles.wordpress.org/ruhanirabin/)
 *   [ DNutbourne ](https://profiles.wordpress.org/dnutbourne/)
 *   [ aporter ](https://profiles.wordpress.org/aporter/)
 *   [ snightingale ](https://profiles.wordpress.org/snightingale/)
 *   [ LumberHack ](https://profiles.wordpress.org/lumberhack/)
 *   [ Venkat Raj ](https://profiles.wordpress.org/webulous/)

A ti túmọ̀ “WP-Optimize – Cache, Compress images, Minify & Clean database to boost
page speed & performance” sí àwọn èdè agbègbè 33. Ọpẹ́lọpẹ́ fún [àwọn atúmọ̀ èdè](https://translate.wordpress.org/projects/wp-plugins/wp-optimize/contributors)
fún àwọn ìkópa wọn.

[Túmọ̀ “WP-Optimize – Cache, Compress images, Minify & Clean database to boost page speed & performance” sí èdè rẹ.](https://translate.wordpress.org/projects/wp-plugins/wp-optimize)

### Ṣe o nífẹ̀ẹ́ sí ìdàgbàsókè?

[Ṣàwárí koodu](https://plugins.trac.wordpress.org/browser/wp-optimize/), ṣàyẹ̀wò
[ibi ìpamọ́ SVN](https://plugins.svn.wordpress.org/wp-optimize/), tàbí ṣe àgbékalẹ̀
sí [àkọsílẹ̀ ìdàgbàsókè](https://plugins.trac.wordpress.org/log/wp-optimize/) nípasẹ̀
[RSS](https://plugins.trac.wordpress.org/log/wp-optimize/?limit=100&mode=stop_on_copy&format=rss).

## Àkọsílẹ̀ àwọn àyípadà

#### 4.6.1 Ìtumọ̀ Yorùbá: – 29/Jul/2026

 * 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
 * REFACTOR: WPO_KD_Submissions_Compatibility class
 * REFACTOR: WP_Optimize_Server_Compatibility class
 * REFACTOR: WPO_Polylang_Compatibility class
 * TWEAK: Clear cached local Google Fonts statistics when the CSS font file is downloaded
 * TWEAK: Create a new class named WP_Optimize_UpdraftCentral_Commands to group 
   UpdraftCentral specific commands, currently including methods for retrieving 
   and updating WP-Optimize settings
 * TWEAK: Removed deprecated UpdraftCentral commands from WP_Optimize_Commands class
 * TWEAK: Removed unused phpseclib dependency from composer
 * TWEAK: Smush post meta keys are prefixed with `_` and now is multisite compatible

#### 4.6.0 Ìtumọ̀ Yorùbá: – 06/Jul/2026

 * FEATURE: Premium Ìtumọ̀ Yorùbá: – Automatically preloads the page’s Largest Contentful
   Paint (LCP) element to improve initial load speed and perceived performance
 * FIX: Cache Ìtumọ̀ Yorùbá: – 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()
 * REFACTOR: Fix WordPress Security check errors and warnings on admin page
 * REFACTOR: Make `is_edit_mode` a static method and avoid duplication
 * REFACTOR: Optimized WP_Optimize_Database_Information::get_table_plugin() method
 * TWEAK: Added method to check current user has the capability
 * TWEAK: Added methods to retrieve and save essential WP-Optimize toggleable settings
   for UpdraftCentral
 * TWEAK: Disable and hide the “Speed up WooCommerce ‘Get total spent’ query” Power
   Tweak when itÌtumọ̀ Yorùbá: ’s no longer relevant
 * TWEAK: Handle race conditions in font downloading and optimize cache stats storage
 * TWEAK: Improved image grid action button visibility to accommodate WordPress 
   7.0 button styling changes
 * TWEAK: Matched response styles when purging via the admin bar
 * TWEAK: Premium Ìtumọ̀ Yorùbá: – Handle empty orders in WooCommerce Total Spent
   Power Tweak feature
 * TWEAK: Premium Ìtumọ̀ Yorùbá: – Improved hash logic for the Unused CSS Removal
   feature
 * TWEAK: Prevent unwanted cache growth caused by crawlers or preload bots
 * TWEAK: UI changes to match WordPress 7.0
 * TWEAK: Unschedule all WP-Optimize cron jobs on deactivation in multisite
 * TWEAK: WP_Optimize_Power_Tweaks class method deactivate bug fixed related to 
   the array_diff function

#### 4.5.5 Ìtumọ̀ Yorùbá: – 05/Jun/2026

 * TWEAK: Update the bundled common-libs version

#### 4.5.4 Ìtumọ̀ Yorùbá: – 25/May/2026

 * FIX: WebP image compression breaking in some cases
 * REFACTOR: Avoid instantiating PHPSQLParser on each call in WPO_DB_Table_Analysis
 * REFACTOR: Class WPO_WebP_Convert
 * REFACTOR: Make markup readable in `tables-body.php` template
 * REFACTOR: Refactored duplicated cache_admin_bar logic by centralizing it in the
   admin class and removing redundant implementations.
 * REFACTOR: Removed unused `WPO_Htaccess_Capabilities` class
 * REFACTOR: WPO_Activation class
 * REFACTOR: WPO_Uninstall class
 * REFACTOR: WPO_WebP_Alter_HTML class
 * REFACTOR: WPO_WebP_Self_Test class
 * REFACTOR: WPO_WebP_Test_Run class
 * REFACTOR: WPO_WebP_Utils class
 * REFACTOR: WPO_Webp_Task_Manager class
 * REFACTOR: WP_Optimize_WebP class
 * REFACTOR: WP_Optimize_WebP_Images class
 * TWEAK: Added an additional check to prevent SplFileInfo::getSize() RuntimeException
   in WP_Optimize_Utils::get_folder_stats()
 * TWEAK: All in One SEO plugin compatibility issue
 * TWEAK: Cache Ìtumọ̀ Yorùbá: – Inconsistent REST cache filenames due to query 
   parameter order
 * TWEAK: Cache Ìtumọ̀ Yorùbá: – Set the purge old cache cron schedule based on 
   the Cache lifespan setting
 * TWEAK: Ensure parsed result is an array in WPO_DB_Table_Analysis::get_query_table()
 * TWEAK: Exclude GIF from being converted to WebP with `wpo_webp_convert_compressed_images`
   cron job
 * TWEAK: Optimized `wpo_username_from_cookies()` to avoid repeated database queries
   per request
 * TWEAK: Precheck for existing WebP format of file before running WebP conversion
 * TWEAK: Remove redundant code that is not reachable.
 * TWEAK: Resolved edge cases in CapoJS

#### 4.5.3 Ìtumọ̀ Yorùbá: – 29/Apr/2026

 * SECURITY: Prevented path traversal security risk. Thanks to Wordfence for the
   responsible disclosure

#### 4.5.2 Ìtumọ̀ Yorùbá: – 20/Apr/2026

 * FIX: Bug preg_match() fails on wildcard * patterns in browser agents exclusion
   list
 * FIX: Cache Ìtumọ̀ Yorùbá: – purge the cache when a plugin is auto-updated
 * FIX: Ensure page caching is fully disabled by updating internal cache configuration
   to prevent constant-related errors in logs
 * FIX: Premium Ìtumọ̀ Yorùbá: – Unused images Ìtumọ̀ Yorùbá: – Fixed an issue where
   multiple unused images were displayed for an edited image on setups where images
   are not stored in /yyyy/mm folders
 * FIX: Minify Ìtumọ̀ Yorùbá: – The cron job to purge old cache files is not created
 * REFACTOR: Instead of nested output buffering, code make use of single buffer 
   using Page Optimizer class
 * REFACTOR: Refactor Updraft_Smush_Manager::update_smush_options() method
 * REFACTOR: Using ABSPATH to prevent direct access instead of plugin constants 
   to comply with PCP
 * TWEAK: Added a safety check to remove scheduled table optimization cron jobs 
   when the server does not allow table optimization
 * TWEAK: Enhanced database table detection by marking the KD Submissions database
   table as used by Elementor Pro
 * TWEAK: Fixed a UI issue with WebP conversion in the Media Library
 * TWEAK: Handle WP_Error in WPO_Page_Cache::enable() callers
 * TWEAK: Initialize Heartbeat only on admin pages
 * TWEAK: Premium Ìtumọ̀ Yorùbá: – Preload only selected URLs in the “Cache Specific
   URLs Only” setting
 * TWEAK: Premium Ìtumọ̀ Yorùbá: – Smush Ìtumọ̀ Yorùbá: – Improved PHP 8.5 compatibility
   by replacing deprecated $http_response_header usage
 * TWEAK: Updated user agent for the cache preloader

#### 4.5.1 Ìtumọ̀ Yorùbá: – 23/Mar/2026

 * FIX: Fixed compatibility issue with WP Remote
 * FIX: Notice: Function _load_textdomain_just_in_time was called incorrectly
 * FIX: Resolved weekly cron not running on WordPress < 5.4 by switching to the 
   wpo_weekly schedule
 * FIX: Database table error when upgrading from free to premium version
 * REFACTOR: Improved WebP conversion flow by separating capability checks from 
   configuration changes
 * REFACTOR: Improved auto-optimization handling by correcting static method usage
 * REFACTOR: Introduced `WP_Optimize_Server_Compatibility` class to centralize all
   server environment checks
 * REFACTOR: Removed separate `get_schedule_types()` method in premium version
 * SECURITY: Enforced capability checks and allowed-command validation for Smush
   actions triggered via Heartbeat API. Thanks to WordFence for the responsible 
   disclosure
 * TWEAK: Display the `Enable the caching menu in the admin bar` option only when
   Cache or Minify is enabled
 * TWEAK: Improved detection of LearnDash plugin tables
 * TWEAK: Improved onboarding wizard RTL support and eliminated dependency on the
   PHP Reflection class
 * TWEAK: Improved robustness of `uploads/wpo` directory removal during plugin uninstallation
 * TWEAK: Minify Ìtumọ̀ Yorùbá: – DonÌtumọ̀ Yorùbá: ’t remove the version query 
   argument when the source is not processed by Minify
 * TWEAK: Premium Ìtumọ̀ Yorùbá: – Unused Images Ìtumọ̀ Yorùbá: – Enhanced detection
   of edited WordPress images
 * TWEAK: Prevent deprecation notices in PHP 8.5
 * TWEAK: Add a notice when `.htaccess` file is not available or renamed in Apache
   servers

#### 4.5.0 Ìtumọ̀ Yorùbá: – 11/Feb/2026

 * FEATURE: Premium Ìtumọ̀ Yorùbá: – Cache – Added ability to cache only selected
   URLs
 * FEATURE: Premium Ìtumọ̀ Yorùbá: – Minify Ìtumọ̀ Yorùbá: – Host Google Fonts locally
 * FEATURE: Premium Ìtumọ̀ Yorùbá: – Option to enhance page performance by applying
   Capo.js rules
 * FIX: Cache Ìtumọ̀ Yorùbá: – fixed sitemap caching issue
 * FIX: Improved compatibility with WordPress versions earlier than 6.1
 * FIX: Reset WebP conversion failure no longer appears in the popup
 * FIX: Resolved issues with detecting WebP conversion availability
 * FIX: Smush – Fixed missing tooltip in the ‘Compress’ pop-up in Media Library
 * FIX: Stop initialization of page optimizer for non-HTML requests
 * FIX: Remove marcusschwarz/lessc lib from autoload
 * TWEAK: Added support for bypassing WPO features via a URL query parameter defined
   by the WPO_DISABLE_MODE_URL_PARAM constant
 * TWEAK: Allow some database records cleanup for Kinsta users
 * TWEAK: Clear cache of archived pages when a related post is updated
 * TWEAK: Disabled CSS/JS merging by default.
 * TWEAK: Enhanced 404 detector compatibility with plain permalinks
 * TWEAK: WP_Optimize_Options::auto_option_settings() is not called in Premium version
 * TWEAK: Improved timestamp handling to prevent fatal errors on WordPress 4.9
 * TWEAK: Improved Minify settings UI so JavaScript options correctly show/hide 
   when JS minification is enabled/disabled

#### 4.4.1 Ìtumọ̀ Yorùbá: – 08/Jan/2026

 * FIX: Onboarding wizard RTL issue
 * FIX: Prevented plugin table JSON data in the uploads directory from being updated
   on every WP-Optimize admin page load

#### 4.4.0 Ìtumọ̀ Yorùbá: – 12/Dec/2025

 * FEATURE: Added Onboarding Wizard
 * FIX: Ensured old cache purging cron job is scheduled successfully
 * FIX: Fixed a potential fatal error in the WPO_Page_Optimizer class
 * TWEAK: Fixed the ability to disable caching menu in admin bar
 * TWEAK: Updated file permissions for wpo-plugins-tables-list.json

#### 4.3.1 Ìtumọ̀ Yorùbá: – 14/Nov/2025

 * FIX: Prevent PHP fatal error occurring when cache is enabled and the “Aelia Currency
   Switcher for WooCommerce” plugin is active
 * FIX: Cache – Fixed compatibility issue
 * FIX: Database Ìtumọ̀ Yorùbá: – Table Usage Ìtumọ̀ Yorùbá: – Fixed the issue with
   incorrect table name detection in certain cases
 * FIX: Fixed UI Issue Ìtumọ̀ Yorùbá: – Content cut off in “Review Actions” modal
   under WP-Optimize > Database
 * FIX: Fixed _load_textdomain_just_in_time trigger too early
 * FIX: Premium Ìtumọ̀ Yorùbá: – Unused images Ìtumọ̀ Yorùbá: – Fixed an issue with
   clearing the cache of unused images
 * FIX: Smush Ìtumọ̀ Yorùbá: – Compressing an image larger than the reSmush.it service
   limit freezes the popup in the Media Library
 * FIX: Smush Ìtumọ̀ Yorùbá: – Fixed issue with multiple images compression action
 * FIX: Undefined property: stdClass::$plugin_status bug fixed
 * REFACTOR: Database Ìtumọ̀ Yorùbá: – Table Usage Ìtumọ̀ Yorùbá: – enhanced variable
   names
 * REFACTOR: Using strict comparison throughout the codebase
 * TWEAK: Improve detection of cloudflare handling browser cache
 * TWEAK: Added validation for AJAX commands in the Premium version
 * TWEAK: Convert already compressed images to webp format when possible
 * TWEAK: Fix the compatibility issue with ALTCHA when using the ASE Pro Plugin
 * TWEAK: Improve browser caching by adding max-age option
 * TWEAK: Premium Ìtumọ̀ Yorùbá: – Cache Ìtumọ̀ Yorùbá: – Do not process the cache
   when the user cannot be identified
 * TWEAK: Premium Ìtumọ̀ Yorùbá: – Database Ìtumọ̀ Yorùbá: – Tables usage report
   shows data only for active plugins
 * TWEAK: Premium Ìtumọ̀ Yorùbá: – Unused Images Ìtumọ̀ Yorùbá: – Enhanced detection
   for Revolution Slider
 * TWEAK: Premium Ìtumọ̀ Yorùbá: – Unused Images Ìtumọ̀ Yorùbá: – Improved detection
   of unused images in Oxygen Builder
 * TWEAK: Premium Ìtumọ̀ Yorùbá: – Unused Images Ìtumọ̀ Yorùbá: – Recognize Oxygen
   6 images
 * TWEAK: Premium Ìtumọ̀ Yorùbá: – Prevent PHP warnings from Table Usage feature
 * TWEAK: Remove unused jQuery 1.12.4 dependency
 * TWEAK: Run database table optimization last
 * TWEAK: Updated links
 * TWEAK: Various tweaks and improvements to code

#### 4.3.0 Ìtumọ̀ Yorùbá: – 22/Sep/2025

 * FEATURE: Premium Ìtumọ̀ Yorùbá: – Cache Ìtumọ̀ Yorùbá: – Cache REST API requests
 * FEATURE: Premium Ìtumọ̀ Yorùbá: – Further reduce CSS files sizes by removing 
   unused CSS rules
 * FIX: Added backward compatibility for timezone and datetime functions and improved
   status report support for older WordPress versions like 4.9.
 * FIX: PHP Warning file_exists(): open_basedir restriction in effect
 * FIX: Prevented buffer initialization during wp-cron when HTML DOM is unavailable.
 * REFACTOR: Database Ìtumọ̀ Yorùbá: – Table Usage Ìtumọ̀ Yorùbá: – Refactored execute_query_analysis()
   function
 * TWEAK: Added new UpdraftCentral endpoints
 * TWEAK: Enhanced multisite support: added performance widget to Network Dashboard
   and fixed sub-site widgets to show only site-specific 404 request counts.
 * TWEAK: Fix external loading of Gtag analytics script
 * TWEAK: Moved the tooltip tag outside the tag
 * TWEAK: Performance Ìtumọ̀ Yorùbá: – 404 Detector (Not Found Requests) added a
   button to clear all logs.
 * TWEAK: Publishing a post or custom post type (CPT) no longer clears the cache
   of all posts of the same type.
 * TWEAK: Removed return statements from constructors and added checks at the point
   of class instantiation.
 * TWEAK: Smush Ìtumọ̀ Yorùbá: – Enhanced compatibility and performance with EWWW
   Image Optimizer installed
 * TWEAK: Premium Ìtumọ̀ Yorùbá: – Added cache support for Nelio A/B Testing plugin
 * TWEAK: Added a hook to trigger custom code when a page is not cached

#### 4.2.4 Ìtumọ̀ Yorùbá: – 30/Jul/2025

 * FIX: Potential PHP fatal error when no site is selected during database optimization
   in multisite
 * FIX: Issue where the database optimization spinner remained indefinitely active
 * FIX: PHP 8.4 compatibility warnings
 * FIX: Minify default exclusions fatal error
 * FIX: Premium Ìtumọ̀ Yorùbá: – Potential PHP fatal error Ìtumọ̀ Yorùbá: – type
   hinting error in the database table usage feature
 * FIX: Premium Ìtumọ̀ Yorùbá: – Page cache and lazy load meta boxes no longer display
   on post edit screen when their respective options are disabled
 * FIX: Only purge relevant files when a published post is saved; also purge the
   author archive cache upon post save
 * FIX: Premium Ìtumọ̀ Yorùbá: – Fixed compatibility of Table usage with WordPress
   versions earlier than 5.3
 * REFACTOR: Premium Ìtumọ̀ Yorùbá: – Database Ìtumọ̀ Yorùbá: – Table Usage Ìtumọ̀
   Yorùbá: – added missed translation functions
 * TWEAK: Purged content will preload only when cache is enabled, and the user-agent
   has been updated to a modern browser and OS version
 * TWEAK: Update seasonal advert banner logos, texts and links
 * TWEAK: Update plugin readme text and links
 * TWEAK: Premium Ìtumọ̀ Yorùbá: – Cache Ìtumọ̀ Yorùbá: – Add UI element to ignore
   query variables
 * TWEAK: Premium Ìtumọ̀ Yorùbá: – Database Ìtumọ̀ Yorùbá: – Table Usage Ìtumọ̀ 
   Yorùbá: – replaced loading state with native modal
 * TWEAK: Removed seasonal discount ads except Black Friday

#### 4.2.3 Ìtumọ̀ Yorùbá: – 15/Jul/2025

 * FIX: Cache Ìtumọ̀ Yorùbá: – Resolved PHP warning caused by excessively long cache
   file names
 * FIX: Corrected typo from `meta data` to `metadata`
 * FIX: Cron reschedule event error for hook `wpo_prune_404_log` when `is_minimum_requirement_met`
   is `false`
 * FIX: Premium Ìtumọ̀ Yorùbá: – Fixed a rare PHP warning that could occur when 
   saving a post
 * FIX: Unused image Ìtumọ̀ Yorùbá: – incorrect image filtering in multisite
 * FIX: WP Remote sync conflict caused in v4.2.1 and v4.2.2 By replacing wp_salt
   with core PHP functions
 * FIX: YouTube lazy-load – Thumbnail image now falls back to JPG if browser doesnÌtumọ̀
   Yorùbá: ’t support WebP
 * FIX: WebP images were not being served in Firefox on certain environments
 * TWEAK: 404 detector logs URLs on mobile screens goes out of viewport fixed.
 * TWEAK: CSS Improvements, better font size handling, remove duplication, and SASS
   instead of import
 * TWEAK: Delay YouTube preview image cache purging
 * TWEAK: Display notice when server does not allow database optimizations
 * TWEAK: Enhanced database optimization compatibility with jQuery 4
 * TWEAK: Fixed incorrect transients count in database optimizations UI
 * TWEAK: Improved sanitization of incoming data in `Updraft_Smush_Manager_Commands`
 * TWEAK: Minify Ìtumọ̀ Yorùbá: – Improved compatibility with Divi themeÌtumọ̀ Yorùbá:’
   s dynamically generated assets
 * TWEAK: Multisite corrected site count in database optimizations UI.
 * TWEAK: Preserve EXIF data is set to false by default in all places at codebase
   level.
 * TWEAK: Update URLs of links and images to point to https://teamupdraft.com

#### 4.2.2 Ìtumọ̀ Yorùbá: – 02/June/2025

 * FIX: Cache Ìtumọ̀ Yorùbá: – Resolved unwanted output in WP-CLI and fatal error
   related to WooCommerceÌtumọ̀ Yorùbá: ’s country-specific files, introduced in
   v4.2.0
 * TWEAK: Premium Ìtumọ̀ Yorùbá: – Cache Ìtumọ̀ Yorùbá: – Compatibility with WordPress
   6.8

#### 4.2.1 Ìtumọ̀ Yorùbá: – 05/May/2025

 * FIX: Cache Ìtumọ̀ Yorùbá: – Compatibility issue with other plugins due to late
   start of output buffering
 * TWEAK: Improved array handling in `get_active_plugins()`, potentially avoiding
   edge-case fatal error

#### 4.2.0 Ìtumọ̀ Yorùbá: – 01/May/2025

 * SECURITY: On multisite installs (only), a logged-in site administrator could 
   use an unsanitised parameter to inject unwanted content into SQL queries. Thanks
   to Marc Montpas for the responsible disclosure.
 * FEATURE: Premium Ìtumọ̀ Yorùbá: – Replace YouTube Iframes with preview images
   to improve page speed
 * FIX: Fix conflict with the WPML plugin
 * FIX: Smush Ìtumọ̀ Yorùbá: – Fixed PHP warning on the Media Library page
 * FIX: Smush Ìtumọ̀ Yorùbá: – Fixed issue where the Smush popup would freeze
 * FIX: WebP images not served after WP-Optimize reactivation
 * REFACTOR: Smush option removed from media upload modal
 * TWEAK: Update advert banner logos, texts and links
 * TWEAK: Add missing separator between compression items in media library
 * TWEAK: Avoid PHP warning thrown by Page Speed Ninja plugin
 * TWEAK: Cache Ìtumọ̀ Yorùbá: – Start caching after plugins loaded
 * TWEAK: Fix PHP deprecation warning in PHPSQLParser for PHP 8.4
 * TWEAK: Fix deprecation warning in Updraft_Logger class for PHP 8.4
 * TWEAK: Fixes absence of checkbox to remove all transients
 * TWEAK: Premium Ìtumọ̀ Yorùbá: – Support and feedback links in Help tab now point
   to getwpo.com

#### 4.1.1 Ìtumọ̀ Yorùbá: – 05/Mar/2025

 * FIX: Page builders not working with Delay JS option enabled

#### 4.1.0 Ìtumọ̀ Yorùbá: – 03/Mar/2025

 * FEATURE: Premium Ìtumọ̀ Yorùbá: – Improve performance by caching Gravatar images
   locally.
 * FIX: Premium Ìtumọ̀ Yorùbá: – Unused images Ìtumọ̀ Yorùbá: – Fixed warnings when
   moving non existing image to trash

#### 4.0.1 Ìtumọ̀ Yorùbá: – 17/Feb/2025

 * FIX: File system usage issue

#### 4.0.0 Ìtumọ̀ Yorùbá: – 10/Feb/2025

 * FEATURE: Delay JavaScript execution
 * FIX: Cache Ìtumọ̀ Yorùbá: – Fixed PHP warning “Cannot modify header information”
 * FIX: Minify Ìtumọ̀ Yorùbá: – Unusual behavior occurs when the “Disable Google
   Fonts processing” option is enabled
 * FIX: Smush Ìtumọ̀ Yorùbá: – Fixed image compression actions in Media Library
 * REFACTOR: Replacing jQuery Tablesorter with ‘sortable-tablesort’ package
 * TWEAK: Cache Ìtumọ̀ Yorùbá: – Enhance ActivityPub compatibility
 * TWEAK: Fix PHP notice caused by subscriben plugin advert
 * TWEAK: Minimum requirements were updated to PHP version 7.2 and WordPress version
   4.9
 * TWEAK: Remove uses of `unserialize` without restriction of allowed_classes
 * TWEAK: Recognise Independent Analytics Pro plugin tables in database optimization

#### 3.8.0 Ìtumọ̀ Yorùbá: – 09/Dec/2024

 * FEATURE: Added a system status page
 * FEATURE: Logs frequent and highly recurrent 404 requests; introduces a new Performance
   tab.
 * FIX: Cache Ìtumọ̀ Yorùbá: – Legacy Widgets visibility issue with WP-Optimize 
   Cache enabled
 * FIX: Cache Ìtumọ̀ Yorùbá: – UI issue: Preload “Cancel” option is gone after reloading
   the WPO settings page instantly
 * FIX: Database Ìtumọ̀ Yorùbá: – optimizing any item also changes the status of
   other items
 * REFACTOR: Minify Ìtumọ̀ Yorùbá: – Removal of the WPO_MINIFY_PHP_VERSION_MET constant
 * TWEAK: Add a warning message before deleting post metadata or orphaned relationship
   data.
 * TWEAK: Bailout early if the minimum PHP version is not met
 * TWEAK: Introduced logging for cache purge operations, available under `uploads/
   wpo/logs/cache-*.log`
 * TWEAK: Open CRON overdue guide in new tab
 * TWEAK: Persist Analytics Tab when minification is disabled
 * TWEAK: Premium Ìtumọ̀ Yorùbá: – Unused Images Ìtumọ̀ Yorùbá: – Improved detection
   of images not present in the Media Library, marking them as used
 * TWEAK: UI improvements in Analytics section
 * TWEAK: Wrapped checkboxes inside `label` tags in the confirmation popup that 
   appears when clicking the “Remove” button on the Database > Tables tab.

#### 3.7.1 Ìtumọ̀ Yorùbá: – 20/Nov/2024

 * TWEAK: Resolved a PHP notice caused by translation loading too early when caching
   is enabled, introduced in WordPress 6.7

#### 3.7.0 Ìtumọ̀ Yorùbá: – 21/Oct/2024

 * FEATURE: Added an option to automatically preload URLs immediately after cache
   content is purged
 * FEATURE: Premium Ìtumọ̀ Yorùbá: – Gather data about table usage by filtering `
   query` event
 * FIX: Cache Ìtumọ̀ Yorùbá: – Scheduled preloading wasnÌtumọ̀ Yorùbá: ’t working
 * FIX: Inconsistency in `smush_manager_send_command` function
 * REFACTOR: Smush Ìtumọ̀ Yorùbá: – Popup styles, remove unused code
 * TWEAK: Fix fatal implode error when updating to v3.5.0
 * TWEAK: Image compression Ìtumọ̀ Yorùbá: – Issue with cancelling smush image compression
 * TWEAK: Improve module minification logic
 * TWEAK: Premium Ìtumọ̀ Yorùbá: – Unused images Ìtumọ̀ Yorùbá: – Fixed popup when
   moving images to or restoring images from the trash
 * TWEAK: Premium Ìtumọ̀ Yorùbá: – Unused images Ìtumọ̀ Yorùbá: – Placeholder images
   in unused images section
 * TWEAK: Added `security.md` file with information to report security issues

#### 3.6.0 Ìtumọ̀ Yorùbá: – 12/Sep/2024

 * FEATURE: Premium Ìtumọ̀ Yorùbá: – Auto-detect images lacking dimension attributes
   and add them to improve CLS
 * FIX: Fixed the issue that disabled WebP conversion due to checking all shell 
   commands for WebP compression
 * FIX: Premium Ìtumọ̀ Yorùbá: – Unused Images Ìtumọ̀ Yorùbá: – The unused image
   size deletion functionality does not work when images are not in the /yyyy/mm/
   folder
 * REFACTOR: Removed unnecessary static methods in WebP class
 * TWEAK: Image compression Ìtumọ̀ Yorùbá: – Rolled back to using popup error notices
   as in versions prior to 3.4.0
 * TWEAK: Added a more descriptive error with resolution proposals for failed gzip
   compression and browser cache tests
 * TWEAK: Fix broken unused image list thumbnails and download as csv link in Multisite
 * TWEAK: Fix the singleton pattern in Heartbeat class
 * TWEAK: Image compression functionality added to the Media Library page
 * TWEAK: Premium Ìtumọ̀ Yorùbá: – Cache Ìtumọ̀ Yorùbá: – Added support for Aelia
   Currency Switcher plugin
 * TWEAK: Premium Ìtumọ̀ Yorùbá: – Unused images Ìtumọ̀ Yorùbá: – improve clarity
   in UI for images in post revisions
 * TWEAK: Added additional checks to the `implode()` function to mitigate the risk
   of fatal errors on certain instances

#### 3.5.0 Ìtumọ̀ Yorùbá: – 14/Aug/2024

 * FEATURE: Premium Ìtumọ̀ Yorùbá: – Host Google and minimal analytics scripts locally
 * FIX: Premium Ìtumọ̀ Yorùbá: – Cache Ìtumọ̀ Yorùbá: – Single page cache purge/
   preload feature isnÌtumọ̀ Yorùbá: ’t working
 * TWEAK: Add logging for the WebP feature
 * TWEAK: Allow minification of script modules
 * TWEAK: Cache Ìtumọ̀ Yorùbá: – Purge the cache when the site is migrated
 * TWEAK: Improvements to asset minification cache logic
 * TWEAK: Improvements to reSmushIt curl error message
 * TWEAK: Minify Ìtumọ̀ Yorùbá: – Added an option to disable Google Fonts processing
   when it causes conflicts with other plugins
 * TWEAK: Move all WPO files from the `uploads` folder to `uploads/wpo`
 * TWEAK: Style improvement of the loading modals

#### 3.4.2 Ìtumọ̀ Yorùbá: – 03/Jul/2024

 * FIX: Removes unnecessary heartbeat calls for retrieving information about images

#### 3.4.1 Ìtumọ̀ Yorùbá: – 26/Jun/2024

 * FIX: Issue with bulk editing on the posts and pages edit screen

#### 3.4.0 Ìtumọ̀ Yorùbá: – 25/Jun/2024

 * FEATURE: Premium Ìtumọ̀ Yorùbá: – Smush Ìtumọ̀ Yorùbá: – Bulk compress / restore
   from media library
 * FIX: Deactivate the form for minifying JS/CSS settings when the corresponding
   option is disabled
 * REFACTOR: The functionality for the ‘Unused Images’ feature in ACF has been moved
   to a separate class
 * TWEAK: Add UpdraftCentral commands for the latest WP-Optimize features
 * TWEAK: Adjusted the scheduled preload time for improved performance
 * TWEAK: Auto-update advanced-cache.php settings during site migration
 * TWEAK: Cache Ìtumọ̀ Yorùbá: – Human-readable file names for the cache directory
 * TWEAK: Caching related cron jobs are activated even though cache is disabled
 * TWEAK: Image compression Ìtumọ̀ Yorùbá: – Updated message for restoring images
   action
 * TWEAK: Implement Heartbeat API for image compression progress updates
 * TWEAK: Improving vendor autoload
 * TWEAK: Introduces a hook (`wpo_force_webp_serve_using_altered_html`) for changing
   WebP serving method
 * TWEAK: Minify Ìtumọ̀ Yorùbá: – Exclude .min files from minification
 * TWEAK: Minify Ìtumọ̀ Yorùbá: – Improve list of processed files UI
 * TWEAK: Optimization of the get_uncompressed_image query
 * TWEAK: Persist script loading strategy when minifying JS files
 * TWEAK: Premium Ìtumọ̀ Yorùbá: – Compatibility with Curcy WooCommerce multi currency
   plugin
 * TWEAK: Premium Ìtumọ̀ Yorùbá: – Unused Images Ìtumọ̀ Yorùbá: – Added an option
   to delete original images when scaled versions exist

#### 3.3.2 Ìtumọ̀ Yorùbá: – 16/Apr/2024

 * FIX: Ensure the admin bar is not cached when caching is enabled for both logged-
   in and guest users
 * REFACTOR: Remove unused code
 * TWEAK: Cache Ìtumọ̀ Yorùbá: – Prevent sitemaps being cached
 * TWEAK: Display a notice when static browser cache is enabled but not working
 * TWEAK: Premium Ìtumọ̀ Yorùbá: – Added “Lost your password?” link on pluginÌtumọ̀
   Yorùbá: ’s page
 * TWEAK: Premium Ìtumọ̀ Yorùbá: – Unused images Ìtumọ̀ Yorùbá: – Detect ElementorÌtumọ̀
   Yorùbá: ’s ‘Video’ widgetÌtumọ̀ Yorùbá: ’s image
 * TWEAK: Recognise Rank Math plugin tables as used in database optimization
 * TWEAK: Reduce .htaccess file write operations when WebP is enabled
 * TWEAK: Seasonal notice content update for 2024
 * TWEAK: Unused Images Ìtumọ̀ Yorùbá: – Unused tab displays multiple images for
   compressed images with WebP Conversion
 * TWEAK: Prevent multiple AJAX requests being generated by repeated clicks on the“
   Purge Cache” button
 * TWEAK: Call the `litespeed_finish_request()` function when attempting to close
   browser connection on LiteSpeed servers

#### 3.3.1 Ìtumọ̀ Yorùbá: – 06/Mar/2024

 * FIX: Cache Ìtumọ̀ Yorùbá: – Compatibility issue with JetpackÌtumọ̀ Yorùbá: ’s
   infinity scroll feature
 * FIX: Cache Ìtumọ̀ Yorùbá: – DonÌtumọ̀ Yorùbá: ’t cache activity stream (ActivityPub
   plugin compatibility)
 * FIX: Cache Ìtumọ̀ Yorùbá: – Page not cached comment is added to `robots.txt`
 * TWEAK: Fix PHP warnings when server variables are not available
 * TWEAK: Fix Unexpected response alert and PHP warning when cache preloading is
   triggered manually
 * TWEAK: Migrate from setInterval to WP heartbeat API to refresh information about
   backend tasks
 * TWEAK: Optimization of the WebP Implementation
 * TWEAK: Update dashboard notice to include all of our plugins
 * TWEAK: Update the footer review prompt

#### 3.3.0 Ìtumọ̀ Yorùbá: – 31/Jan/2024

 * FEATURE: Premium Ìtumọ̀ Yorùbá: – Ability to preload and purge caches from individual
   post/page
 * FIX: Premium Ìtumọ̀ Yorùbá: – Unused Images Ìtumọ̀ Yorùbá: – Recognise ElementorÌtumọ̀
   Yorùbá: ’s Container, and Section widget background images
 * FIX: Avoid having repeated minified scripts in the same bundle, it breaks the
   code in some specific cases
 * FIX: Cache Ìtumọ̀ Yorùbá: – TranslatePress compatibility Ìtumọ̀ Yorùbá: – Post
   updates purges cache for all related translated languages
 * FIX: Only try to parse canonical URLs if there is a path or querystring, needed
   for WPML with multi-domain compatibility
 * TWEAK: Add cron de-scheduling of all wpo_* events during plugin uninstall
 * TWEAK: Cache Ìtumọ̀ Yorùbá: – Always add source code comment about page not being
   cached, but only add details when WP_DEBUG is ON
 * TWEAK: Cache Ìtumọ̀ Yorùbá: – Fix issue with excluding encoded (non-latin) URLs
 * TWEAK: Do not attempt to close browser connection when the context is not an 
   AJAX action
 * TWEAK: Minify Ìtumọ̀ Yorùbá: – Logging more information about why minify static
   assets cache gets invalidated and regenerated
 * TWEAK: Revert to the original `matthiasmullie/minify` repository after confirming
   resolution of previous issues
 * TWEAK: Setup Cron job to clear failed smush tasks from DB
 * TWEAK: Using clear text user agent strings instead of regular expressions to 
   identify web browsers for improved clarity
 * TWEAK: Updater library in the Premium version updated to the current release 
   series

[See changelog for all versions](https://plugins.svn.wordpress.org/wp-optimize/trunk/changelog.txt).

## Àkójọpọ̀ Meta

 *  Ẹ̀yà **4.6.1**
 *  Ìgbàgbọ́hùn tó kẹ́yìn **ọ̀sẹ̀ 4 sẹ́yìn**
 *  Àwọn ìgbéwọlẹ̀ tó ṣiṣẹ́ **1+ mílíọ̀nù**
 *  Ẹ̀yà WordPress ** 4.9 tàbí ju bẹ́ẹ̀ lọ **
 *  Dánwò dé **7.1**
 *  Ẹ̀yà PHP ** 7.2 tàbí ju bẹ́ẹ̀ lọ **
 *  Àwọn èdè
 * [Azerbaijani](https://az.wordpress.org/plugins/wp-optimize/), [Chinese (China)](https://cn.wordpress.org/plugins/wp-optimize/),
   [Czech](https://cs.wordpress.org/plugins/wp-optimize/), [Dutch](https://nl.wordpress.org/plugins/wp-optimize/),
   [Dutch (Belgium)](https://nl-be.wordpress.org/plugins/wp-optimize/), [English (Australia)](https://en-au.wordpress.org/plugins/wp-optimize/),
   [English (Canada)](https://en-ca.wordpress.org/plugins/wp-optimize/), [English (New Zealand)](https://en-nz.wordpress.org/plugins/wp-optimize/),
   [English (South Africa)](https://en-za.wordpress.org/plugins/wp-optimize/), [English (UK)](https://en-gb.wordpress.org/plugins/wp-optimize/),
   [English (US)](https://wordpress.org/plugins/wp-optimize/), [French (France)](https://fr.wordpress.org/plugins/wp-optimize/),
   [Galician](https://gl.wordpress.org/plugins/wp-optimize/), [Georgian](https://ka.wordpress.org/plugins/wp-optimize/),
   [German](https://de.wordpress.org/plugins/wp-optimize/), [Hebrew](https://he.wordpress.org/plugins/wp-optimize/),
   [Hungarian](https://hu.wordpress.org/plugins/wp-optimize/), [Italian](https://it.wordpress.org/plugins/wp-optimize/),
   [Japanese](https://ja.wordpress.org/plugins/wp-optimize/), [Korean](https://ko.wordpress.org/plugins/wp-optimize/),
   [Persian](https://fa.wordpress.org/plugins/wp-optimize/), [Polish](https://pl.wordpress.org/plugins/wp-optimize/),
   [Portuguese (Portugal)](https://pt.wordpress.org/plugins/wp-optimize/), [Romanian](https://ro.wordpress.org/plugins/wp-optimize/),
   [Russian](https://ru.wordpress.org/plugins/wp-optimize/), [Slovenian](https://sl.wordpress.org/plugins/wp-optimize/),
   [Spanish (Argentina)](https://es-ar.wordpress.org/plugins/wp-optimize/), [Spanish (Chile)](https://cl.wordpress.org/plugins/wp-optimize/),
   [Spanish (Colombia)](https://es-co.wordpress.org/plugins/wp-optimize/), [Spanish (Ecuador)](https://es-ec.wordpress.org/plugins/wp-optimize/),
   [Spanish (Mexico)](https://es-mx.wordpress.org/plugins/wp-optimize/), [Spanish (Peru)](https://pe.wordpress.org/plugins/wp-optimize/),
   [Spanish (Spain)](https://es.wordpress.org/plugins/wp-optimize/), àti [Spanish (Venezuela)](https://ve.wordpress.org/plugins/wp-optimize/).
 *  [Túmọ̀ sí èdè rẹ](https://translate.wordpress.org/projects/wp-plugins/wp-optimize)
 * Àwọn àmì
 * [cache](https://yor.wordpress.org/plugins/tags/cache/)[caching](https://yor.wordpress.org/plugins/tags/caching/)
   [image cache](https://yor.wordpress.org/plugins/tags/image-cache/)[minify](https://yor.wordpress.org/plugins/tags/minify/)
   [performance cache](https://yor.wordpress.org/plugins/tags/performance-cache/)
 *  [Ìwòye Tó Péye](https://yor.wordpress.org/plugins/wp-optimize/advanced/)

## Àwọn ìbò

 4.8 lára àwọn ìràwọ̀ 5.

 *  [  2,391 5-star reviews     ](https://wordpress.org/support/plugin/wp-optimize/reviews/?filter=5)
 *  [  79 4-star reviews     ](https://wordpress.org/support/plugin/wp-optimize/reviews/?filter=4)
 *  [  25 3-star reviews     ](https://wordpress.org/support/plugin/wp-optimize/reviews/?filter=3)
 *  [  26 2-star reviews     ](https://wordpress.org/support/plugin/wp-optimize/reviews/?filter=2)
 *  [  87 1-star reviews     ](https://wordpress.org/support/plugin/wp-optimize/reviews/?filter=1)

[Your review](https://wordpress.org/support/plugin/wp-optimize/reviews/#new-post)

[Wo gbogbo àwọn àgbéyẹ̀wò](https://wordpress.org/support/plugin/wp-optimize/reviews/)

## Àwọn Olùkópa

 *   [ David Anderson / Team Updraft ](https://profiles.wordpress.org/davidanderson/)
 *   [ ruhanirabin ](https://profiles.wordpress.org/ruhanirabin/)
 *   [ DNutbourne ](https://profiles.wordpress.org/dnutbourne/)
 *   [ aporter ](https://profiles.wordpress.org/aporter/)
 *   [ snightingale ](https://profiles.wordpress.org/snightingale/)
 *   [ LumberHack ](https://profiles.wordpress.org/lumberhack/)
 *   [ Venkat Raj ](https://profiles.wordpress.org/webulous/)

## Ìrànlọ́wọ́

Àwọn ọ̀ràn tí a yanjú ní oṣù méjì tó kọjá:

     14 nínú 16

 [Wo àpéjọ ìrànlọ́wọ́](https://wordpress.org/support/plugin/wp-optimize/)

## Ṣe ìtọrẹ

Ṣé o fẹ́ ṣe àtìlẹ́yìn fún ìlọsíwájú plugin yìí?

 [ Ṣe ìtọrẹ sí plugin yìí ](https://david.dw-perspective.org.uk/donate)