Turbopress Database Diagnostics
by robbsie 1 (0 reviews)

Turbopress Database Diagnostics

Shows why WordPress loads slowly: autoload size with the plugin responsible, database bloat, and the state of object cache and OPcache.

Turbopress Database Diagnostics ranks #56,370 among WordPress.org plugins with 1+ active installations, is #2,854 of 5,058 in the Security category, a 1/5 rating from 0 reviews, and was last updated Aug 23, 2026. Data from WordPress.org, refreshed twice daily — see methodology.

Compatible with WP 7.1
v1.0.5 Current Version v1.0.5
Updated 2 months ago Last Update on 23 Aug, 2026
Refreshed 1 week ago Last Refreshed on
#2,854 of 5,058 in Security
View on WordPress.org
Rank
#56,370
— No change
Active Installs
1+
— No change
KW Avg Position
59
0.5 worse
Downloads
305
+2 today
Support Resolved
0%
— No change
Rating
20%
Review 1 out of 5
1 (0 reviews)

Next Milestone 10

Total Progress 30%
0+ 10+
43,433
Ranks to Climb
-
Growth Needed
8,000,000
Active Installs
Pro

Unlock Exact Install Count

See the precise estimated active installs for this plugin, calculated from real-time ranking data.

  • Exact install estimates within tiers
  • Track install growth over time
  • Milestone progress predictions
Upgrade to Pro
Need 7 more installs to reach 10+

Rank Changes

53,552 54,961 56,370 57,779 59,189 31-10-2026 01-11-2026 02-11-2026 03-11-2026 04-11-2026 05-11-2026 06-11-2026 07-11-2026
52,601 58,269 63,937 69,604 75,272 23-10-2026 24-10-2026 25-10-2026 26-10-2026 27-10-2026 28-10-2026 29-10-2026 30-10-2026 31-10-2026 01-11-2026 02-11-2026 03-11-2026 04-11-2026 05-11-2026 06-11-2026 07-11-2026
Current #56,370
Change
Best #

Upgrade to Pro

Unlock 30-day and 90-day rank history charts with a Pro subscription.

Upgrade Now

Active Installs Growth

Active Installs 0,000,000+
Growth +0.0%
Peak 0,000,000

Downloads Growth

0 10 31-10-2026 01-11-2026 02-11-2026 03-11-2026 04-11-2026 05-11-2026 06-11-2026 07-11-2026
0 10 23-10-2026 24-10-2026 25-10-2026 26-10-2026 27-10-2026 28-10-2026 29-10-2026 30-10-2026 31-10-2026 01-11-2026 02-11-2026 03-11-2026 04-11-2026 05-11-2026 06-11-2026 07-11-2026
Downloads
Growth
Peak

Upgrade to Pro

Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.

Upgrade Now

Reviews & Ratings

1.0
0 reviews
Overall 20%
5
0 (0%)
4
0 (0%)
3
0 (0%)
2
0 (0%)
1
0 (0%)

Frequently Asked Questions

Common questions about Turbopress Database Diagnostics

Reading is safe. The scan runs two queries against the options table and a handful of aggregate queries against INFORMATION_SCHEMA, all of them bounded. Nothing runs during normal page loads. Cleanup deletes rows, and deleting rows is never risk free. Every operation shows you the affected row count first and requires confirmation. Make a backup before you delete anything.
Because it does not know. Option names carry no author. Attribution is derived from prefixes, and when a prefix matches nothing on the installation, the honest answer is that the origin is unknown. A guess would send you looking in the wrong place.
Yes. The prefix table is filterable: add_filter( 'turbopress_diagnostics_plugin_prefixes', function ( $prefixes, $plugins, $themes ) { $prefixes['acme'] = array( 'type' => 'plugin', // plugin, mu_plugin, theme, // removed_plugin, removed_theme 'id' => 'acme-widgets', // directory slug 'label' => 'Acme Widgets', // name shown in the report ); return $prefixes; }, 10, 3 ); The array is keyed by prefix without a trailing separator. $plugins contains the installed plugins and must-use plugins keyed by slug, $themes the installed themes keyed by stylesheet, so you can decide whether to register anything at all. Entries that do not follow this shape are discarded, because a malformed entry would produce a wrong statement about who is responsible for a payload. If you are a plugin author whose options are showing up as unattributed on other people's sites, adding this filter to your own plugin fixes it for every user at once.
Yes, and that is the point of it for anyone looking after more than one site. wp turbopress-diagnostics scan prints the score and the figures behind it, wp turbopress-diagnostics report the full JSON document, wp turbopress-diagnostics categories what can be cleaned up, and wp turbopress-diagnostics cleanup <category> runs one category. Cleanup simulates unless you add --execute, and asks for confirmation unless you add --yes. wp help turbopress-diagnostics lists every subcommand and option. The commands are also shown on the plugin screen, under the settings.
turbopress_diagnostics_loopback_sslverify decides whether the loopback request verifies the TLS certificate. Return false on a staging environment behind a self signed certificate, where the check would fail for a reason unrelated to caching. turbopress_diagnostics_table_prefixes registers table name prefixes so leftover tables of a plugin that is gone are named rather than ignored, in the same way as the option prefixes above. turbopress_diagnostics_count_time_budget sets how many seconds an exact orphan count may take on a large table before it falls back to a sample. The default is 5. The deadline is enforced by the database server, so an overrunning query is stopped rather than left to consume the PHP execution time. Raise it to trade a slower scan for an exact number.
Probably not. Managed hosting commonly puts opcache_get_status into disable_functions, or restricts it with opcache.restrict_api. OPcache keeps working; only the counters are unreadable. The plugin tells that apart from a genuinely disabled OPcache, leaves it out of the score instead of counting it against your site, and still reports the configuration through opcache_get_configuration, which usually survives. It also asks whether a WordPress core file is currently in the cache, which answers whether OPcache is doing its job even when the numbers are hidden.
No. It is a single GET request to your own home URL, made by your own server, to look at the response headers. Nothing is sent to any third party. You can switch it off in the settings, in which case page cache detection is skipped.
It does not. Redis and Valkey statistics are read through the connection the object cache drop-in has already established. If the drop-in does not expose its client, the plugin reports that no statistics are available rather than trying to connect on its own.
Yes, as JSON. This is meant for support tickets: it contains the measurements and option names, no option values.

Sign In / Register

You need to sign in or register to use this feature.