Report - Fatal Error Notify 1.4.3

Does Fatal Error Notify work with WordPress 5.8 and PHP 7.4.8? A smoke test was performed on 2021-07-23 03:38:39 UTC.

Summary

Errors

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

Performance

Memory usage: 12.7 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
PHP version	7.4.8
MySQL version	8.0.21
PHP memory limit	256M

Plugin Info

Last updated	2024-01-12T11:11:00+00:00
Active installs	7,000+
WordPress.org page	https://wordpress.org/plugins/fatal-error-notify/
Badges	Get badge code

Pages 3

Plugins ‹ Test site — WordPress

URL	/wp-admin/plugins.php?plugin_status=all&paged=1&s
Requested URL	/wp-admin/plugins.php?action=activate&plugin=fatal-error-notify%2Ffatal-error-notify.php&plugin_status=all&paged=1&s&_wpnonce=58f9745dc8
Aspect	after-activation
HTTP status	200
Load time	0.385 s
Memory usage	3.05 MiB
JS errors	None
Resource errors	None

Settings → Fatal Error Notify

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

Test site – Just another WordPress site

URL	/
Aspect	front-page
HTTP status	200
Load time	0.270 s
Memory usage	2.92 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.341 s	0.293 s	-0.048 s	3.08 MiB	3.09 MiB	+ 8.76 KiB
/wp-admin/edit.php	0.200 s	0.214 s	+0.014 s	3.11 MiB	3.18 MiB	+ 72.76 KiB
/wp-admin/post-new.php	1.141 s	1.220 s	+0.079 s	5.27 MiB	5.28 MiB	+ 13.12 KiB
/wp-admin/upload.php	0.592 s	0.369 s	-0.223 s	3.03 MiB	3.04 MiB	+ 7.63 KiB
/wp-admin/options-writing.php	0.175 s	0.143 s	-0.032 s	3.02 MiB	3.02 MiB	- 8.4 KiB
/wp-admin/media-new.php	0.251 s	0.207 s	-0.044 s	3.01 MiB	3.02 MiB	+ 7.8 KiB
/wp-admin/edit-tags.php?taxonomy=category	0.225 s	0.195 s	-0.030 s	3.04 MiB	3.05 MiB	+ 8.7 KiB
/wp-admin/post-new.php?post_type=page	0.998 s	1.059 s	+0.061 s	5.26 MiB	5.27 MiB	+ 8.7 KiB
/wp-admin/options-discussion.php	0.229 s	0.306 s	+0.077 s	3 MiB	3.01 MiB	+ 8.11 KiB
/wp-admin/edit-comments.php	0.254 s	0.248 s	-0.006 s	3.04 MiB	3.05 MiB	+ 7.61 KiB
/	0.287 s	0.290 s	+0.003 s	2.91 MiB	2.92 MiB	+ 4.92 KiB
Average	0.427 s	0.413 s	-0.014 s	3.43 MiB	3.45 MiB	+ 12.7 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

CSS

Language		%	Lines of code	Comment lines	Files
	PHP	83.7%	287	140	3
	CSS	12.2%	42	0	1
	JavaScript	4.1%	14	0	1
Total			343	140	5

PHP Code Analysis | More results »

Lines of code	306
Total complexity	61
Median class complexity	18.0
Median method complexity	1.0
Most complex class	Fatal_Error_Notify
Most complex function	Fatal_Error_Notify_Public::shutdown()

Classes	3
Methods	14
Functions	1

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.

No new entries found.

PHP Error Log 1 lines

[23-Jul-2021 03:38:55 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 5535