WP fail2ban 5.3.4

Does WP fail2ban work with WordPress 6.7 and PHP 8.1.12? A smoke test was performed on .

Summary

Errors
No PHP errors, warnings or notices
No JavaScript exceptions
All test pages loaded successfully
No resource errors
Looks good! No problems were detected.
Performance

Memory usage: 420.11 KiB
The average PHP memory usage increased by this amount after activating by the plugin.

Page speed impact: 0.026 seconds
The average page load time increased by this amount after activating the plugin.

Environment
WordPress version6.7
PHP version8.1.12
MySQL version10.6.10
PHP memory limit512M
Plugin Info
Last updated
Active installs 70,000+
WordPress.org page https://wordpress.org/plugins/wp-fail2ban/
Badges

WordPress compatibility badge PHP compatibility badge

Get badge code

Pages 11

WP fail2ban ‹ Test site — WordPress

Page screenshot: WP fail2ban ‹ Test site — WordPress
URL /wp-admin/admin.php?page=wp-fail2ban-menu
Requested URL /wp-admin/plugins.php?action=activate&plugin=wp-fail2ban%2Fwp-fail2ban.php&plugin_status=all&paged=1&s&_wpnonce=8d2a9bdd69
Aspect after-activation
HTTP status 200
Load time 0.444 s
Memory usage 3.81 MiB
JS errors None
Resource errors None

WP fail2ban

Page screenshot: WP fail2ban
URL /wp-admin/admin.php?page=wp-fail2ban-menu
Aspect menu-item
HTTP status 200
Load time 0.181 s
Memory usage 3.68 MiB
JS errors None
Resource errors None

WP fail2ban → Settings

Page screenshot: WP fail2ban → Settings
URL /wp-admin/admin.php?page=wpf2b-settings
Aspect menu-item
HTTP status 200
Load time 0.173 s
Memory usage 3.72 MiB
JS errors None
Resource errors None

WP fail2ban → Settings → syslog

Page screenshot: WP fail2ban → Settings → syslog
URL /wp-admin/admin.php?page=wpf2b-settings&tab=syslog
Aspect menu-item-tab
HTTP status 200
Load time 0.145 s
Memory usage 3.72 MiB
JS errors None
Resource errors None

WP fail2ban → Settings → Block

Page screenshot: WP fail2ban → Settings → Block
URL /wp-admin/admin.php?page=wpf2b-settings&tab=block
Aspect menu-item-tab
HTTP status 200
Load time 0.136 s
Memory usage 3.72 MiB
JS errors None
Resource errors None

WP fail2ban → Settings → Remote IPs

Page screenshot: WP fail2ban → Settings → Remote IPs
URL /wp-admin/admin.php?page=wpf2b-settings&tab=remote-ips
Aspect menu-item-tab
HTTP status 200
Load time 0.146 s
Memory usage 3.72 MiB
JS errors None
Resource errors None

WP fail2ban → Settings → Plugins

Page screenshot: WP fail2ban → Settings → Plugins
URL /wp-admin/admin.php?page=wpf2b-settings&tab=plugins
Aspect menu-item-tab
HTTP status 200
Load time 0.148 s
Memory usage 3.72 MiB
JS errors None
Resource errors None

WP fail2ban → Add-Ons

Page screenshot: WP fail2ban → Add-Ons
URL /wp-admin/admin.php?page=wp-fail2ban-menu-addons
Aspect menu-item
HTTP status 200
Load time 0.804 s
Memory usage 3.81 MiB
JS errors None
Resource errors None

WP fail2ban → Upgrade  ➤

Page screenshot: WP fail2ban → Upgrade  ➤
URL /wp-admin/admin.php?page=wp-fail2ban-menu-pricing
Aspect menu-item
HTTP status 200
Load time 0.269 s
Memory usage 3.76 MiB
JS errors None
Resource errors None

Test site – Just another WordPress site

Page screenshot: Test site – Just another WordPress site
URL /
Aspect front-page
HTTP status 200
Load time 0.180 s
Memory usage 3.54 MiB
JS errors None
Resource errors None

Dashboard ‹ Test site — WordPress

Page screenshot: Dashboard ‹ Test site — WordPress
URL /wp-admin/index.php
Aspect new-meta-boxes
HTTP status 200
Load time 0.293 s
Memory usage 3.98 MiB
JS errors None
Resource errors None

Benchmark

URL Load time Memory usage
Inactive Active Change Inactive Active Change
/wp-admin/index.php0.281 s0.293 s+0.012 s3.48 MiB3.98 MiB+ 515.45 KiB
/wp-admin/edit.php0.183 s0.192 s+0.009 s3.54 MiB4 MiB+ 473.56 KiB
/wp-admin/post-new.php0.711 s0.977 s+0.266 s5.92 MiB6.37 MiB+ 455.68 KiB
/wp-admin/upload.php0.503 s0.503 s+0.000 s3.49 MiB3.92 MiB+ 435.07 KiB
/wp-admin/options-writing.php0.208 s0.171 s-0.037 s3.47 MiB3.9 MiB+ 439.12 KiB
/wp-admin/media-new.php0.244 s0.233 s-0.011 s3.46 MiB3.9 MiB+ 447.31 KiB
/wp-admin/edit-tags.php?taxonomy=category0.174 s0.175 s+0.001 s3.47 MiB3.92 MiB+ 452.98 KiB
/wp-admin/post-new.php?post_type=page0.563 s0.562 s-0.001 s5.92 MiB6.35 MiB+ 447.77 KiB
/wp-admin/options-discussion.php0.272 s0.418 s+0.146 s3.47 MiB3.9 MiB+ 435.62 KiB
/wp-admin/edit-comments.php0.194 s0.199 s+0.005 s3.49 MiB3.94 MiB+ 452.48 KiB
/0.273 s0.172 s-0.101 s3.47 MiB3.54 MiB+ 66.13 KiB
Average 0.328 s0.354 s+0.026 s3.93 MiB4.34 MiB+ 420.11 KiB

Code Statistics

Note: Third-party libraries and minified JS/CSS files are excluded from these statistics where possible, so the numbers you see here may be lower than those reported by other tools.

PHP
Language % Lines of code Comment lines Files
PHP98.7%4,6373,32637
JavaScript0.6%2801
Markdown0.6%2801
CSS0.0%202
SVG0.0%101
Total 4,696 3,326 42

PHP Code Analysis | More results »

Lines of code 3,753
Total complexity 638
Median class complexity 11.0
Median method complexity 1.0
Most complex class org\lecklider\charles\wordpress\wp_fail2ban\SiteHealth
Most complex function plugins_loaded()
Classes 14
Methods 149
Functions 79

Additions

Things that the plugin adds to the site. This section is not intended to be comprehensive. The test tool only looks for a few specific types of added content.

Options wp_options 4

Meta Boxes

{
    "dashboard": {
        "wp_fail2ban_last_messages": {
            "title": "[WPf2b] Last 5 Messages",
            "context": "normal"
        }
    }
}

PHP Error Log

The log file is empty.

See also: All tests for this plugin, How to Hide WP fail2ban Admin Menus and Widgets