Benchmarks
Plugin footprint Passed 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲4.05MB] [CPU: ▼125.35ms] 75% from 4 tests
An overview of server-side resources used by Setka Workflow — manage the editorial process, track content production
The following require your attention
- RAM: Try to keep total memory usage under 10MB (currently 13.81MB on /wp-admin/options-general.php?page=setka-workflow)
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 4.65 ▲1.93 | 45.77 ▲22.90 |
Dashboard /wp-admin | 7.82 ▲4.76 | 82.15 ▲34.04 |
Posts /wp-admin/edit.php | 7.87 ▲4.76 | 76.03 ▲28.12 |
Add New Post /wp-admin/post-new.php | 10.34 ▲4.90 | 89.81 ▼572.49 |
Media Library /wp-admin/upload.php | 7.76 ▲4.75 | 61.75 ▲20.07 |
Setka Workflow /wp-admin/options-general.php?page=setka-workflow | 13.81 | 116.44 |
Server storage [IO: ▲22.78MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
There were no storage issued detected upon installing this plugin
Filesystem: 3,870 new files
Database: no new tables, 1 new option
New WordPress options |
---|
setka_workflow_auto_created_posts_author_id |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Setka Workflow — manage the editorial process, track content production
Normal browser usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 3,742 ▲146 | 16.15 ▲0.65 | 9.75 ▼1.13 | 50.60 ▼3.47 |
Dashboard /wp-admin | 3,000 ▲66 | 6.96 ▲1.04 | 147.67 ▼14.07 | 122.24 ▲3.29 |
Posts /wp-admin/edit.php | 2,772 ▲33 | 3.04 ▲0.36 | 75.91 ▲9.63 | 111.60 ▲22.34 |
Add New Post /wp-admin/post-new.php | 1,558 ▼33 | 18.19 ▼0.59 | 385.91 ▲1.86 | 141.69 ▲27.39 |
Media Library /wp-admin/upload.php | 1,834 ▲27 | 5.41 ▲0.41 | 139.04 ▼17.49 | 129.14 ▲1.46 |
Setka Workflow /wp-admin/options-general.php?page=setka-workflow | 1,153 | 2.59 | 62.54 | 86.32 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] Passed 4 tests
🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
The plugin uninstalled completely, with no zombie files or tables
Smoke tests 50% 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)
Even though no errors were found, this is by no means an exhaustive test
SRP 0% from 2 tests
🔹 Tests weight: 20 | A shallow check of the single-responsibility principle; PHP files should perform no action - including output of placeholder text - and trigger no errors when accessed directly
The following issues need your attention
- 2× PHP files output text when accessed directly:
- > /wp-content/plugins/setka-workflow/vendor/symfony/mime/Resources/bin/update_mime_types.php
- > /wp-content/plugins/setka-workflow/vendor/symfony/intl/Resources/bin/update-data.php
- 1463× PHP files trigger errors when accessed directly with GET requests (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Class 'Composer\\Installers\\BaseInstaller' not found in wp-content/plugins/setka-workflow/vendor/composer/installers/src/Composer/Installers/LithiumInstaller.php:4
- > PHP Fatal error
Uncaught Error: Class 'Zend\\Code\\Generator\\AbstractGenerator' not found in wp-content/plugins/setka-workflow/vendor/zendframework/zend-code/src/Generator/DocBlock/Tag/LicenseTag.php:16
- > PHP Fatal error
Uncaught Error: Class 'Twig\ode\\Expression\\Binary\\AbstractBinary' not found in wp-content/plugins/setka-workflow/vendor/twig/twig/src/Node/Expression/Binary/EndsWithBinary.php:16
- > PHP Fatal error
Uncaught Error: Class 'ProxyManager\\Generator\\MethodGenerator' not found in wp-content/plugins/setka-workflow/vendor/ocramius/proxy-manager/src/ProxyManager/ProxyGenerator/AccessInterceptorScopeLocalizer/MethodGenerator/StaticProxyConstructor.php:33
- > PHP Fatal error
Uncaught Error: Class 'Monolog\\Handler\\StreamHandler' not found in wp-content/plugins/setka-workflow/vendor/monolog/monolog/src/Monolog/Handler/RotatingFileHandler.php:26
- > PHP Fatal error
Uncaught Error: Class 'Korobochkin\\WPKit\\Runners\\AbstractRunner' not found in wp-content/plugins/setka-workflow/source/Admin/MetaBoxes/MetaBoxesRunner.php:9
- > PHP Warning
require_once(lib/byte_safe_strings.php): failed to open stream: No such file or directory in wp-content/plugins/setka-workflow/vendor/paragonie/random_compat/psalm-autoload.php on line 3
- > PHP Fatal error
Uncaught Error: Interface 'Zend\\EventManager\\EventsCapableInterface' not found in wp-content/plugins/setka-workflow/vendor/zendframework/zend-eventmanager/src/EventManagerAwareInterface.php:15
- > PHP Fatal error
Uncaught Error: Interface 'Symfony\\Component\\Validator\\Violation\\ConstraintViolationBuilderInterface' not found in wp-content/plugins/setka-workflow/vendor/symfony/validator/Violation/ConstraintViolationBuilder.php:28
- > PHP Fatal error
Uncaught Error: Interface 'Symfony\\Component\\Form\\Extension\\Validator\\ViolationMapper\\ViolationMapperInterface' not found in wp-content/plugins/setka-workflow/vendor/symfony/form/Extension/Validator/ViolationMapper/ViolationMapper.php:25
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
Everything seems fine on the user side
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 94% from 16 tests
It's important to format your readme.txt file correctly as it is parsed for the public listing of your plugin
Attributes that need to be fixed:
- Tags: There are too many tags (11 tag instead of maximum 10)
setka-workflow/plugin.php 85% from 13 tests
"Setka Workflow — manage the editorial process, track content production" version 2.0.0's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
Please make the necessary changes and fix the following:
- Main file name: Please rename the main PHP file in this plugin to the plugin slug ("setka-workflow.php" instead of "plugin.php")
- Domain Path: The domain path points to a folder that does not exist ("/languages/")
Code Analysis 97% from 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short check of programming languages and file extensions; no executable files are allowed
Good job! No executable or dangerous file extensions detected515,233 lines of code in 3,698 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
JSON | 1,157 | 0 | 0 | 336,672 |
PHP | 2,202 | 29,168 | 69,813 | 137,826 |
XML | 104 | 18 | 1 | 19,859 |
Markdown | 79 | 2,495 | 0 | 7,863 |
JavaScript | 11 | 1,248 | 358 | 4,782 |
reStructuredText | 104 | 2,454 | 2,404 | 2,930 |
CSS | 8 | 341 | 33 | 2,214 |
Twig | 19 | 219 | 59 | 1,867 |
XSD | 2 | 45 | 1 | 420 |
SVG | 1 | 2 | 15 | 329 |
Bourne Shell | 6 | 40 | 12 | 230 |
PO File | 1 | 46 | 65 | 151 |
Sass | 1 | 10 | 0 | 60 |
Bourne Again Shell | 1 | 2 | 0 | 11 |
Dockerfile | 1 | 8 | 0 | 10 |
make | 1 | 4 | 0 | 9 |
PHP code 50% from 2 tests
Cyclomatic complexity and code structure are the fingerprint of this plugin
These items need your attention
- Cyclomatic complexity of methods should be reduced to less than 100 (currently 179)
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.45 |
Average class complexity | 8.03 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 531.00 |
Average method complexity | 2.79 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 179.00 |
Code structure | ||
---|---|---|
Namespaces | 310 | |
Interfaces | 256 | |
Traits | 71 | |
Classes | 1,843 | |
▷ Abstract classes | 109 | 5.91% |
▷ Concrete classes | 1,734 | 94.09% |
▷ Final classes | 152 | 8.77% |
Methods | 8,937 | |
▷ Static methods | 619 | 6.93% |
▷ Public methods | 7,457 | 83.44% |
▷ Protected methods | 680 | 7.61% |
▷ Private methods | 800 | 8.95% |
Functions | 635 | |
▷ Named functions | 225 | 35.43% |
▷ Anonymous functions | 410 | 64.57% |
Constants | 855 | |
▷ Global constants | 52 | 6.08% |
▷ Class constants | 803 | 93.92% |
▷ Public constants | 771 | 96.01% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
2 PNG files occupy 0.01MB with 0.00MB in potential savings
Potential savings
Compression of 2 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
vendor/ocramius/proxy-manager/doc-template/img/enf.png | 3.65KB | 3.65KB | 0.00% |
vendor/ocramius/proxy-manager/doc-template/img/block.png | 2.32KB | 1.58KB | ▼ 31.82% |