Report - Titan Anti-spam & Security 7.2.9

Does Titan Anti-spam & Security work with WordPress 5.9.3 and PHP 7.4.8? A smoke test was performed on 2022-04-05 22:02:41 UTC.

Summary

Errors

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

Performance

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

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

Environment

WordPress version	5.9.3
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=f79e7f0085
Aspect	after-activation
HTTP status	200
Load time	0.710 s
Memory usage	4.39 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.965 s
Memory usage	4.6 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.213 s
Memory usage	4.2 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.341 s
Memory usage	4.44 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.262 s
Memory usage	4.24 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.274 s
Memory usage	4.24 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.429 s
Memory usage	4.58 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.274 s
Memory usage	4.3 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.336 s
Memory usage	4.22 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.361 s
Memory usage	4.57 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.293 s
Memory usage	4.41 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.336 s
Memory usage	4.24 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.338 s
Memory usage	4.66 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.322 s
Memory usage	4.24 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.277 s
Memory usage	4.23 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.352 s
Memory usage	4.24 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.280 s
Memory usage	4.23 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.288 s
Memory usage	4.55 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.265 s
Memory usage	4.23 MiB
JS errors	None
Resource errors	None

Test site – Just another WordPress site

URL	/
Aspect	front-page
HTTP status	200
Load time	0.318 s
Memory usage	3.52 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.373 s	0.520 s	+0.147 s	3.37 MiB	4.32 MiB	+ 974.02 KiB
/wp-admin/edit.php	0.183 s	0.230 s	+0.047 s	3.4 MiB	4.35 MiB	+ 974.91 KiB
/wp-admin/post-new.php	1.000 s	1.465 s	+0.465 s	5.65 MiB	6.6 MiB	+ 967.59 KiB
/wp-admin/upload.php	0.394 s	0.435 s	+0.041 s	3.25 MiB	4.27 MiB	+ 1.02 MiB
/wp-admin/options-writing.php	0.291 s	0.204 s	-0.087 s	3.24 MiB	4.18 MiB	+ 963.89 KiB
/wp-admin/media-new.php	0.268 s	0.227 s	-0.041 s	3.23 MiB	4.25 MiB	+ 1.02 MiB
/wp-admin/edit-tags.php?taxonomy=category	0.201 s	0.348 s	+0.147 s	3.27 MiB	4.28 MiB	+ 1.02 MiB
/wp-admin/post-new.php?post_type=page	0.989 s	0.992 s	+0.003 s	5.65 MiB	6.59 MiB	+ 963.18 KiB
/wp-admin/options-discussion.php	0.221 s	0.298 s	+0.077 s	3.22 MiB	4.18 MiB	+ 980.52 KiB
/wp-admin/edit-comments.php	0.209 s	0.253 s	+0.044 s	3.27 MiB	4.29 MiB	+ 1.02 MiB
/	0.319 s	0.233 s	-0.086 s	3.4 MiB	3.52 MiB	+ 129.05 KiB
Average	0.404 s	0.473 s	+0.069 s	3.72 MiB	4.62 MiB	+ 921.36 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	56.8%	95,703	0	7
	PHP	16.0%	26,872	15,130	302
	JavaScript	14.3%	24,024	1,954	72
	CSS	9.9%	16,670	281	67
	LESS	1.8%	2,968	116	17
	PO File	1.2%	2,081	901	7
	Markdown	0.0%	72	0	3
	SVG	0.0%	6	0	1
Total			168,396	18,382	476

PHP Code Analysis | More results »

Lines of code	24,136
Total complexity	5,019
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	229
Methods	1,486
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` 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

[05-Apr-2022 22:02:59 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 5775
[05-Apr-2022 22:03:00 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 5775
[05-Apr-2022 22:03:01 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 5775
[05-Apr-2022 22:03:02 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 5775
[05-Apr-2022 22:03:02 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 5775
[05-Apr-2022 22:03:03 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 5775
[05-Apr-2022 22:03:04 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 5775
[05-Apr-2022 22:03:05 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 5775
[05-Apr-2022 22:03:05 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 5775
[05-Apr-2022 22:03:06 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 5775
[05-Apr-2022 22:03:07 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 5775
[05-Apr-2022 22:03:08 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 5775
[05-Apr-2022 22:03:08 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 5775
[05-Apr-2022 22:03:09 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 5775
[05-Apr-2022 22:03:10 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 5775
[05-Apr-2022 22:03:10 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 5775

Titan Anti-spam & Security 7.2.9

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