Latest version 2.6.3 available

Database Check – what does this button do?

The Database Check button is used to check the condition of your WordPress site’s database.
It performs a safe analysis that does not delete or modify anything – it only shows what can potentially be cleaned or optimized.

You can think of it as a database scan before cleaning.


What exactly does Database Check analyze?

After clicking the button, the plugin analyzes the database and counts unnecessary or outdated elements, such as:

WordPress data

  • old and expired temporary data (transients),

  • orphaned technical data (leftovers after deleted posts, users, or comments),

  • items in the trash,

  • post revisions (old versions of posts),

  • auto drafts,

  • comments marked as spam or moved to trash,

  • unconfirmed users,

  • old or unused CRON jobs.

WooCommerce data (if WooCommerce is active)

  • old, completed, or failed system tasks,

  • old technical logs,

  • outdated customer sessions,

  • old unpaid orders,

  • unused stock-related data and reservations.

If WooCommerce is not installed, this part of the analysis is automatically skipped.


What will the user see after the check?

After the analysis is completed, a clear summary is displayed, for example:

  • how many items can be removed in each category,

  • which parts of the database are clean,

  • which areas may require optimization.

This allows you to know exactly what would be cleaned before deciding to perform the actual cleanup.


What Database Check does NOT do

  • it does not delete any data,

  • it does not modify the database structure,

  • it does not affect how the site works,

  • it does not make any automatic decisions.

It is analysis and reporting only.


Security and performance

  • The analysis is available only to administrators.

  • It is protected against accidental execution.

  • For large databases, it runs in stages to avoid server overload.

  • The maximum analysis time is a few minutes for very large sites.


When should you use Database Check?

  • before cleaning the database,

  • when the site feels slower and you want to check possible causes,

  • after a long period without optimization,

  • before migration or creating a backup.


Summary

Database Check is a safe diagnostic tool that shows:

“What can be cleaned and how much of it there is”

before you decide to take any action.

Database Optimization – what does this button do?

The Database Optimization button is used to clean and optimize your WordPress site’s database.
Unlike Database Check, this action actually removes unnecessary data and optimizes database tables to improve performance.

This process is designed to be safe and efficient, even for large websites.


What exactly does Database Optimization do?

After clicking the button, the plugin performs a full database cleanup and optimization by:

  • removing unnecessary and outdated data from the database,

  • running all operations inside secure database transactions,

  • processing large tables in stages to avoid server overload,

  • optimizing database tables after cleanup to improve performance.


What data is cleaned in WordPress?

During optimization, the plugin removes the following WordPress-related data:

Options and transients

  • unused cron jobs,

  • transients without expiration time,

  • site transients without expiration time,

  • expired transients,

  • all remaining transients.

Orphaned metadata

  • post meta data without related posts,

  • user meta data without related users,

  • comment meta data without related comments.

Posts and content

  • post revisions,

  • posts moved to the trash,

  • auto drafts.

Comments

  • spam comments,

  • comments in the trash.

CRON jobs

  • old or orphaned CRON tasks older than 24 hours.

Duplicate data

  • duplicate entries in post meta,

  • duplicate entries in user meta,

  • duplicate entries in comment meta.


What data is cleaned in WooCommerce (if active)?

If WooCommerce is installed and active, the optimization also includes:

Action Scheduler

  • completed actions,

  • failed actions older than 7 days,

  • canceled actions,

  • pending actions older than 30 days.

Action Scheduler logs

  • logs related to completed actions,

  • orphaned logs without related actions,

  • logs older than 30 days.

Other WooCommerce data

  • old claim entries older than 30 days,

  • orphaned action groups,

  • customer sessions older than 7 days.

If WooCommerce is not installed, these steps are skipped automatically.


Safety and performance

  • All cleanup operations are executed within database transactions to ensure data integrity.

  • Large tables are processed in batches to prevent timeouts and server overload.

  • After cleanup, database tables are analyzed and optimized for better performance.


When should you use Database Optimization?

  • after reviewing the results from Database Check,

  • when the database contains a large amount of unnecessary data,

  • if the website performance has decreased,

  • as part of regular maintenance.


Summary

Database Optimization is a powerful cleanup tool that:

  • removes unnecessary WordPress and WooCommerce data,

  • safely processes even large databases,

  • optimizes database tables after cleanup,

helping keep your site fast, clean, and efficient.

Autoload Optimization – what does this button do?

The Autoload Optimization button is used to optimize how WordPress loads data from the database during every page request.
It focuses on the autoload options stored in the wp_options table, which are automatically loaded on each page load.

This optimization helps reduce memory usage and improve site performance without affecting essential functionality.


What exactly does Autoload Optimization do?

After clicking the button, the plugin analyzes and optimizes autoloaded options by:

  • optimizing how options are marked as autoloaded in the database,

  • running a multi-step optimization process designed for performance and safety,

  • automatically adapting to your WordPress and WooCommerce configuration.


