Forge12 Interactive GmbH

F12 Profiler analyzes your WordPress site comprehensively and delivers concrete, prioritized recommendations to improve load times. The plugin combines server diagnostics, asset analysis, database optimization, and plugin impact assessment in a modern, clean interface.
<h4>Features</h4>
Analysis & Diagnostics
<ul>
<li>Server analysis (PHP, MySQL, OPcache, web server, SSL, HTTP/2, compression)</li>
<li>Automatic site crawler with load time measurement (desktop & mobile)</li>
<li>Asset analysis (CSS, JS, images) with optimization potential</li>
<li>OPcache status & configuration recommendations</li>
<li>PHP profiler (runtime, queries, hooks, plugin ranking, culprit analysis)</li>
<li>Plugin impact analysis (assets, hooks, queries per plugin)</li>
<li>PageSpeed Insights integration (Lighthouse Scores + Core Web Vitals + CrUX)</li>
<li>Performance score with 6 weighted categories (A-F grades, trend delta)</li>
<li>Recommendation engine with automatic optimization suggestions</li>
</ul>
Optimization Tools
<ul>
<li>Lazy Loading (images and iframes)</li>
<li>Font Display Optimization (font-display: swap/optional/fallback/block)</li>
<li>Script Defer Manager (automatic defer for scripts with exclusion list)</li>
<li>Auto Image Dimensions (prevents Layout Shifts / CLS)</li>
<li>HTML Minification (whitespace, comments, empty attributes)</li>
<li>CSS/JS Minification (file-based cache)</li>
<li>WordPress Bloat Removal (emojis, embeds, Dashicons, jQuery Migrate, XML-RPC, Heartbeat, and more)</li>
<li>Browser Cache (.htaccess-based)</li>
<li>DNS Prefetch & Preconnect (domain detection from asset scan)</li>
<li>Database Analysis (8 categories with detail view)</li>
<li>Autoload Manager (granular wp_options management)</li>
<li>Background Asset Scanner with conflict detection</li>
<li>File-based Page Cache with TTL and URL exclusion (Pro)</li>
<li>CSS/JS Asset Manager – disable, defer, async per page or globally (Pro)</li>
<li>Conditional Loading – shortcode, block, regex, archive, login status, post type, plugin (Pro)</li>
<li>Smart auto-suggestions with source-based plugin detection after full scan (Pro)</li>
<li>Asset Preload Manager – Link headers for critical assets (Pro)</li>
<li>Critical CSS Generator & Applier – above-the-fold CSS per template (Pro)</li>
<li>Unused CSS Removal – per page template, safelist, regex safelist (Pro)</li>
<li>WebP Image Conversion with batch queue and backup (Pro)</li>
<li>LQIP Image Placeholders – 20px blur-up previews with IntersectionObserver (Pro)</li>
<li>Preload Key Requests – LCP images, fonts, critical resources (Pro)</li>
<li>Script Delay – delays third-party JS until first user interaction (Pro)</li>
<li>Local Google Fonts – GDPR-compliant WOFF2 self-hosting (Pro)</li>
<li>YouTube/Vimeo Facade – thumbnail + play button instead of iframe (Pro)</li>
<li>Database Cleanup – one-click per category or bulk action (Pro)</li>
<li>Redis Object Cache Management – drop-in installation/removal (Pro)</li>
<li>Scheduled Crawls & Cleanups via WP-Cron (Pro)</li>
<li>Performance Budgets with email/webhook notifications (Pro)</li>
<li>Settings Import/Export as JSON (Pro)</li>
<li>One-Click Optimizer – automated optimization with backup & restore (Pro)</li>
<li>License Management with activation/deactivation (Pro)</li>
</ul>
User Interface
<ul>
<li>Modern iOS-style design system</li>
<li>React 18 + TypeScript SPA</li>
<li>30+ pages/tools with dedicated configuration</li>
<li>Context-sensitive info sections on all pages</li>
<li>Pro features visible with lock icon and upgrade prompt</li>
</ul>
<a href="https://www.forge12.com/f12-profiler-pro/" rel="nofollow ugc">Get F12 Profiler Pro</a>
<h4>System Requirements</h4>
<ul>
<li>WordPress 6.0 or higher</li>
<li>PHP 8.0 or higher</li>
<li>MySQL 5.7 / MariaDB 10.3 or higher</li>
</ul>

F12 Profiler

