Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.07MB] [CPU: ▼2.60ms] Passed 4 tests
An overview of server-side resources used by Conversion for Tracktum on Woocommerce
This plugin has minimal impact on server resources
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.54 ▲0.08 | 37.98 ▼3.93 |
Dashboard /wp-admin | 3.37 ▲0.07 | 45.31 ▼3.10 |
Posts /wp-admin/edit.php | 3.49 ▲0.13 | 48.52 ▲2.02 |
Add New Post /wp-admin/post-new.php | 5.95 ▲0.07 | 90.98 ▼5.37 |
Media Library /wp-admin/upload.php | 3.30 ▲0.07 | 35.67 ▲4.08 |
Server storage [IO: ▲5.38MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
The plugin installed successfully
Filesystem: 1,699 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_recent-comments |
widget_theysaidso_widget |
can_compress_scripts |
theysaidso_admin_options |
widget_recent-posts |
db_upgraded |
Browser metrics Passed 4 tests
An overview of browser requirements for Conversion for Tracktum on Woocommerce
There were no issues detected in relation to browser resource usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,825 ▲90 | 13.29 ▼1.48 | 1.87 ▼0.04 | 42.64 ▼0.92 |
Dashboard /wp-admin | 2,206 ▲21 | 5.86 ▲0.93 | 105.04 ▼10.47 | 41.81 ▼4.53 |
Posts /wp-admin/edit.php | 2,092 ▼0 | 2.05 ▲0.06 | 39.69 ▲3.23 | 35.25 ▲4.39 |
Add New Post /wp-admin/post-new.php | 1,533 ▼0 | 23.11 ▲0.05 | 643.23 ▼23.40 | 55.43 ▼2.56 |
Media Library /wp-admin/upload.php | 1,382 ▼6 | 4.19 ▼0.21 | 95.78 ▼16.21 | 40.34 ▼8.74 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
You still need to fix the following
- Zombie WordPress options were found after uninstall: 6 options
- can_compress_scripts
- widget_recent-comments
- widget_recent-posts
- theysaidso_admin_options
- widget_theysaidso_widget
- db_upgraded
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
Even though everything seems fine, this is not an exhaustive test
SRP 0% from 2 tests
🔹 Tests weight: 20 | It is important to ensure that your PHP files perform no action when accessed directly, respecting the single-responsibility principle
Please fix the following
- 4× GET requests to PHP files return non-empty strings:
- > /wp-content/plugins/wc-tracktum/vendor/automattic/vipwpcs/WordPress-VIP-Go/ruleset-test.php
- > /wp-content/plugins/wc-tracktum/vendor/squizlabs/php_codesniffer/scripts/build-phar.php
- > /wp-content/plugins/wc-tracktum/vendor/automattic/vipwpcs/tests/bootstrap.php
- > /wp-content/plugins/wc-tracktum/vendor/automattic/vipwpcs/WordPressVIPMinimum/ruleset-test.php
- 720× PHP files trigger server errors when accessed directly (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Interface 'PHP_CodeSniffer\\Sniffs\\Sniff' not found in wp-content/plugins/wc-tracktum/vendor/squizlabs/php_codesniffer/src/Standards/Squiz/Sniffs/Functions/GlobalFunctionSniff.php:15
- > PHP Fatal error
Uncaught Error: Class 'PHP_CodeSniffer\\Tests\\Standards\\AbstractSniffUnitTest' not found in wp-content/plugins/wc-tracktum/vendor/squizlabs/php_codesniffer/src/Standards/PSR2/Tests/ControlStructures/ControlStructureSpacingUnitTest.php:14
- > PHP Fatal error
Uncaught Error: Class 'PHP_CodeSniffer\\Tests\\Standards\\AbstractSniffUnitTest' not found in wp-content/plugins/wc-tracktum/vendor/squizlabs/php_codesniffer/src/Standards/Generic/Tests/Files/OneClassPerFileUnitTest.php:14
- > PHP Fatal error
Uncaught Error: Class 'WordPressCS\\WordPress\\Sniff' not found in wp-content/plugins/wc-tracktum/vendor/wp-coding-standards/wpcs/WordPress/Sniffs/CodeAnalysis/EmptyStatementSniff.php:32
- > PHP Fatal error
Uncaught Error: Class 'WordPressCS\\WordPress\\AbstractFunctionParameterSniff' not found in wp-content/plugins/wc-tracktum/vendor/wp-coding-standards/wpcs/WordPress/Sniffs/CodeAnalysis/EscapedNotTranslatedSniff.php:24
- > PHP Fatal error
Uncaught Error: Interface 'PHP_CodeSniffer\\Sniffs\\Sniff' not found in wp-content/plugins/wc-tracktum/vendor/squizlabs/php_codesniffer/src/Standards/Squiz/Sniffs/PHP/DisallowInlineIfSniff.php:15
- > PHP Fatal error
Uncaught Error: Class 'PHP_CodeSniffer\\Sniffs\\AbstractArraySniff' not found in wp-content/plugins/wc-tracktum/vendor/squizlabs/php_codesniffer/tests/Core/Sniffs/AbstractArraySniffTestable.php:14
- > PHP Fatal error
Uncaught Error: Class 'PHPUnit\\Framework\\TestCase' not found in wp-content/plugins/wc-tracktum/vendor/squizlabs/php_codesniffer/tests/Core/AbstractMethodUnitTest.php:17
- > PHP Fatal error
Uncaught Error: Class 'PHP_CodeSniffer\\Tests\\Standards\\AbstractSniffUnitTest' not found in wp-content/plugins/wc-tracktum/vendor/squizlabs/php_codesniffer/src/Standards/PSR2/Tests/Methods/FunctionClosingBraceUnitTest.php:14
- > PHP Fatal error
Uncaught Error: Interface 'PHP_CodeSniffer\\Sniffs\\Sniff' not found in wp-content/plugins/wc-tracktum/vendor/squizlabs/php_codesniffer/src/Standards/Generic/Sniffs/PHP/NoSilencedErrorsSniff.php:22
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
Everything seems fine on the user side
Optimizations
Plugin configuration 96% from 29 tests
readme.txt Passed 16 tests
The readme.txt file is important because it is parsed by WordPress.org for the public listing of your plugin
5 plugin tags: e-ecommerce, tracking, ecommerce, commerce, woocommerce
wc-tracktum/tracktum.php 92% from 13 tests
The main PHP file in "Conversion for Tracktum on Woocommerce" ver. 1.3 adds more information about the plugin and also serves as the entry point for this plugin
You should first fix the following items:
- Main file name: The principal plugin file should be the same as the plugin slug ("wc-tracktum.php" instead of "tracktum.php")
Code Analysis 3% from 3 tests
File types 0% from 1 test
🔸 Test weight: 35 | Executable files are not allowed as they can serve as attack vectors
It is important to fix the following items
- Do not distribute dangerous files with your plugin
- .bat - Batch File in Windows
- ☣ wp-content/plugins/wc-tracktum/vendor/squizlabs/php_codesniffer/bin/phpcbf.bat
- ☣ wp-content/plugins/wc-tracktum/vendor/squizlabs/php_codesniffer/bin/phpcs.bat
- .bat - Batch File in Windows
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 900 | 20,556 | 36,828 | 80,824 |
XML | 170 | 416 | 765 | 6,025 |
Pascal | 123 | 2,652 | 5,392 | 5,699 |
Markdown | 12 | 541 | 0 | 2,253 |
JavaScript | 64 | 779 | 863 | 2,237 |
CSS | 35 | 209 | 108 | 988 |
JSON | 1 | 0 | 0 | 270 |
XSD | 1 | 6 | 0 | 130 |
Bourne Again Shell | 6 | 8 | 83 | 19 |
DOS Batch | 2 | 4 | 10 | 10 |
PHP code 50% from 2 tests
A brief analysis of cyclomatic complexity and code structure for this plugin
Please tend to the following items
- Method cyclomatic complexity has to be reduced to less than 100 (currently 357)
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.47 |
Average class complexity | 15.64 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 505.00 |
Average method complexity | 5.91 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 357.00 |
Code structure | ||
---|---|---|
Namespaces | 193 | |
Interfaces | 2 | |
Traits | 0 | |
Classes | 751 | |
▷ Abstract classes | 18 | 2.40% |
▷ Concrete classes | 733 | 97.60% |
▷ Final classes | 1 | 0.14% |
Methods | 2,260 | |
▷ Static methods | 114 | 5.04% |
▷ Public methods | 1,866 | 82.57% |
▷ Protected methods | 294 | 13.01% |
▷ Private methods | 100 | 4.42% |
Functions | 17 | |
▷ Named functions | 3 | 17.65% |
▷ Anonymous functions | 14 | 82.35% |
Constants | 138 | |
▷ Global constants | 106 | 76.81% |
▷ Class constants | 32 | 23.19% |
▷ Public constants | 32 | 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
3 PNG files occupy 0.06MB with 0.02MB in potential savings
Potential savings
Compression of 3 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
assets/images/google.png | 41.17KB | 14.04KB | ▼ 65.90% |
assets/images/facebook.png | 1.48KB | 0.74KB | ▼ 49.64% |
assets/images/pinterest.png | 16.31KB | 16.84KB | 0.00% |