Report - Titan Anti-spam & Security 7.2.7

Does Titan Anti-spam & Security work with WordPress 5.8.1 and PHP 7.4.8? A smoke test was performed on 2021-09-09 05:29:17 UTC.

Summary

Errors

16	PHP notices
	No JavaScript exceptions
	All test pages loaded successfully
	No resource errors

Performance

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

Page speed impact: insignificant.
The plugin didn't make the site noticeably slower.

Environment

WordPress version	5.8.1
PHP version	7.4.8
MySQL version	8.0.21
PHP memory limit	256M

Plugin Info

Last updated	2023-03-24T05:05:00+00:00
Active installs	100,000+
WordPress.org page	https://wordpress.org/plugins/anti-spam/
Badges	Get badge code

Pages 20

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=c11d3f66d6
Aspect	after-activation
HTTP status	200
Load time	1.182 s
Memory usage	4.14 MiB
JS errors	None
Resource errors	None

Settings → Anti-spam

URL	/wp-admin/options-general.php?page=antispam-titan_security
Aspect	menu-item
HTTP status	200
Load time	0.383 s
Memory usage	4.31 MiB
JS errors	None
Resource errors	None

Setup master

URL	/wp-admin/admin.php?page=setup-titan_security
Aspect	menu-item
HTTP status	200
Load time	0.185 s
Memory usage	3.92 MiB
JS errors	None
Resource errors	None

Titan Anti-spam

URL	/wp-admin/admin.php?page=dashboard-titan_security
Aspect	menu-item
HTTP status	200
Load time	0.283 s
Memory usage	4.18 MiB
JS errors	None
Resource errors	None

Site Checker

URL	/wp-admin/admin.php?page=sitechecker-titan_security
Aspect	menu-item
HTTP status	200
Load time	0.227 s
Memory usage	3.97 MiB
JS errors	None
Resource errors	None

Error Log

URL	/wp-admin/admin.php?page=logs-titan_security
Aspect	menu-item
HTTP status	200
Load time	0.214 s
Memory usage	3.97 MiB
JS errors	None
Resource errors	None

Tweaks

URL	/wp-admin/admin.php?page=tweaks-titan_security
Aspect	menu-item
HTTP status	200
Load time	0.239 s
Memory usage	4.28 MiB
JS errors	None
Resource errors	None

Components

URL	/wp-admin/admin.php?page=components-titan_security
Aspect	menu-item
HTTP status	200
Load time	0.263 s
Memory usage	3.96 MiB
JS errors	None
Resource errors	None

License

URL	/wp-admin/admin.php?page=license-titan_security
Aspect	menu-item
HTTP status	200
Load time	0.300 s
Memory usage	3.95 MiB
JS errors	None
Resource errors	None

Settings

URL	/wp-admin/admin.php?page=plugin_settings-titan_security
Aspect	menu-item
HTTP status	200
Load time	0.291 s
Memory usage	4.27 MiB
JS errors	None
Resource errors	None

Audit

URL	/wp-admin/admin.php?page=check-titan_security
Aspect	menu-item
HTTP status	200
Load time	0.290 s
Memory usage	4.15 MiB
JS errors	None
Resource errors	None

Firewall

URL	/wp-admin/admin.php?page=firewall-titan_security
Aspect	menu-item
HTTP status	200
Load time	0.255 s
Memory usage	3.97 MiB
JS errors	None
Resource errors	None

Settings

URL	/wp-admin/admin.php?page=firewall-settings-titan_security
Aspect	menu-item
HTTP status	200
Load time	0.279 s
Memory usage	4.49 MiB
JS errors	None
Resource errors	None

Blocking

URL	/wp-admin/admin.php?page=firewall-blocking-titan_security
Aspect	menu-item
HTTP status	200
Load time	0.205 s
Memory usage	3.97 MiB
JS errors	None
Resource errors	None

Attacks log

URL	/wp-admin/admin.php?page=firewall-attack-log-titan_security
Aspect	menu-item
HTTP status	200
Load time	0.187 s
Memory usage	3.96 MiB
JS errors	None
Resource errors	None

Two-factor

URL	/wp-admin/admin.php?page=tfa_settings-titan_security
Aspect	menu-item
HTTP status	200
Load time	0.301 s
Memory usage	3.97 MiB
JS errors	None
Resource errors	None

Backup

URL	/wp-admin/admin.php?page=bm_settings-titan_security
Aspect	menu-item
HTTP status	200
Load time	0.215 s
Memory usage	3.96 MiB
JS errors	None
Resource errors	None

Limit login Attempts

URL	/wp-admin/admin.php?page=bruteforce-titan_security
Aspect	menu-item
HTTP status	200
Load time	0.336 s
Memory usage	4.25 MiB
JS errors	None
Resource errors	None

Login Attempts Log

URL	/wp-admin/admin.php?page=firewall-activity-log-titan_security
Aspect	menu-item
HTTP status	200
Load time	0.239 s
Memory usage	3.96 MiB
JS errors	None
Resource errors	None

