Benchmarks
Plugin footprint 65% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | All plugins must install correctly, without throwing any errors, warnings, or notices
This plugin's installer ran successfully
Server metrics [RAM: ▲0.16MB] [CPU: ▲0.04ms] Passed 4 tests
This is a short check of server-side resources used by CrowdHandler virtual waiting room
Normal server usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.61 ▲0.14 | 40.94 ▲5.50 |
Dashboard /wp-admin | 3.52 ▲0.21 | 56.89 ▲10.46 |
Posts /wp-admin/edit.php | 3.57 ▲0.21 | 50.31 ▲1.48 |
Add New Post /wp-admin/post-new.php | 6.05 ▲0.16 | 87.46 ▼7.52 |
Media Library /wp-admin/upload.php | 3.38 ▲0.14 | 34.61 ▲0.70 |
Server storage [IO: ▲0.13MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
The plugin installed successfully
Filesystem: 53 new files
Database: no new tables, 6 new options
New WordPress options |
---|
db_upgraded |
widget_recent-comments |
widget_recent-posts |
widget_theysaidso_widget |
theysaidso_admin_options |
can_compress_scripts |
Browser metrics Passed 4 tests
CrowdHandler virtual waiting room: an overview of browser usage
This plugin has a minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,834 ▲48 | 14.10 ▼0.46 | 1.99 ▲0.09 | 45.16 ▲6.59 |
Dashboard /wp-admin | 2,215 ▲35 | 5.51 ▼0.15 | 98.86 ▲13.25 | 43.37 ▼0.38 |
Posts /wp-admin/edit.php | 2,123 ▲23 | 2.02 ▲0.01 | 33.17 ▼2.94 | 32.91 ▼0.85 |
Add New Post /wp-admin/post-new.php | 1,543 ▲17 | 23.67 ▲0.65 | 641.43 ▼0.64 | 64.98 ▲13.73 |
Media Library /wp-admin/upload.php | 1,423 ▲29 | 4.17 ▲0.01 | 92.37 ▼4.82 | 39.62 ▼4.29 |
Uninstaller [IO: ▲0.13MB] [DB: ▲0.00MB] 50% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
These items require your attentionZombie WordPress options detected upon uninstall: 6 options
- The plugin did not uninstall correctly, leaving 53 files (0.13MB) in the plugin directory
- (new file) admin/class-crowdhandler-admin.php
- (new file) admin/css/crowdhandler-admin.css
- (new file) README.txt
- (new file) composer.json
- (new file) consts.php
- (new file) crowdhandler.php
- (new file) composer.lock
- (new file) LICENSE.txt
- (new file) admin/js/crowdhandler-admin.js
- (new file) admin/index.php
- ...
- widget_recent-posts
- widget_theysaidso_widget
- can_compress_scripts
- widget_recent-comments
- theysaidso_admin_options
- db_upgraded
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the server (in the Apache logs)
Good news, no errors were detected
SRP 50% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle: PHP files have to remain inert when accessed directly, throwing no errors and performing no actions
Please take a closer look at the following
- 8× PHP files trigger server errors when accessed directly:
- > PHP Warning
require(../../../vendor/autoload.php): failed to open stream: No such file or directory in wp-content/plugins/crowdhandler-virtual-waiting-room/vendor/crowdhandler/sdk/examples/slim-framework-psr/web/index.php on line 5
- > PHP Fatal error
Uncaught Error: Class 'CrowdHandler\\Client' not found in wp-content/plugins/crowdhandler-virtual-waiting-room/vendor/crowdhandler/sdk/src/PublicClient.php:5
- > PHP Fatal error
Uncaught Error: Class 'CrowdHandler\\Client' not found in wp-content/plugins/crowdhandler-virtual-waiting-room/vendor/crowdhandler/sdk/src/PrivateClient.php:5
- > PHP Warning
require_once(../../vendor/autoload.php): failed to open stream: No such file or directory in wp-content/plugins/crowdhandler-virtual-waiting-room/vendor/crowdhandler/sdk/examples/flat-php/advanced.php on line 8
- > PHP Fatal error
require_once(): Failed opening required '../../vendor/autoload.php' (include_path='.:/usr/share/php') in wp-content/plugins/crowdhandler-virtual-waiting-room/vendor/crowdhandler/sdk/examples/flat-php/basic.php on line 3
- > PHP Fatal error
require_once(): Failed opening required '../../vendor/autoload.php' (include_path='.:/usr/share/php') in wp-content/plugins/crowdhandler-virtual-waiting-room/vendor/crowdhandler/sdk/examples/flat-php/advanced.php on line 8
- > PHP Warning
require_once(../../vendor/autoload.php): failed to open stream: No such file or directory in wp-content/plugins/crowdhandler-virtual-waiting-room/vendor/crowdhandler/sdk/examples/flat-php/basic.php on line 3
- > PHP Fatal error
require(): Failed opening required '../../../vendor/autoload.php' (include_path='.:/usr/share/php') in wp-content/plugins/crowdhandler-virtual-waiting-room/vendor/crowdhandler/sdk/examples/slim-framework-psr/web/index.php on line 5
- > PHP Warning
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
Everything seems fine on the user side
Optimizations
Plugin configuration 93% from 29 tests
readme.txt Passed 16 tests
The readme.txt file describes your plugin functionality and requirements and it is parsed to prepare the your plugin's listing
5 plugin tags: waiting room, ecommerce, crowdhandler, queue management, traffic management
crowdhandler-virtual-waiting-room/crowdhandler.php 85% from 13 tests
The principal PHP file in "CrowdHandler virtual waiting room" v. 1.1.12 is loaded by WordPress automatically on each request
The following require your attention:
- Text Domain: You no longer need to specify the text domain since WordPress 4.6; it must be the same as the plugin slug
- Main file name: It is recommended to name the main PHP file as the plugin slug ("crowdhandler-virtual-waiting-room.php" instead of "crowdhandler.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is a short overview of programming languages used in this plugin, detecting executable files
There were no executable files found in this plugin1,876 lines of code in 41 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 34 | 384 | 957 | 1,639 |
JSON | 4 | 0 | 0 | 136 |
Markdown | 1 | 62 | 0 | 90 |
CSS | 1 | 1 | 4 | 8 |
JavaScript | 1 | 2 | 27 | 3 |
PHP code Passed 2 tests
Analyzing logical lines of code, cyclomatic complexity, and other code metrics
No complexity issues detected
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.37 |
Average class complexity | 9.00 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 47.00 |
Average method complexity | 2.45 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 18.00 |
Code structure | ||
---|---|---|
Namespaces | 3 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 21 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 21 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 117 | |
▷ Static methods | 20 | 17.09% |
▷ Public methods | 101 | 86.32% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 16 | 13.68% |
Functions | 6 | |
▷ Named functions | 4 | 66.67% |
▷ Anonymous functions | 2 | 33.33% |
Constants | 13 | |
▷ Global constants | 6 | 46.15% |
▷ Class constants | 7 | 53.85% |
▷ Public constants | 7 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
No PNG files were detected