Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.06MB] [CPU: ▼3.25ms] Passed 4 tests
A check of server-side resources used by SMSAPI WooCommerce
This plugin has minimal impact on server resources
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.52 ▲0.06 | 35.79 ▼7.28 |
Dashboard /wp-admin | 3.37 ▲0.06 | 45.15 ▲3.55 |
Posts /wp-admin/edit.php | 3.48 ▲0.13 | 47.09 ▼1.81 |
Add New Post /wp-admin/post-new.php | 5.95 ▲0.06 | 92.11 ▼6.90 |
Media Library /wp-admin/upload.php | 3.29 ▲0.06 | 33.05 ▲2.98 |
Server storage [IO: ▲1.37MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
This plugin installed successfully
Filesystem: 421 new files
Database: no new tables, 6 new options
New WordPress options |
---|
db_upgraded |
theysaidso_admin_options |
can_compress_scripts |
widget_recent-comments |
widget_theysaidso_widget |
widget_recent-posts |
Browser metrics Passed 4 tests
Checking browser requirements for SMSAPI WooCommerce
There were no issues detected in relation to browser resource usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,802 ▲31 | 13.36 ▼1.00 | 1.73 ▼0.71 | 42.72 ▼6.04 |
Dashboard /wp-admin | 2,208 ▲17 | 5.86 ▲0.82 | 106.87 ▲6.60 | 40.06 ▲1.19 |
Posts /wp-admin/edit.php | 2,091 ▲2 | 2.05 ▲0.02 | 38.80 ▼2.59 | 34.27 ▼2.41 |
Add New Post /wp-admin/post-new.php | 1,539 ▲4 | 18.48 ▼4.75 | 612.48 ▲14.41 | 65.01 ▲5.00 |
Media Library /wp-admin/upload.php | 1,390 ▼1 | 4.22 ▲0.02 | 94.85 ▲1.06 | 41.62 ▲0.68 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
These items require your attention
- The uninstall procedure has failed, leaving 6 options in the database
- widget_recent-posts
- widget_recent-comments
- db_upgraded
- widget_theysaidso_widget
- can_compress_scripts
- theysaidso_admin_options
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
Even though everything seems fine, this is not 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
Please take a closer look at the following
- 131× PHP files trigger errors when accessed directly with GET requests (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Class 'GuzzleHttp\\Promise\\RejectionException' not found in wp-content/plugins/woo-smsapi-pl/class/vendor/guzzlehttp/promises/src/CancellationException.php:7
- > PHP Fatal error
Uncaught Error: Interface 'GuzzleHttp\\Promise\\PromiseInterface' not found in wp-content/plugins/woo-smsapi-pl/class/vendor/guzzlehttp/promises/src/FulfilledPromise.php:10
- > PHP Fatal error
Uncaught Error: Class 'MabeEnum\\Enum' not found in wp-content/plugins/woo-smsapi-pl/class/vendor/smsapi/php-client/tests/ServiceName.php:13
- > PHP Fatal error
Uncaught Error: Interface 'Psr\\Http\\Message\\StreamInterface' not found in wp-content/plugins/woo-smsapi-pl/class/vendor/guzzlehttp/psr7/src/LimitStream.php:10
- > PHP Fatal error
Uncaught Error: Class 'PHPUnit\\Framework\\Assert' not found in wp-content/plugins/woo-smsapi-pl/class/vendor/smsapi/php-client/tests/Assert/SubuserAssert.php:13
- > PHP Fatal error
Trait 'Smsapi\\Client\\Feature\\Bag\\PaginationBag' not found in wp-content/plugins/woo-smsapi-pl/class/vendor/smsapi/php-client/src/Feature/Contacts/Bag/FindContactsBag.php on line 21
- > PHP Fatal error
Uncaught Error: Interface 'Smsapi\\Client\\Feature\\Profile\\ProfileFeature' not found in wp-content/plugins/woo-smsapi-pl/class/vendor/smsapi/php-client/src/Feature/Profile/SmsapiPlProfileFeature.php:10
- > PHP Fatal error
Uncaught Error: Class 'Smsapi\\Client\\Tests\\SmsapiClientIntegrationTestCase' not found in wp-content/plugins/woo-smsapi-pl/class/vendor/smsapi/php-client/tests/Integration/Feature/Contacts/Groups/ContactsGroupsFeatureTest.php:20
- > PHP Fatal error
Uncaught Error: Interface 'Smsapi\\Client\\Feature\\Mfa\\MfaFeature' not found in wp-content/plugins/woo-smsapi-pl/class/vendor/smsapi/php-client/src/Feature/Mfa/MfaHttpFeature.php:17
- > PHP Fatal error
Uncaught Error: Class 'Smsapi\\Client\\Tests\\SmsapiClientUnitTestCase' not found in wp-content/plugins/woo-smsapi-pl/class/vendor/smsapi/php-client/tests/Unit/Infrastructure/ResponseMapper/RestResponseMapperTest.php:14
- > 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 90% from 29 tests
readme.txt Passed 16 tests
Often overlooked, readme.txt is one of the most important files in your plugin
3 plugin tags: smsapi, woocommerce, sms
woo-smsapi-pl/woocommerce-smsapi.php 77% from 13 tests
The main file in "SMSAPI WooCommerce" v. 2.1 serves as a complement to information provided in readme.txt and as the entry point to the plugin
Please take the time to fix the following:
- Main file name: Please rename the main PHP file in this plugin to the plugin slug ("woo-smsapi-pl.php" instead of "woocommerce-smsapi.php")
- Text Domain: The text domain must be the same as the plugin slug, although optional since WordPress version 4.6
- Requires at least: The required version number did not match the one declared in readme.txt ("4.0" instead of "3.9")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are not allowed as they can serve as attack vectors
Success! There were no dangerous files found in this plugin24,954 lines of code in 401 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 356 | 4,229 | 7,304 | 19,782 |
Markdown | 17 | 1,163 | 0 | 3,557 |
JSON | 16 | 0 | 0 | 1,062 |
JavaScript | 2 | 82 | 12 | 213 |
PO File | 1 | 45 | 52 | 142 |
XML | 2 | 4 | 0 | 83 |
Ant | 1 | 1 | 0 | 43 |
CSS | 1 | 5 | 1 | 27 |
make | 2 | 10 | 0 | 21 |
YAML | 2 | 0 | 0 | 14 |
Dockerfile | 1 | 8 | 0 | 10 |
PHP code Passed 2 tests
Analyzing cyclomatic complexity and code structure
This plugin has no cyclomatic complexity issues
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.30 |
Average class complexity | 5.23 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 153.00 |
Average method complexity | 2.02 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 27.00 |
Code structure | ||
---|---|---|
Namespaces | 101 | |
Interfaces | 38 | |
Traits | 8 | |
Classes | 290 | |
▷ Abstract classes | 6 | 2.07% |
▷ Concrete classes | 284 | 97.93% |
▷ Final classes | 13 | 4.58% |
Methods | 1,442 | |
▷ Static methods | 167 | 11.58% |
▷ Public methods | 1,242 | 86.13% |
▷ Protected methods | 25 | 1.73% |
▷ Private methods | 175 | 12.14% |
Functions | 199 | |
▷ Named functions | 106 | 53.27% |
▷ Anonymous functions | 93 | 46.73% |
Constants | 134 | |
▷ Global constants | 48 | 35.82% |
▷ Class constants | 86 | 64.18% |
▷ Public constants | 86 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
PNG files should be compressed to save space and minimize bandwidth usage
3 PNG files occupy 0.24MB with 0.15MB in potential savings
Potential savings
Compression of 3 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
assets/images/screenshot-1.png | 126.91KB | 36.02KB | ▼ 71.62% |
assets/images/screenshot-2.png | 100.12KB | 27.53KB | ▼ 72.50% |
assets/images/wpdesk-woocommerce-plugins.png | 17.02KB | 8.66KB | ▼ 49.12% |