Test site – Just another WordPress site

URL	/
Aspect	front-page
HTTP status	200
Load time	0.188 s
Memory usage	3.14 MiB
JS errors	None
Resource errors	None

Benchmark

URL	Load time			Memory usage
URL	Inactive	Active	Change	Inactive	Active	Change
/wp-admin/index.php	0.336 s	0.421 s	+0.085 s	3.08 MiB	3.99 MiB	+ 930.3 KiB
/wp-admin/edit.php	0.313 s	0.193 s	-0.120 s	3.11 MiB	4.09 MiB	+ 996.29 KiB
/wp-admin/post-new.php	2.287 s	1.048 s	-1.239 s	5.27 MiB	6.17 MiB	+ 924.49 KiB
/wp-admin/upload.php	1.078 s	0.434 s	-0.644 s	3.03 MiB	3.94 MiB	+ 933.24 KiB
/wp-admin/options-writing.php	0.137 s	0.152 s	+0.015 s	3.02 MiB	3.91 MiB	+ 912.29 KiB
/wp-admin/media-new.php	0.309 s	0.211 s	-0.098 s	3.01 MiB	3.92 MiB	+ 933.64 KiB
/wp-admin/edit-tags.php?taxonomy=category	0.165 s	0.197 s	+0.032 s	3.04 MiB	3.95 MiB	+ 932.81 KiB
/wp-admin/post-new.php?post_type=page	1.043 s	0.732 s	-0.311 s	5.26 MiB	6.16 MiB	+ 919.45 KiB
/wp-admin/options-discussion.php	0.300 s	0.372 s	+0.072 s	3 MiB	3.91 MiB	+ 928.8 KiB
/wp-admin/edit-comments.php	0.197 s	0.202 s	+0.005 s	3.04 MiB	3.95 MiB	+ 934.06 KiB
/	0.312 s	0.204 s	-0.108 s	2.91 MiB	3.14 MiB	+ 231.63 KiB
Average	0.589 s	0.379 s	-0.210 s	3.43 MiB	4.28 MiB	+ 870.64 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
	JSON	55.6%	95,703	0	7
	PHP	17.3%	29,690	17,384	323
	JavaScript	14.3%	24,510	3,010	111
	CSS	9.8%	16,858	622	101
	LESS	1.7%	3,006	121	18
	PO File	1.2%	2,142	911	8
	Markdown	0.0%	72	0	3
	SVG	0.0%	6	0	1
Total			171,987	22,048	572

PHP Code Analysis | More results »

Lines of code	32,020
Total complexity	6,754
Median class complexity	11.0
Median method complexity	2.0
Most complex class	WBCR\Titan\Bruteforce\Limit_Login_Attempts
Most complex function	WBCR\Titan\MalwareScanner\SignaturePool::scanFile()

Classes	307
Methods	2,020
Functions	80

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` 16

titan_bruteforce_allowed_retries
titan_bruteforce_blacklist_ips
titan_bruteforce_blacklist_usernames
titan_bruteforce_gdpr
titan_bruteforce_lockouts
titan_bruteforce_lockouts_total
titan_bruteforce_logged
titan_bruteforce_minutes_lockout
titan_bruteforce_set_default_options
titan_bruteforce_valid_duration
titan_bruteforce_whitelist_ips
titan_bruteforce_whitelist_usernames
titan_last_check_update
titan_last_check_update_time
titan_plugin_activated
titan_plugin_version

PHP Error Log 16 lines

[09-Sep-2021 05:29:35 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 5663
[09-Sep-2021 05:29:36 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 5663
[09-Sep-2021 05:29:37 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 5663
[09-Sep-2021 05:29:37 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 5663
[09-Sep-2021 05:29:38 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 5663
[09-Sep-2021 05:29:38 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 5663
[09-Sep-2021 05:29:39 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 5663
[09-Sep-2021 05:29:40 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 5663
[09-Sep-2021 05:29: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 5663
[09-Sep-2021 05:29: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 5663
[09-Sep-2021 05:29:42 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 5663
[09-Sep-2021 05:29: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 5663
[09-Sep-2021 05:29: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 5663
[09-Sep-2021 05:29: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 5663
[09-Sep-2021 05:29: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 5663
[09-Sep-2021 05:29: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 5663

Titan Anti-spam & Security 7.2.7

Summary

Pages 20

Setup ‹ Test site — WordPress

Settings → Anti-spam

Setup master

Titan Anti-spam

Site Checker

Error Log

Tweaks

Components

License

Settings

Audit

Firewall

Settings

Blocking

Attacks log

Two-factor

Backup

Limit login Attempts

Login Attempts Log

Test site – Just another WordPress site

Benchmark

Code Statistics

PHP Code Analysis | More results »

Additions

Options wp_options 16

PHP Error Log 16 lines

Options `wp_options` 16