Peter Wilson

<p>This is a utility plugin for backporting a minor performance improvement scheduled for inclusion in WordPress 6.6 to earlier versions.</p>
<p>In WordPress 6.4 the function <code>wp_prime_option_caches()</code> was introduced to allow for multiple options to be queried in a single database call.</p>
<p>On sites without a persistent cache, temporary transients are stored in two options. One containing the transient itself, the other containing the timeout. These are stored as <code>_transient_[transient name]</code> and <code>_transient_timeout_[transient name]</code>.</p>
<p>In WordPress 6.6 and later, these options are primed by a single database call using the priming function. This plugin can be used on WordPress 6.4 and 6.5 to backport the functionality.</p>
<p>While a mild improvement on sites making limited use of transients, this can significantly reduce the number of database queries on sites running plugins making heavy use of transients.</p>


Performant Transients

Reduce the number of database calls querying transients.

Stoil Dobreff

Golemiq

<p><strong>0 Day Analytics</strong> is a comprehensive WordPress debugging and operational<br />
intelligence plugin. It is purpose-built for developers and site administrators<br />
who need real-time visibility into their PHP errors, scheduled tasks, database<br />
state, outgoing emails, HTTP requests, hook behaviour, and overall site health —<br />
all from a single admin interface.</p>
<p>Unlike general monitoring services, 0 Day Analytics runs entirely inside your<br />
WordPress installation with no third-party data collection. Every module is<br />
opt-in and designed with performance in mind.</p>
<p><strong>Plugin Website:</strong> <a href="https://0-day-analytics.com/0-day-analytics-wordpress-debugging-monitoring-toolkit/?src=readme" rel="nofollow ugc">0-day-analytics.com</a><br />
<strong>User Documentation:</strong> <a href="https://0-day-analytics.com/category/0-day-plugin/user-guide/?src=readme" rel="nofollow ugc">User Guide</a></p>
<h4>Dashboard</h4>
<p>A centralised overview page providing at-a-glance status for all active plugin<br />
modules. Displays real-time widgets for Error Log, Fatal Errors, Cron Jobs,<br />
Transients, HTTP Requests, WP Mail, REST API, and Security — each showing<br />
key metrics and recent events. Toggle individual module widgets on or off.<br />
The Dashboard is the default landing page when clicking the main plugin menu<br />
item, giving administrators immediate visibility into site health and activity<br />
without navigating to each module separately.</p>
<h4>Error Log Manager</h4>
<p>Read, search, filter, and manage your PHP/WordPress error log without leaving<br />
the admin. Engineered for very large (GB-sized) logs using a reverse-line reader<br />
that never performs a full-file read. Supports code-context viewing (click any<br />
error to see the surrounding source), per-severity filtering, log truncation,<br />
and download. Optionally randomise the log filename to reduce exposure.</p>
<h4>PHP Fatal Error Tracker</h4>
<p>Captures and stores PHP fatal errors in a dedicated database table, it records PHP errors even if the WP_DEBUG is turned off so they persist even after the log is rotated or overwritten. Each record includes<br />
error type, file, line, stack trace, and timestamp — searchable and filterable<br />
directly in the admin.</p>
<h4>Site Performance & Security Scanner</h4>
<p>Runs 32+ automated checks across three categories — Security, Speed, and<br />
Resources used — and presents a scored dashboard with actionable<br />
recommendations. Checks include: PHP version, WordPress version, SSL<br />
certificate, debug mode exposure, file permissions, database prefix, XML-RPC,<br />
login URL, active plugin count, autoloaded options, cron health, page caching,<br />
object caching, gzip compression, lazy loading, image optimisation, and more.</p>
<h4>Google PageSpeed & Core Web Vitals</h4>
<p>Analyse any URL directly from the WordPress admin using the Google PageSpeed<br />
Insights API. Displays Performance, Accessibility, Best Practices, and SEO<br />
scores with Lighthouse category breakdowns for both desktop and mobile. For that you need to provide your own PageSpeed Google API key.</p>
<h4>URL Tracker & Asset Analyser</h4>
<p>Automatically tracks visited page URLs on your site. For each recorded URL,<br />
you can collect all associated JS, CSS, and media assets (with file sizes), run<br />
a Google PageSpeed analysis, and review visit counts — making it easy to audit<br />
page weight and performance regressions over time.</p>
<h4>Cron Manager</h4>
<p>View, search, edit, manually run, and delete WordPress scheduled tasks. Shows<br />
next run time (UTC), recurrence interval, arguments, and last execution status.<br />
Supports bulk actions and advanced filtering.</p>
<h4>Transients Manager</h4>
<p>Browse, search, edit, and safely delete database transients. Displays expiry<br />
time, serialised value (pretty-printed), and size. Bulk delete supports<br />
filtered selections.</p>
<h4>Outgoing HTTP Requests Viewer</h4>
<p>Logs all outgoing <code>wp_remote_*</code> calls made by WordPress core, themes, and<br />
plugins. Records URL, method, status code, response time, triggering plugin,<br />
user, and full request/response detail. Export to CSV for external analysis.<br />
Advanced filtering by domain, plugin, status, and date range.</p>
<h4>Mail Logger & Composer</h4>
<p>Records every email sent through <code>wp_mail()</code> — including headers, body,<br />
attachments, CC, and BCC — and stores it in a searchable log. View the<br />
rendered email body, resend any logged email, or compose and send new emails<br />
directly from the admin. Supports HTML and plain-text previews.</p>
<h4>SMTP Configuration</h4>
<p>Configure custom SMTP settings (host, port, encryption, username, password)<br />
with a built-in test email tool. Optionally log SMTP debug output to the<br />
WordPress debug log.</p>
<h4>WP Hooks Monitor</h4>
<p>Define which WordPress actions and filters (core or custom) you want to<br />
observe. The Hooks Capture module records each invocation with its parameters,<br />
return value (for filters), and a full stack backtrace. Organise monitoring<br />
rules into named groups, enable/disable per hook, and review the captured<br />
output in a dedicated list view.</p>
<h4>DB Table Manager</h4>
<p>Browse, search, edit, and delete records across any table in your<br />
WordPress database — including custom plugin tables. Displays table size,<br />
engine, collation, row count, and schema information. Supports full and<br />
filtered truncation and table drop with confirmation.</p>
<h4>Server Info & System Status</h4>
<p>Displays real-time server metrics (CPU load, memory usage, disk space,<br />
PHP version, active extensions) as both admin-bar badges and a dashboard<br />
widget. Also provides a detailed environment report useful for support tickets<br />
and deployment checks.</p>
<h4>Plugin Version Switcher</h4>
<p>Roll back or switch between any previously downloaded version of an installed<br />
plugin without leaving the admin. Useful for quickly reverting after a bad<br />
update. Supports only free plugins from the WordPress repo.</p>
<h4>Code Snippets</h4>
<p>Write, save, and execute custom PHP snippets from the admin. Snippets support<br />
shortcodes, can be enabled/disabled individually, and are sandboxed before<br />
execution. Useful for one-off data migrations, testing custom logic, or<br />
generating dynamic output without creating a custom plugin.</p>
<h4>REST API Manager</h4>
<p>A security and management tool that gives full visibility and control over<br />
every registered REST API endpoint (<code>/wp-json/</code>). Inspect all registered<br />
routes, disable individual endpoints, restrict HTTP methods, and hide routes<br />
from discovery responses. Useful for hardening your site by removing<br />
unnecessary API surface area.</p>
<h4>WP Panel</h4>
<p>A centralised control panel for toggling WordPress core features and settings.<br />
Enable or disable comments, revisions, auto-updates, XML-RPC, the REST API,<br />
emojis, embeds, heartbeat behaviour, frontend asset loading, and more — all<br />
from a single, organised admin page. No code changes or custom snippets<br />
required.</p>
<h4>Traffic Analytics</h4>
<p>Privacy-focused website traffic monitoring built directly into WordPress — no external services or third-party scripts. Tracks unique visitors, pageviews, top pages, referrers, and technology breakdown (devices, browsers, operating systems) with a visual SVG-based dashboard. Choose between server-side (PHP) or client-side (JavaScript) tracking. Includes real-time visitor count automatic period comparison, configurable data retention, and a high-performance file-based write buffer.</p>
<p><strong>Important:</strong> By default, Traffic Analytics uses server-side (PHP) tracking mode. This method is less accurate because it cannot distinguish bots from real visitors as effectively and may miss visitors served from full-page caches. If you need more precise analytics, switch to client-side (JavaScript) tracking in the module settings — this mode runs a lightweight script in the browser that provides significantly more accurate visitor detection and pageview counting.</p>
<h4>Security Monitor</h4>
<p>Real-time security event monitoring and threat detection for your WordPress<br />
site. Tracks brute-force login attempts, burst rate limiting (DoS protection),<br />
user enumeration attempts, and blocked requests. Displays a summary dashboard<br />
with total events, critical alerts, blocked requests, and active incidents over<br />
the last 7 days. Includes an Emergency Lockdown button to immediately restrict<br />
site access during an active attack. Events are logged with severity level,<br />
IP hash (privacy-preserving), attempt counts, and detailed request information.</p>
<h4>Login & Auth Audit</h4>
<p>Comprehensive authentication event logging that tracks all login activity on<br />
your site. Records successful logins, failed login attempts, session expirations,<br />
and password resets with full context — including user, IP hash, user agent,<br />
and timestamp. Displays summary statistics (total events, successful logins,<br />
failed logins, password resets) for the last 7 days. Supports filtering by<br />
event type and severity, search, and CSV export.</p>
<h4>Recovery Mode</h4>
<p>Generate single-use recovery links that can disable a specific plugin or<br />
trigger a custom action — delivered via Slack, Telegram, or any configured<br />
webhook channel. Designed for emergency recovery when the site is inaccessible through normal means. The recovery URLs are sent in Slack and Telegram channels for security.</p>
<h4>Other Features</h4>
<ul>
<li>Dark mode for all admin screens.</li>
<li>CSV export on all list views (requests, errors, mails, hooks, etc.).</li>
<li>Screen Options on every screen (configure columns, items per page).</li>
<li>WP CLI compatible scaffolding for background operations.</li>
<li>Multisite aware (note: recovery mode has core multisite limitations).</li>
</ul>
<h3>Requirements & Compatibility</h3>
<ul>
<li>WordPress 6.0+ (tested up to 6.9)</li>
<li>PHP 7.4+ (compatible with PHP 8.0, 8.1, 8.2, 8.3, 8.4, 8.5)</li>
<li>MySQL 5.7+ / MariaDB 10.3+</li>
<li>Not intended as a primary multisite recovery tool (see FAQ)</li>
</ul>
<h3>Best Practices & Security Notes</h3>
<ul>
<li>Keep log files outside the webroot when possible, or restrict access via<br />
server rules (.htaccess / nginx) to prevent public exposure.</li>
<li>Use the built-in “Randomise Log Filename” feature when logs must stay in the<br />
webroot.</li>
<li>All plugin capabilities are restricted to <code>manage_options</code> (administrators)<br />
by default. The menu can optionally be restricted to admins only.</li>
<li>Sanitize and escape all output; nonces are enforced on all state-changing<br />
actions.</li>
<li>Secure SMTP credentials using TLS/STARTTLS; credentials are stored in the<br />
WordPress options table.</li>
<li>Set file permissions tightly (e.g., 600/640) and restrict ownership to the<br />
web server user.</li>
<li>Backup database and files before using bulk delete or table truncation.</li>
<li>Disable unused modules to reduce footprint and potential attack surface.</li>
<li>Disable or throttle high-frequency background polling on high-load sites.</li>
</ul>
<h3>Usage Notes & Performance</h3>
<ul>
<li>The Error Log viewer reads the last N lines (default 100, max configurable<br />
via Screen Options) to avoid full-file reads on GB-sized logs.</li>
<li>No pagination on error logs by design — pagination would force repeated<br />
expensive full-file reads.</li>
<li>The PHP Fatal Error Tracker uses its own DB table; apply a retention policy<br />
in Settings to avoid unbounded growth.</li>
<li>The Hooks Capture module adds minimal overhead per captured hook invocation;<br />
disable capturing on production when not actively debugging.</li>
<li>The URL Tracker records page visits in a custom table; configure retention<br />
or pause tracking on high-traffic sites.</li>
</ul>
<h3>Support & Notes</h3>
<ul>
<li>Secure log paths and consider randomising filenames in production.</li>
<li>Disable unused modules to reduce footprint and attack surface.</li>
<li>Recovery Mode has limitations on multisite — test before relying on it.</li>
<li>For bugs or feature requests, open an issue on the plugin page.</li>
</ul>
<p>Live preview and full details:<br />
https://wordpress.org/plugins/0-day-analytics/</p>
<p>Plugin website and documentation:<br />
https://0-day-analytics.com</p>


0 Day Analytics

All-in-one WordPress debug & operations toolkit: error log manager, PHP fatal tracker, cron & transient manager, mail logger, traffic analytic …

Performant Transients vs 0 Day Analytics