Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices
Installer ran successfully
Server metrics [RAM: ▲0.49MB] [CPU: ▲6.39ms] Passed 4 tests
An overview of server-side resources used by Wyvern Toolkit
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.95 ▲0.48 | 45.83 ▲5.51 |
| Dashboard /wp-admin | 3.80 ▲0.50 | 58.94 ▲7.65 |
| Posts /wp-admin/edit.php | 3.85 ▲0.49 | 55.74 ▲2.57 |
| Add New Post /wp-admin/post-new.php | 6.42 ▲0.53 | 103.26 ▲9.82 |
| Media Library /wp-admin/upload.php | 3.73 ▲0.49 | 50.63 ▲11.48 |
Server storage [IO: ▲2.02MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
This plugin installed successfully
Filesystem: 73 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| db_upgraded |
| widget_theysaidso_widget |
| theysaidso_admin_options |
| widget_recent-comments |
| can_compress_scripts |
| widget_recent-posts |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Wyvern Toolkit
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,904 ▲143 | 15.51 ▲0.98 | 1.62 ▼0.11 | 39.84 ▼4.51 |
| Dashboard /wp-admin | 2,310 ▲140 | 6.91 ▲1.30 | 124.29 ▲23.14 | 41.19 ▲0.38 |
| Posts /wp-admin/edit.php | 2,217 ▲114 | 3.98 ▲1.97 | 83.39 ▲43.99 | 40.50 ▲2.28 |
| Add New Post /wp-admin/post-new.php | 1,571 ▲34 | 24.44 ▲6.16 | 695.96 ▲55.45 | 37.81 ▼23.77 |
| Media Library /wp-admin/upload.php | 1,515 ▲115 | 5.62 ▲1.38 | 159.33 ▲58.56 | 47.98 ▲5.83 |
| Modules /wp-admin/admin.php?page=wyvern-toolkit#/modules | 1,100 | 10.24 | 378.30 | 111.85 |
| Settings /wp-admin/admin.php?page=wyvern-toolkit#/settings | 1,251 | 11.83 | 303.18 | 78.60 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
These items require your attention
- This plugin did not uninstall successfully, leaving 6 options in the database
- can_compress_scripts
- db_upgraded
- widget_theysaidso_widget
- widget_recent-posts
- theysaidso_admin_options
- widget_recent-comments
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
Even though no errors were found, this is by no means an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle applies for WordPress plugins as well - please make sure your PHP files perform no actions when accessed directly
Almost there! Just fix the following items
- 11× PHP files trigger server errors when accessed directly (only 10 are shown):
- > PHP Warning
Use of undefined constant WP_DEBUG - assumed 'WP_DEBUG' (this will throw an Error in a future version of PHP) in wp-content/plugins/wyvern-toolkit/modules/import-export/inc/importers/content-importer/init.php on line 9
- > PHP Warning
require_once(WYVERN_TOOLKIT_PATHincludes/Traits/Singleton.php): failed to open stream: No such file or directory in wp-content/plugins/wyvern-toolkit/includes/requires.php on line 35
- > PHP Warning
Use of undefined constant WYVERN_TOOLKIT_PATH - assumed 'WYVERN_TOOLKIT_PATH' (this will throw an Error in a future version of PHP) in wp-content/plugins/wyvern-toolkit/includes/requires.php on line 35
- > PHP Fatal error
require_once(): Failed opening required 'ABSPATHwp-admin/includes/import.php' (include_path='.:/usr/share/php') in wp-content/plugins/wyvern-toolkit/modules/import-export/inc/importers/content-importer/init.php on line 13
- > PHP Fatal error
require_once(): Failed opening required 'WYVERN_TOOLKIT_PATHincludes/Traits/Singleton.php' (include_path='.:/usr/share/php') in wp-content/plugins/wyvern-toolkit/includes/requires.php on line 35
- > PHP Fatal error
Uncaught Error: Call to undefined function WyvernToolkit\\Modules\\CustomScripts\\Functions\\add_filter() in wp-content/plugins/wyvern-toolkit/modules/custom-scripts/inc/functions.php:102
- > PHP Warning
Use of undefined constant ABSPATH - assumed 'ABSPATH' (this will throw an Error in a future version of PHP) in wp-content/plugins/wyvern-toolkit/modules/import-export/inc/importers/content-importer/init.php on line 13
- > PHP Fatal error
Uncaught Error: Call to undefined function WyvernToolkit\\Modules\\Preloader\\Functions\\add_action() in wp-content/plugins/wyvern-toolkit/modules/preloader/inc/functions.php:19
- > PHP Fatal error
Uncaught Error: Class 'WP_REST_Controller' not found in wp-content/plugins/wyvern-toolkit/includes/Abstracts/RestController.php:13
- > PHP Warning
require_once(ABSPATHwp-admin/includes/import.php): failed to open stream: No such file or directory in wp-content/plugins/wyvern-toolkit/modules/import-export/inc/importers/content-importer/init.php on line 13
- > PHP Warning
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
There were no browser issues found
Optimizations
Plugin configuration 96% from 29 tests
readme.txt Passed 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
8 plugin tags: page-speed, maintenance-mode, preloader, import-export, google-fonts...
wyvern-toolkit/wyvern-toolkit.php 92% from 13 tests
The principal PHP file in "Wyvern Toolkit" v. 1.0.6 is loaded by WordPress automatically on each request
You should first fix the following items:
- Description: Please don't use more than 140 characters for the plugin description (currently 246 characters long)
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | There should be no dangerous file extensions present in any WordPress plugin
Good job! No executable or dangerous file extensions detected36,668 lines of code in 67 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| JSON | 6 | 0 | 0 | 32,272 |
| PHP | 57 | 1,388 | 1,903 | 4,349 |
| JavaScript | 2 | 0 | 0 | 41 |
| SVG | 1 | 0 | 0 | 5 |
| CSS | 1 | 0 | 0 | 1 |
PHP code Passed 2 tests
An short overview of logical lines of code, cyclomatic complexity, and other code metrics
Although this was not an exhaustive test, there were no cyclomatic complexity issues detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.44 |
| Average class complexity | 16.54 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 214.00 |
| Average method complexity | 3.51 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 50.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 11 | |
| Interfaces | 0 | |
| Traits | 1 | |
| Classes | 40 | |
| ▷ Abstract classes | 2 | 5.00% |
| ▷ Concrete classes | 38 | 95.00% |
| ▷ Final classes | 1 | 2.63% |
| Methods | 248 | |
| ▷ Static methods | 56 | 22.58% |
| ▷ Public methods | 197 | 79.44% |
| ▷ Protected methods | 46 | 18.55% |
| ▷ Private methods | 5 | 2.02% |
| Functions | 32 | |
| ▷ Named functions | 26 | 81.25% |
| ▷ Anonymous functions | 6 | 18.75% |
| Constants | 16 | |
| ▷ Global constants | 13 | 81.25% |
| ▷ Class constants | 3 | 18.75% |
| ▷ Public constants | 3 | 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
There were not PNG files found in your plugin