How does autoload optimization work?

The optimization process includes the following actions:

Autoload value normalization

  • standardizes autoload values to ensure consistency (yes or no).

Transients optimization

  • disables autoload for all transients, as they do not need to be loaded on every request.

Non-critical options

  • disables autoload for options that are not required on every page load.

Critical options

  • ensures autoload is enabled for options that are required for WordPress to function correctly.


What are considered critical options?

WordPress core options

  • essential WordPress settings such as site URLs, active plugins, scheduled tasks, user configuration, and widgets.

WooCommerce options (if active)

  • essential store settings such as currency, payment methods, shipping configuration, and product-related settings.

If WooCommerce is not installed, WooCommerce-related optimization is skipped automatically.


Safety and reliability

  • The process uses caching to avoid unnecessary repeated operations.

  • Secure database queries are used to protect against SQL issues.

  • Errors are safely handled during the optimization process.

  • Only authorized users can run this optimization.


What are the benefits of Autoload Optimization?

  • reduced PHP memory usage by loading fewer unnecessary options,

  • faster page loading times,

  • full functionality of critical WordPress and WooCommerce features is preserved.


When should you use Autoload Optimization?

  • if your site loads slowly despite a clean database,

  • when the wp_options table has grown large over time,

  • after installing and removing multiple plugins,

  • as part of regular performance maintenance.


Summary

Autoload Optimization improves performance by:

  • reducing the number of options loaded on every request,

  • keeping only essential options autoloaded,

  • maintaining full site and store functionality,

resulting in a faster and more efficient WordPress site.

Database Cleanup – what do the checkboxes do?

The Database Cleanup section allows you to choose exactly what type of data you want to remove from your database.
Each checkbox represents a specific cleanup action. You stay in full control and decide what will be cleaned.

All cleanup actions are designed to be safe, controlled, and optimized for performance.


What can you clean using Database Cleanup?

Post revisions

Removes all saved revisions of posts.
These are older versions of posts created automatically by WordPress and are usually no longer needed.


Posts in trash

Permanently removes posts that were moved to the trash.
This helps clean up content that was already deleted but still exists in the database.


Auto drafts

Deletes automatically created draft posts.
These are temporary drafts created by WordPress that were never published.


Spam comments

Removes all comments marked as spam.
This helps reduce database size and keeps comment data clean.


Comments in trash

Deletes comments that were moved to the trash.
These comments are no longer visible on the site and can be safely removed.


Expired transients

Removes temporary data that has already expired.
Only outdated transients are removed; active ones are left untouched.


All transients

Removes all transient data.
This clears cached temporary values while keeping the database structure intact.


Orphaned post metadata

Removes post metadata that no longer belongs to any existing post.
This usually happens after posts are deleted.


Orphaned user metadata

Removes user metadata that is no longer linked to any user account.
This helps clean leftovers after users are removed.


Orphaned comment metadata

Removes metadata that belongs to comments which no longer exist.
This keeps comment-related data consistent and clean.


Expired or orphaned CRON jobs

Removes old or unused scheduled tasks.
System-critical WordPress tasks are preserved.


Duplicate post metadata

Removes duplicate post metadata entries.
The original value is kept, and only unnecessary duplicates are removed.


Duplicate user metadata

Removes duplicate metadata for users.
This reduces redundant data while preserving correct values.


Duplicate comment metadata

Removes duplicate metadata entries related to comments.
Only repeated copies are removed.


Optimize all tables

Optimizes all database tables after cleanup.
This reorganizes table data to improve query performance and efficiency.


Safety and performance

  • Cleanup operations run in controlled steps to avoid server overload.

  • Large datasets are processed gradually for stability.

  • All actions are protected against accidental data loss.

  • Only users with proper permissions can run cleanup actions.


When should you use Database Cleanup?

  • after reviewing results from Database Check,

  • when the database has grown over time,

  • after removing plugins, users, or content,

  • as part of regular site maintenance.


Summary

Database Cleanup gives you precise control over database maintenance by allowing you to:

  • choose exactly what data to remove,

  • safely clean unnecessary and outdated records,

  • improve database performance and efficiency,

while protecting important data and site stability.

Why are Database Optimization and Database Cleanup separated?

Although Database Optimization and Database Cleanup checkboxes may look similar, they are designed for different purposes and different user needs.
This separation is intentional and improves both safety and flexibility.


Database Optimization – automated, safe baseline cleanup

The Database Optimization button is designed as a one-click, automated cleanup.

Its purpose is to:

  • safely remove the most common unnecessary data,

  • focus on system-level cleanup (especially WooCommerce),

  • improve performance without requiring decisions from the user.

This action always runs a predefined and carefully selected set of operations.
The user does not choose individual items – everything is handled automatically.