Excellent! After P3 doesn’t work with PHP7+ anymore, F12 seems finally the one stepping in to fill that gap.

Update [18-Jun-19]. After some small contributions of mine to the dev efforts, the plugin developer has decided to add me to the team, long after this review was written.

Finally an alternative to P3

Comprehensive WordPress performance analysis with crawling, load time measurement, server diagnostics, and integrated optimization tools. Free.

Brian Fegter

Chris Dillon

Chris Wallace

<blockquote>
This plugin is up for adoption.
</blockquote>
Kint Debugger is a simple wrapper for <a href="https://github.com/raveren/kint" rel="nofollow ugc">Kint</a>, a debugging tool to output information about variables and traces in a styled, collapsible format that makes understanding deep arrays and objects easier.
No more adding PRE tags before print_r or var_dump!
Kint Debugger works well with the <a href="https://wordpress.org/plugins/debug-bar/" rel="ugc">Debug Bar</a> plugin by creating its own panel to display your debug results.
<h4>Basic Usage</h4>
<pre><code><?php d( $var ); ?>
</code></pre>
Examples:
<pre><code><?php
 global $post;
 $term_list = wp_get_post_terms( $post->ID, 'my_taxonomy', array( 'fields' => 'all' ) );
 d( $term_list );
?>
</code></pre>
Kint Debugger also provides some helper functions for dumping variables that are frequently needed.
<ul>
<li><code>dump_wp_query()</code></li>
<li><code>dump_wp()</code></li>
<li><code>dump_post()</code></li>
<li><code>dump_this( $var, $inline = false )</code> – explained below</li>
</ul>
Examples:
<pre><code><?php dump_post(); ?>

<?php add_action( 'wp_head', 'dump_post' ); ?>
</code></pre>
Obviously, if this plugin is not active, calls to the helper functions will cause errors.
<h4>Your Own Functions</h4>
If you are dumping the same information in different places, consider writing your own helper functions in your theme’s functions file or an mu-plugin. For example:
<pre><code><?php
function my_dump_terms() {
 global $post;
 $term_list = wp_get_post_terms( $post->ID, 'my_taxonomy', array( 'fields' => 'all' ) );
 d( $term_list );
}
?>
</code></pre>
Then at strategic points in your theme or plugin:
<pre><code><?php my_dump_terms(); ?>
</code></pre>
<h4>With Debug Bar</h4>
By default, when <a href="https://wordpress.org/plugins/debug-bar/" rel="ugc">Debug Bar</a> is installed and active, Kint Debugger will send d() output to its Debug Bar panel.
To print debug output inline instead, as if Debug Bar was not active, declare the constant KINT_TO_DEBUG_BAR in your config.php (or really anywhere before your d() call):
<pre><code>define( 'KINT_TO_DEBUG_BAR', false );
</code></pre>
Or to print a specific dump inline, use a helper function with the parameter <code>$inline</code>. The generic <code>dump_this()</code> takes <code>$inline</code> as the second parameter.
Examples:
<pre><code><?php dump_post( true ); ?>

<?php
 global $post;
 $term_list = wp_get_post_terms( $post->ID, 'my_taxonomy', array( 'fields' => 'all' ) );
 dump_this( $term_list , true );
?>
</code></pre>
Kint Debugger overrides Kint’s d() function in order to buffer its output for Debug Bar. If you already have a modified d() function, you need to prevent the override in one of two ways.
<ol>
<li>Move your modified d() function to an mu-plugin. Kint Debugger checks if the function exists before declaring it so putting yours in an mu-plugin is the only way to ensure it exists first.</li>
<li>Declare KINT_TO_DEBUG_BAR as described above.</li>
</ol>
<h4>Restricting Output</h4>
To restrict visibility, use the <code>kint_debug_display</code> filter. For example, to prevent non-admins from seeing the debug output:
<pre><code>add_filter( 'kint_debug_display', function( $allow ) { return is_super_admin(); } );
</code></pre>
<h4>Try these plugins too</h4>
<ul>
<li><a href="https://wordpress.org/plugins/what-the-file/" rel="ugc">What The File</a> – Identify template files without fail.</li>
<li><a href="https://wordpress.org/plugins/debug-this/" rel="ugc">Debug This</a> – Peek under the hood with sixty debugging reports just one click away.</li>
</ul>

Kint Debugger

Dump variables and traces in an organized and interactive display. Integrates seamlessly with Debug Bar.

F12 Profiler vs Kint Debugger