The product is designed as an automatic WordPress optimization engine and it starts working just after installation. But sometimes it still needed to be fine-tuned or troubleshot on particular sites.
Here you can see the overall working status of the WordPress cache and do some operations if necessary. See below.
Status#
Here we can see all background activities.
- Particular update (auto)
Shows processing of posts updating according to specified revalidation settings.
- Particular update (scheduled)
Shows processing of posts updating according to specified scheduled revalidation settings.
- Cleanup old
Automatically deleting the old content according to common and user cache timeout settings. Can produce medium server loading.
Statistics#
Here we can see the total amount of cached pages and occupied cache size. The data can be refreshed by pressing the corresponding button.
Note. The refreshing could take a long time (several minutes) and it’s OK.
Operate#
All posts are revalidated automatically if a relevant option is enabled. But sometimes it is needed to do it manually.
The operation’s scope can also be chosen – for all or individual addresses:
- All
All pages according to the specified scope.
- Specified URLs, URIs, or expressions
Site’s URLs or relative URIs each on new line or leave empty for site’s root. Also, revalidation expressions can be also used.
Available operations:
- Delete cache
Deletes all cached content. The status will be auto-refreshed after completion. Server’s cache is deleted automatically if ‘Update cache (if available)‘ option is set.
Warning: can produce high server loading.
- Revalidate cache
Just revalidates the cached data without erasing previously cached content that preserves minimal server loading. If the ‘Lazy revalidation’ is active, the content will be updated transparently to the user rather than the first user will have to wait for content updating and next users get previously cached version. Server’s cache is deleted automatically if ‘Update cache (if available)‘ option is set.
- Revalidate cache if needed
The same as the previous one, only if the page has already been optimized, then re-optimization is not performed.
- Delete server’s cache (if available)
Tries to clear server cache if available. It works as same as this similar option.
Content optimization queue#
Here is a list of all pages that are need to be optimized. Pressing ‘Delete’ will clear the queue (not optimized pages itself).
State#
Each item has several states:
- Green (finished)
Optimization has been completed.
- Black (finished)
Optimization is not needed or already done.
- Red (finished)
Optimization had error. There is not enough PHP memory or there is PHP error that can be checked in error log.
- Blue (in-progress)
Optimization is in progress. Number of parallel optimizations can be set.
- Gray (pending)
Optimization has not been started.
Note: Only 10 last finished items are shown.
Initiator#
Indicates the reason for the update. Arranged in descending order of priority.
- Particular manual update
The update was launched manually from the ‘Operate‘ block.
- Particular auto update
The update was started after the post was changed.
- Particular scheduled update
The update was launched according to the established schedule.
- External request
The update was launched due to the expiration of the lifetime during the external opening of a page on the site.
- All update
The update was launched manually – either from the ‘Operate‘ block or after finishing the setup wizard.
HTML checker#
Performs error checking of HTML markup of any page by URL. Mostly it is used while troubleshooting particular pages on the site. As a result, the list of notices and warnings will be shown. The warnings mean that content might be processed incorrectly.