Titan Anti-spam & Security 7.2.5

Does Titan Anti-spam & Security work with WordPress 5.7 and PHP 7.4.8? A smoke test was performed on .

Summary

Errors
15PHP notices
No JavaScript exceptions
All test pages loaded successfully
No resource errors
Performance

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

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

Environment
WordPress version5.7
PHP version7.4.8
MySQL version8.0.21
PHP memory limit256M
Plugin Info
Last updated
Active installs 100,000+
WordPress.org page https://wordpress.org/plugins/anti-spam/
Badges

WordPress compatibility badge PHP compatibility badge

Get badge code

Pages 19

Setup ‹ Test site — WordPress

Page screenshot: Setup ‹ Test site — WordPress
URL /wp-admin/admin.php?page=setup-titan_security&wtitan_setup_page_viewed=1
Requested URL /wp-admin/plugins.php?action=activate&plugin=anti-spam%2Fanti-spam.php&plugin_status=all&paged=1&s&_wpnonce=93a0f3c765
Aspect after-activation
HTTP status 200
Load time 0.982 s
Memory usage 3.82 MiB
JS errors None
Resource errors None

Settings → Anti-spam

Page screenshot: Settings → Anti-spam
URL /wp-admin/options-general.php?page=antispam-titan_security
Aspect menu-item
HTTP status 200
Load time 1.377 s
Memory usage 4.03 MiB
JS errors None
Resource errors None

Setup master

Page screenshot: Setup master
URL /wp-admin/admin.php?page=setup-titan_security
Aspect menu-item
HTTP status 200
Load time 0.228 s
Memory usage 3.6 MiB
JS errors None
Resource errors None

Titan Anti-spam

Page screenshot: Titan Anti-spam
URL /wp-admin/admin.php?page=dashboard-titan_security
Aspect menu-item
HTTP status 200
Load time 0.353 s
Memory usage 3.86 MiB
JS errors None
Resource errors None

Site Checker

Page screenshot: Site Checker
URL /wp-admin/admin.php?page=sitechecker-titan_security
Aspect menu-item
HTTP status 200
Load time 0.346 s
Memory usage 3.71 MiB
JS errors None
Resource errors None

Error Log

Page screenshot: Error Log
URL /wp-admin/admin.php?page=logs-titan_security
Aspect menu-item
HTTP status 200
Load time 0.247 s
Memory usage 3.7 MiB
JS errors None
Resource errors None

Tweaks

Page screenshot: Tweaks
URL /wp-admin/admin.php?page=tweaks-titan_security
Aspect menu-item
HTTP status 200
Load time 0.294 s
Memory usage 4 MiB
JS errors None
Resource errors None

Components

Page screenshot: Components
URL /wp-admin/admin.php?page=components-titan_security
Aspect menu-item
HTTP status 200
Load time 0.345 s
Memory usage 3.7 MiB
JS errors None
Resource errors None

License

Page screenshot: License
URL /wp-admin/admin.php?page=license-titan_security
Aspect menu-item
HTTP status 200
Load time 0.439 s
Memory usage 3.69 MiB
JS errors None
Resource errors None

Settings

Page screenshot: Settings
URL /wp-admin/admin.php?page=plugin_settings-titan_security
Aspect menu-item
HTTP status 200
Load time 0.345 s
Memory usage 3.99 MiB
JS errors None
Resource errors None

Audit

Page screenshot: Audit
URL /wp-admin/admin.php?page=check-titan_security
Aspect menu-item
HTTP status 200
Load time 0.330 s
Memory usage 3.83 MiB
JS errors None
Resource errors None

Firewall

Page screenshot: Firewall
URL /wp-admin/admin.php?page=firewall-titan_security
Aspect menu-item
HTTP status 200
Load time 0.343 s
Memory usage 3.71 MiB
JS errors None
Resource errors None

Settings

Page screenshot: Settings
URL /wp-admin/admin.php?page=firewall-settings-titan_security
Aspect menu-item
HTTP status 200
Load time 0.405 s
Memory usage 4.16 MiB
JS errors None
Resource errors None

Blocking

Page screenshot: Blocking
URL /wp-admin/admin.php?page=firewall-blocking-titan_security
Aspect menu-item
HTTP status 200
Load time 0.549 s
Memory usage 3.7 MiB
JS errors None
Resource errors None

Attacks log

