Benchmarks
Plugin footprint 65% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices
Install script ran successfully
Server metrics [RAM: ▲0.13MB] [CPU: ▼21.59ms] Passed 4 tests
This is a short check of server-side resources used by Plenigo
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.44 ▼0.02 | 19.99 ▼27.31 |
| Dashboard /wp-admin | 3.96 ▲0.66 | 51.11 ▲0.84 |
| Posts /wp-admin/edit.php | 4.01 ▲0.65 | 49.73 ▼5.46 |
| Add New Post /wp-admin/post-new.php | 5.18 ▼0.70 | 45.32 ▼54.41 |
| Media Library /wp-admin/upload.php | 3.82 ▲0.60 | 43.00 ▲4.18 |
Server storage [IO: ▲1.03MB] [DB: ▲0.07MB] Passed 3 tests
Filesystem and database footprint
This plugin installed successfully
Filesystem: 182 new files
Database: 1 new table, 8 new options
| New tables |
|---|
| wp_plenigo_log |
| New WordPress options |
|---|
| plenigo_settings |
| widget_theysaidso_widget |
| jal_db_version |
| widget_recent-comments |
| can_compress_scripts |
| widget_recent-posts |
| theysaidso_admin_options |
| db_upgraded |
Browser metrics Passed 4 tests
Plenigo: an overview of browser usage
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,949 ▲188 | 14.36 ▲0.07 | 29.17 ▲27.29 | 40.84 ▼3.77 |
| Dashboard /wp-admin | 2,207 ▲33 | 5.71 ▲0.11 | 92.63 ▼5.33 | 80.38 ▲38.69 |
| Posts /wp-admin/edit.php | 2,127 ▲27 | 2.05 ▲0.01 | 38.57 ▼5.49 | 33.70 ▼4.29 |
| Add New Post /wp-admin/post-new.php | 1,704 ▲159 | 23.00 ▼0.47 | 704.89 ▲17.98 | 33.37 ▼27.54 |
| Media Library /wp-admin/upload.php | 1,428 ▲28 | 4.34 ▲0.12 | 105.71 ▲1.06 | 73.32 ▲27.37 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.07MB] 50% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
It is recommended to fix the following
- The plugin did not uninstall successfully, leaving 1 table in the database
- wp_plenigo_log
- Zombie WordPress options detected upon uninstall: 8 options
- can_compress_scripts
- widget_recent-posts
- plenigo_settings
- theysaidso_admin_options
- widget_recent-comments
- jal_db_version
- widget_theysaidso_widget
- db_upgraded
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a short smoke test looking for server-side errors
The smoke test was a success, however most plugin functionality was not tested
SRP 50% from 2 tests
🔹 Tests weight: 20 | SRP (Single-Responsibility Principle) - PHP files must act as libraries and never output text or perform any action when accessed directly in a browser
The following issues need your attention
- 58× PHP files trigger errors when accessed directly with GET requests (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Class 'plenigo_plugin\\settings\\PlenigoWPSetting' not found in wp-content/plugins/plenigo/plenigo_plugin/settings/SettingProductGroupTwoDB.php:30
- > PHP Fatal error
Uncaught Error: Call to undefined function register_activation_hook() in wp-content/plugins/plenigo/plenigo_wordpress.php:53
- > PHP Fatal error
Uncaught Error: Class 'plenigo_plugin\\settings\\SettingCurtainButtonBuy' not found in wp-content/plugins/plenigo/plenigo_plugin/settings/SettingCurtainButtonLogin.php:30
- > PHP Fatal error
Uncaught Error: Interface 'plenigo\\models\\Loggable' not found in wp-content/plugins/plenigo/plenigo_plugin/models/WordpressLogging.php:33
- > PHP Fatal error
Uncaught Error: Class 'plenigo_plugin\\settings\\PlenigoWPSetting' not found in wp-content/plugins/plenigo/plenigo_plugin/settings/SettingCurtainBuyTextDB.php:30
- > PHP Fatal error
Uncaught Error: Class 'plenigo_plugin\\settings\\PlenigoWPSetting' not found in wp-content/plugins/plenigo/plenigo_plugin/settings/SettingGACode.php:30
- > PHP Fatal error
Uncaught Error: Class 'plenigo_plugin\\settings\\PlenigoWPSetting' not found in wp-content/plugins/plenigo/plenigo_plugin/settings/SettingCategoryTagDB.php:30
- > PHP Fatal error
Uncaught Error: Class 'plenigo_plugin\\settings\\PlenigoWPSetting' not found in wp-content/plugins/plenigo/plenigo_plugin/settings/SettingWooProductType.php:30
- > PHP Fatal error
Uncaught Error: Class 'WP_Widget' not found in wp-content/plugins/plenigo/plenigo_plugin/PlenigoLoginWidget.php:17
- > PHP Fatal error
Uncaught Error: Class 'plenigo_plugin\\settings\\PlenigoWPSetting' not found in wp-content/plugins/plenigo/plenigo_plugin/settings/SettingUseWPLogin.php:30
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 86% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file is an important file in your plugin as it is parsed by WordPress.org to prepare the public listing of your plugin
These attributes need to be fixed:
- Tags: Too many tags (24 tag instead of maximum 10); only the first 5 tags are used in your directory listing
plenigo/plenigo_wordpress.php 77% from 13 tests
Analyzing the main PHP file in "Plenigo" version 1.12.0
Please take the time to fix the following:
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("plenigo.php" instead of "plenigo_wordpress.php")
- Requires at least: Required version must be the same as the one declared in readme.txt ("4.0.0" instead of "4.0")
- Description: Keep the plugin description shorter than 140 characters (currently 159 characters long)
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are considered dangerous and should not be included with any WordPress plugin
Good job! No executable or dangerous file extensions detected15,158 lines of code in 171 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 147 | 3,208 | 9,240 | 12,173 |
| PO File | 6 | 955 | 1,403 | 2,143 |
| JavaScript | 10 | 38 | 28 | 473 |
| CSS | 2 | 30 | 9 | 271 |
| HTML | 6 | 6 | 6 | 98 |
PHP code Passed 2 tests
This is a short overview of cyclomatic complexity and code structure for this plugin
There were no cyclomatic complexity issued detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.30 |
| Average class complexity | 12.19 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 217.00 |
| Average method complexity | 2.49 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 32.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 18 | |
| Interfaces | 3 | |
| Traits | 0 | |
| Classes | 142 | |
| ▷ Abstract classes | 4 | 2.82% |
| ▷ Concrete classes | 138 | 97.18% |
| ▷ Final classes | 11 | 7.97% |
| Methods | 1,101 | |
| ▷ Static methods | 195 | 17.71% |
| ▷ Public methods | 907 | 82.38% |
| ▷ Protected methods | 88 | 7.99% |
| ▷ Private methods | 106 | 9.63% |
| Functions | 7 | |
| ▷ Named functions | 5 | 71.43% |
| ▷ Anonymous functions | 2 | 28.57% |
| Constants | 486 | |
| ▷ Global constants | 11 | 2.26% |
| ▷ Class constants | 475 | 97.74% |
| ▷ Public constants | 475 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
Often times overlooked, PNG files can occupy unnecessary space in your plugin
PNG images were not found in this plugin