Does WP fail2ban work with WordPress 6.7 and PHP 8.1.12? A smoke test was performed on .
No PHP errors, warnings or notices | |
No JavaScript exceptions | |
All test pages loaded successfully | |
No resource errors | |
Looks good! No problems were detected. |
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.
WordPress version | 6.7 |
---|---|
PHP version | 8.1.12 |
MySQL version | 10.6.10 |
PHP memory limit | 512M |
Last updated | |
---|---|
Active installs | 70,000+ |
WordPress.org page | https://wordpress.org/plugins/wp-fail2ban/ |
Badges |
Get badge code |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
URL | / |
---|---|
Aspect | front-page |
HTTP status | 200 |
Load time | 0.180 s |
Memory usage | 3.54 MiB |
JS errors | None |
Resource errors | None |
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 |
URL | Load time | Memory usage | ||||
---|---|---|---|---|---|---|
Inactive | Active | Change | Inactive | Active | Change | |
/wp-admin/index.php | 0.281 s | 0.293 s | +0.012 s | 3.48 MiB | 3.98 MiB | + 515.45 KiB |
/wp-admin/edit.php | 0.183 s | 0.192 s | +0.009 s | 3.54 MiB | 4 MiB | + 473.56 KiB |
/wp-admin/post-new.php | 0.711 s | 0.977 s | +0.266 s | 5.92 MiB | 6.37 MiB | + 455.68 KiB |
/wp-admin/upload.php | 0.503 s | 0.503 s | +0.000 s | 3.49 MiB | 3.92 MiB | + 435.07 KiB |
/wp-admin/options-writing.php | 0.208 s | 0.171 s | -0.037 s | 3.47 MiB | 3.9 MiB | + 439.12 KiB |
/wp-admin/media-new.php | 0.244 s | 0.233 s | -0.011 s | 3.46 MiB | 3.9 MiB | + 447.31 KiB |
/wp-admin/edit-tags.php?taxonomy=category | 0.174 s | 0.175 s | +0.001 s | 3.47 MiB | 3.92 MiB | + 452.98 KiB |
/wp-admin/post-new.php?post_type=page | 0.563 s | 0.562 s | -0.001 s | 5.92 MiB | 6.35 MiB | + 447.77 KiB |
/wp-admin/options-discussion.php | 0.272 s | 0.418 s | +0.146 s | 3.47 MiB | 3.9 MiB | + 435.62 KiB |
/wp-admin/edit-comments.php | 0.194 s | 0.199 s | +0.005 s | 3.49 MiB | 3.94 MiB | + 452.48 KiB |
/ | 0.273 s | 0.172 s | -0.101 s | 3.47 MiB | 3.54 MiB | + 66.13 KiB |
Average | 0.328 s | 0.354 s | +0.026 s | 3.93 MiB | 4.34 MiB | + 420.11 KiB |
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.
Language | % | Lines of code | Comment lines | Files | |
---|---|---|---|---|---|
PHP | 98.7% | 4,637 | 3,326 | 37 | |
JavaScript | 0.6% | 28 | 0 | 1 | |
Markdown | 0.6% | 28 | 0 | 1 | |
CSS | 0.0% | 2 | 0 | 2 | |
SVG | 0.0% | 1 | 0 | 1 | |
Total | 4,696 | 3,326 | 42 |
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 |
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.
wp_options
4{
"dashboard": {
"wp_fail2ban_last_messages": {
"title": "[WPf2b] Last 5 Messages",
"context": "normal"
}
}
}
The log file is empty.