Page screenshot: Attacks log
URL /wp-admin/admin.php?page=firewall-attack-log-titan_security
Aspect menu-item
HTTP status 200
Load time 0.226 s
Memory usage 3.7 MiB
JS errors None
Resource errors None

Two-factor

Page screenshot: Two-factor
URL /wp-admin/admin.php?page=tfa_settings-titan_security
Aspect menu-item
HTTP status 200
Load time 0.340 s
Memory usage 3.71 MiB
JS errors None
Resource errors None

Limit login Attempts

Page screenshot: Limit login Attempts
URL /wp-admin/admin.php?page=bruteforce-titan_security
Aspect menu-item
HTTP status 200
Load time 0.296 s
Memory usage 3.97 MiB
JS errors None
Resource errors None

Login Attempts Log

Page screenshot: Login Attempts Log
URL /wp-admin/admin.php?page=firewall-activity-log-titan_security
Aspect menu-item
HTTP status 200
Load time 0.323 s
Memory usage 3.7 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.244 s
Memory usage 2.82 MiB
JS errors None
Resource errors None

Benchmark

URL Load time Memory usage
Inactive Active Change Inactive Active Change
/wp-admin/index.php0.308 s0.518 s+0.210 s2.82 MiB3.74 MiB+ 941.56 KiB
/wp-admin/edit.php0.191 s0.391 s+0.200 s2.86 MiB3.77 MiB+ 930.35 KiB
/wp-admin/post-new.php1.007 s1.233 s+0.226 s5.02 MiB5.99 MiB+ 991.76 KiB
/wp-admin/upload.php0.524 s0.325 s-0.199 s2.7 MiB3.62 MiB+ 944.18 KiB
/wp-admin/options-writing.php0.186 s0.181 s-0.005 s2.71 MiB3.66 MiB+ 971.56 KiB
/wp-admin/media-new.php0.206 s0.215 s+0.009 s2.67 MiB3.6 MiB+ 944.63 KiB
/wp-admin/edit-tags.php?taxonomy=category0.243 s0.231 s-0.012 s2.77 MiB3.69 MiB+ 946.48 KiB
/wp-admin/post-new.php?post_type=page0.929 s1.219 s+0.290 s5.01 MiB5.97 MiB+ 986.72 KiB
/wp-admin/options-discussion.php0.373 s0.415 s+0.042 s2.67 MiB3.59 MiB+ 940.1 KiB
/wp-admin/edit-comments.php0.254 s0.280 s+0.026 s2.78 MiB3.7 MiB+ 945.37 KiB
/0.286 s0.240 s-0.046 s2.71 MiB2.82 MiB+ 114.6 KiB
Average 0.410 s0.477 s+0.067 s3.16 MiB4.01 MiB+ 877.94 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.

JSON
PHP
JavaScript
CSS
Language % Lines of code Comment lines Files
JSON57.3%95,70307
PHP16.0%26,63415,099301
JavaScript14.4%24,0112,22072
CSS9.6%16,05731566
LESS1.4%2,3518616
PO File1.2%2,0819017
Markdown0.0%7203
SVG0.0%601
Total 166,915 18,621 473

PHP Code Analysis | More results »

Lines of code 23,893
Total complexity 4,973
Median class complexity 10.0
Median method complexity 2.0
Most complex class WBCR\Titan\Bruteforce\Limit_Login_Attempts
Most complex function WBCR\Titan\MalwareScanner\SignaturePool::scanFile()
Classes 228
Methods 1,478
Functions 70

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 17

PHP Error Log 15 lines

[09-Mar-2021 22:57:41 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5313
[09-Mar-2021 22:57:43 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5313
[09-Mar-2021 22:57:44 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5313
[09-Mar-2021 22:57:45 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5313
[09-Mar-2021 22:57:45 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5313
[09-Mar-2021 22:57:46 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5313
[09-Mar-2021 22:57:47 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5313
[09-Mar-2021 22:57:48 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5313
[09-Mar-2021 22:57:49 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5313
[09-Mar-2021 22:57:50 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5313
[09-Mar-2021 22:57:51 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5313
[09-Mar-2021 22:57:52 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5313
[09-Mar-2021 22:57:52 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5313
[09-Mar-2021 22:57:53 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5313
[09-Mar-2021 22:57:53 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5313
See also: All tests for this plugin, How to Hide Titan Anti-spam & Security Admin Menus