Report - WebFacing™ – Storage, resource usage and errors in cPanel® 3.2.1

Does "WebFacing - Disk, resource usage and errors from cPanel® on your Dashboard & in Site Health" work with WordPress 6.0.2 and PHP 7.4.8? A smoke test was performed on 2022-09-05 07:27:53 UTC.

Summary

Errors

3	PHP fatal errors
	No JavaScript exceptions
	All test pages loaded successfully
	No resource errors

Performance

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

Plugin Info

Last updated	2024-05-14T14:36:00+00:00
Active installs	60+
WordPress.org page	https://wordpress.org/plugins/wf-cpanel-right-now-site-health/
Badges	Get badge code

Pages 2

Plugins ‹ Test site — WordPress

URL	/wp-admin/plugins.php?plugin_status=all&paged=1&s
Requested URL	/wp-admin/plugins.php?action=activate&plugin=wf-cpanel-right-now-site-health%2Findex.php&plugin_status=all&paged=1&s&_wpnonce=a0c55575f2
Aspect	after-activation
HTTP status	200
Load time	0.413 s
Memory usage	3.75 MiB
JS errors	None
Resource errors	None

Test site – Just another WordPress site

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

Benchmark

URL	Load time			Memory usage
URL	Inactive	Active	Change	Inactive	Active	Change
/wp-admin/edit.php	0.181 s	0.194 s	+0.013 s	3.76 MiB	3.82 MiB	+ 60.9 KiB
/wp-admin/post-new.php	0.971 s	1.201 s	+0.230 s	5.55 MiB	5.62 MiB	+ 69.26 KiB
/wp-admin/upload.php	0.430 s	0.325 s	-0.105 s	3.69 MiB	3.74 MiB	+ 59.77 KiB
/wp-admin/options-writing.php	0.159 s	0.146 s	-0.013 s	3.62 MiB	3.72 MiB	+ 103.67 KiB
/wp-admin/media-new.php	0.393 s	0.190 s	-0.203 s	3.66 MiB	3.72 MiB	+ 59.94 KiB
/wp-admin/edit-tags.php?taxonomy=category	0.187 s	0.184 s	-0.003 s	3.69 MiB	3.75 MiB	+ 60.84 KiB
/wp-admin/post-new.php?post_type=page	0.866 s	0.918 s	+0.052 s	5.54 MiB	5.6 MiB	+ 60.84 KiB
/wp-admin/options-discussion.php	0.209 s	0.317 s	+0.108 s	3.6 MiB	3.72 MiB	+ 124.25 KiB
/wp-admin/edit-comments.php	0.209 s	0.222 s	+0.013 s	3.7 MiB	3.75 MiB	+ 59.75 KiB
/	0.299 s	0.217 s	-0.082 s	3.6 MiB	3.59 MiB	- 17.02 KiB
Average	0.390 s	0.391 s	+0.001 s	4.04 MiB	4.1 MiB	+ 64.22 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

Language		%	Lines of code	Comment lines	Files
	PHP	96.7%	2,082	121	9
	JavaScript	3.3%	71	0	1
Total			2,153	121	10

PHP Code Analysis | More results »

Lines of code	2,062
Total complexity	563
Median class complexity	78.5
Median method complexity	2.0
Most complex class	WebFacing\cPanel\Health
Most complex function	WebFacing\cPanel\Health::admin()

Classes	4
Methods	53
Functions	16

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 27 lines

[05-Sep-2022 07:28:09 UTC] PHP Fatal error:  Uncaught TypeError: json_decode() expects parameter 1 to be string, null given in /wp-content/plugins/wf-cpanel-right-now-site-health/includes/Main.php:323
Stack trace:
#0 /wp-content/plugins/wf-cpanel-right-now-site-health/includes/Main.php(323): json_decode()
#1 /wp-content/plugins/wf-cpanel-right-now-site-health/includes/Main.php(499): WebFacing\cPanel\Main::cpanel_uapi_result()
#2 /wp-content/plugins/wf-cpanel-right-now-site-health/includes/Main.php(227): WebFacing\cPanel\Main::cpanel_version()
#3 /wp-content/plugins/wf-cpanel-right-now-site-health/includes/Main.php(178): WebFacing\cPanel\Main::init_data()
#4 /wp-includes/class-wp-hook.php(307): WebFacing\cPanel\Main::WebFacing\cPanel\{closure}()
#5 /wp-includes/class-wp-hook.php(331): WP_Hook->apply_filters()
#6 /opt/bit in /wp-content/plugins/wf-cpanel-right-now-site-health/includes/Main.php on line 323
[05-Sep-2022 07:28:10 UTC] PHP Fatal error:  Uncaught TypeError: json_decode() expects parameter 1 to be string, null given in /wp-content/plugins/wf-cpanel-right-now-site-health/includes/Main.php:323
Stack trace:
#0 /wp-content/plugins/wf-cpanel-right-now-site-health/includes/Main.php(323): json_decode()
#1 /wp-content/plugins/wf-cpanel-right-now-site-health/includes/Main.php(499): WebFacing\cPanel\Main::cpanel_uapi_result()
#2 /wp-content/plugins/wf-cpanel-right-now-site-health/includes/Main.php(227): WebFacing\cPanel\Main::cpanel_version()
#3 /wp-content/plugins/wf-cpanel-right-now-site-health/includes/Main.php(178): WebFacing\cPanel\Main::init_data()
#4 /wp-includes/class-wp-hook.php(307): WebFacing\cPanel\Main::WebFacing\cPanel\{closure}()
#5 /wp-includes/class-wp-hook.php(331): WP_Hook->apply_filters()
#6 /opt/bit in /wp-content/plugins/wf-cpanel-right-now-site-health/includes/Main.php on line 323
[05-Sep-2022 07:28:17 UTC] PHP Fatal error:  Uncaught TypeError: json_decode() expects parameter 1 to be string, null given in /wp-content/plugins/wf-cpanel-right-now-site-health/includes/Main.php:323
Stack trace:
#0 /wp-content/plugins/wf-cpanel-right-now-site-health/includes/Main.php(323): json_decode()
#1 /wp-content/plugins/wf-cpanel-right-now-site-health/includes/Main.php(499): WebFacing\cPanel\Main::cpanel_uapi_result()
#2 /wp-content/plugins/wf-cpanel-right-now-site-health/includes/Main.php(227): WebFacing\cPanel\Main::cpanel_version()
#3 /wp-content/plugins/wf-cpanel-right-now-site-health/includes/Main.php(178): WebFacing\cPanel\Main::init_data()
#4 /wp-includes/class-wp-hook.php(307): WebFacing\cPanel\Main::WebFacing\cPanel\{closure}()
#5 /wp-includes/class-wp-hook.php(331): WP_Hook->apply_filters()
#6 /opt/bit in /wp-content/plugins/wf-cpanel-right-now-site-health/includes/Main.php on line 323