This makes Database Optimization ideal when:

  • you want a quick and safe cleanup,

  • you manage a WooCommerce store,

  • you are not sure which data can be safely removed,

  • you prefer an automated approach.


Database Cleanup checkboxes – full control and precision

The Database Cleanup section is designed for users who want full control.

Each checkbox represents a specific type of data that can be removed.
Nothing is cleaned unless the user explicitly selects it.

This allows:

  • selective cleanup of WordPress-specific data,

  • removal of content-related data such as post revisions or spam comments,

  • advanced cleanup options like duplicate metadata or full table optimization.

This approach is useful when:

  • you want to clean only specific data,

  • you know exactly what should be removed,

  • you want to avoid touching certain parts of the database,

  • you maintain a non-WooCommerce WordPress site.


Why can each cleanup option be selected separately?

Not all data is equally safe or equally desired to remove.

Some examples:

  • post revisions may be useful for editors,

  • auto drafts may be needed during content creation,

  • transients may temporarily improve performance,

  • metadata duplicates may exist for compatibility reasons.

By separating cleanup actions into individual checkboxes:

  • users stay in control,

  • accidental data removal is avoided,

  • advanced users can fine-tune optimization,

  • different site setups are respected.


Why are these features not combined into one button?

Combining everything into one action would:

  • remove user choice,

  • increase the risk of unwanted data loss,

  • make the plugin harder to use for different site types,

  • force WordPress-only users into WooCommerce-related logic.

The separation ensures:

  • a safe default path (Database Optimization),

  • an advanced path for manual control (Database Cleanup),

  • clarity about what will be cleaned and why.


How should these tools be used together?

For best results, they are meant to complement each other:

  1. Use Database Optimization first
    – to perform safe, automated cleanup and WooCommerce optimization.

  2. Use Database Cleanup checkboxes afterward
    – to selectively clean additional WordPress data or fine-tune the database.


Summary

The separation exists because:

  • Database Optimization is automated and optimized for safety and WooCommerce,

  • Database Cleanup checkboxes provide precision and user control,

  • different websites require different cleanup strategies,

  • users should decide how much control they want.

Together, these tools provide both simplicity and advanced flexibility, without compromising safety or performance.

Scan Unused Tables – what does this button do?

The Scan Unused Tables button checks your database for tables that are no longer used by WordPress or any active plugins.

These tables are often left behind after:

  • uninstalling plugins,

  • removing custom features,

  • migrating or restoring a website.

The scan is read-only and does not delete anything. It only identifies tables that may be safe to remove.


What exactly does Scan Unused Tables do?

When you run the scan, the plugin:

  • analyzes all tables in your WordPress database,

  • ignores core WordPress tables and system-critical tables,

  • checks whether tables belong to currently active plugins,

  • looks for real usage of each table across the database,

  • safely processes large databases in stages,

  • stores scan results temporarily to avoid unnecessary repeated scans.


How does the plugin decide if a table is unused?

The scan uses multiple checks to avoid false positives:

Core WordPress protection

Standard WordPress tables are automatically excluded and never flagged as unused.


Active plugin detection

The plugin checks whether a table belongs to:

  • an active plugin,

  • a known plugin naming pattern,

  • commonly used plugin table structures.

This ensures tables from active plugins are not incorrectly marked as unused.


Usage and reference analysis

Each table is checked to see if it is:

  • referenced by WordPress settings,

  • referenced by post, user, comment, or term data,

  • linked through database relationships,

  • recently updated or actively used.

Only tables that show no meaningful usage are flagged.


What will the user see after the scan?

After the scan is completed, a detailed report is displayed showing:

  • a list of tables that may be unused,

  • the size of each table,

  • the reason why the table was marked as unused,

  • guidance on whether the table can be safely removed.

This gives you full transparency before taking any action.


Safety and performance

  • The scan works only for administrators.

  • No tables are deleted automatically.

  • Large databases are scanned gradually to prevent server overload.

  • Results are cached for a limited time to improve performance.

  • If some database information is unavailable, the scan adapts safely.


When should you use Scan Unused Tables?

  • after uninstalling plugins,

  • after site migration or restoration,

  • when the database size keeps growing,

  • before manual database cleanup,

  • as part of periodic database maintenance.


Why is this scan separate from database cleanup?

Unused tables require manual review.
Automatically deleting them could remove data that is still needed by custom code or integrations.

That is why this tool:

  • only detects and reports,

  • leaves the final decision to the user,

  • prioritizes safety over automation.


Summary

Scan Unused Tables is a diagnostic tool that helps you:

  • identify database tables that are likely no longer needed,

  • understand where database size comes from,

  • clean up leftovers from old plugins safely,

  • make informed decisions without risk.

It provides insight first — cleanup decisions always remain in your control.

Return →
All rights reserved. 2025