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
This plugin's installer ran successfully
Server metrics [RAM: ▲0.25MB] [CPU: ▼4.31ms] Passed 4 tests
An overview of server-side resources used by WC SMS Notification
No issues were detected with server-side resource usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.71 ▲0.25 | 45.14 ▼5.77 |
Dashboard /wp-admin | 3.59 ▲0.29 | 53.23 ▲6.56 |
Posts /wp-admin/edit.php | 3.64 ▲0.28 | 51.48 ▲1.33 |
Add New Post /wp-admin/post-new.php | 6.13 ▲0.24 | 89.60 ▼18.10 |
Media Library /wp-admin/upload.php | 3.45 ▲0.22 | 37.49 ▲5.32 |
Setup /wp-admin/admin.php?page=sdevs-sms-setup | 3.42 | 35.13 |
WooCommerce /wp-admin/admin.php?page=sdevs-sms-woocommerce | 3.44 | 37.41 |
Template /wp-admin/admin.php?page=sdevs-sms-template | 3.43 | 34.66 |
Server storage [IO: ▲19.51MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
No storage issues were detected
Filesystem: 1,653 new files
Database: no new tables, 18 new options
New WordPress options |
---|
sms_order_status_notifications |
can_compress_scripts |
widget_recent-posts |
order_refund_template |
theysaidso_admin_options |
widget_recent-comments |
admin_new_order_sms_template |
order_cancell_template |
order_failed_template |
user_sms_notification |
... |
Browser metrics Passed 4 tests
Checking browser requirements for WC SMS Notification
Minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,816 ▲30 | 14.40 ▼0.02 | 1.81 ▼0.16 | 46.97 ▲5.60 |
Dashboard /wp-admin | 2,222 ▲45 | 5.64 ▲0.08 | 96.79 ▲2.33 | 44.15 ▲3.07 |
Posts /wp-admin/edit.php | 2,124 ▲21 | 2.03 ▲0.09 | 35.54 ▼3.58 | 35.60 ▼1.92 |
Add New Post /wp-admin/post-new.php | 1,548 ▲31 | 23.38 ▲4.43 | 596.73 ▲114.32 | 50.97 ▲0.74 |
Media Library /wp-admin/upload.php | 1,430 ▲30 | 4.17 ▲0.11 | 98.10 ▼12.03 | 43.47 ▼5.72 |
Setup /wp-admin/admin.php?page=sdevs-sms-setup | 938 | 2.52 | 51.92 | 29.84 |
WooCommerce /wp-admin/admin.php?page=sdevs-sms-woocommerce | 1,028 | 2.35 | 64.10 | 30.36 |
Template /wp-admin/admin.php?page=sdevs-sms-template | 1,070 | 2.28 | 29.96 | 34.28 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
You still need to fix the following
- Zombie WordPress options detected upon uninstall: 18 options
- new_order_sms_notification
- order_complete_template
- widget_recent-comments
- widget_recent-posts
- order_processing_template
- theysaidso_admin_options
- new_order_sms_template
- sms_order_status_notifications
- user_sms_notification
- widget_theysaidso_widget
- ...
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a short smoke test looking for server-side errors
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
- 61× PHP files trigger errors when accessed directly with GET requests (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Class 'PHPUnit\\Framework\\TestCase' not found in wp-content/plugins/wc-sms-notification/vendor/giggsey/libphonenumber-for-php/tests/core/PhoneNumberUtilTest.php:20
- > PHP Fatal error
Uncaught Error: Class 'PHPUnit\\Framework\\TestCase' not found in wp-content/plugins/wc-sms-notification/vendor/giggsey/libphonenumber-for-php/tests/Issues/CodeCoverageTest.php:8
- > PHP Fatal error
Uncaught Error: Class 'PHPUnit\\Framework\\TestCase' not found in wp-content/plugins/wc-sms-notification/vendor/giggsey/libphonenumber-for-php/tests/Issues/Issue175Test.php:13
- > PHP Fatal error
Uncaught Error: Class 'PHPUnit\\Framework\\TestCase' not found in wp-content/plugins/wc-sms-notification/vendor/giggsey/libphonenumber-for-php/tests/Issues/Issue35Test.php:8
- > PHP Fatal error
Uncaught Error: Class 'libphonenumber\\Leniency\\AbstractLeniency' not found in wp-content/plugins/wc-sms-notification/vendor/giggsey/libphonenumber-for-php/src/Leniency/ExactGrouping.php:9
- > PHP Fatal error
Uncaught Error: Class 'PHPUnit\\Framework\\TestCase' not found in wp-content/plugins/wc-sms-notification/vendor/giggsey/libphonenumber-for-php/tests/core/PhoneNumberMatcherTest.php:15
- > PHP Fatal error
Uncaught Error: Class 'PHPUnit\\Framework\\TestCase' not found in wp-content/plugins/wc-sms-notification/vendor/giggsey/libphonenumber-for-php/tests/carrier/PhoneNumberToCarrierMapperTest.php:10
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_attr_e() in wp-content/plugins/wc-sms-notification/includes/Admin/views/template.php:2
- > PHP Fatal error
Uncaught Error: Class 'PHPUnit\\Framework\\TestCase' not found in wp-content/plugins/wc-sms-notification/vendor/giggsey/libphonenumber-for-php/tests/buildtools/GeneratePhonePrefixDataTest.php:8
- > PHP Fatal error
Uncaught Error: Class 'PHPUnit\\Framework\\TestCase' not found in wp-content/plugins/wc-sms-notification/vendor/giggsey/libphonenumber-for-php/tests/Issues/Issue44Test.php:10
- > PHP Fatal error
User-side errors 0% from 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the browser (console and network errors and warnings)
Please fix the following user-side errors
- 2 occurences, only the last one shown
- > GET request to /wp-admin/admin.php?page=sdevs-sms-template
- > Console-api (severe) in wp-content/plugins/wc-sms-notification/assets/js/app.js?ver=1.0.0+4702:14
[Vue warn]: Cannot find element: #sdevs_sms_setup
Optimizations
Plugin configuration 90% from 29 tests
readme.txt Passed 16 tests
Perhaps the most important file in your plugin readme.txt gets parsed in order to generate the public listing of your plugin
3 plugin tags: sms, woocommerce, woocommerce-sms
wc-sms-notification/sms.php 77% from 13 tests
This is the main PHP file of "WC SMS Notification" version 1.0.0, providing information about the plugin in the header fields and serving as the principal entry point to the plugin's functions
It is important to fix the following:
- Text Domain: The text domain should only use lowercase characters and dashes
- Domain Path: The domain path is invalid: folder "/languages" does not exist
- Main file name: Name the main plugin file the same as the plugin slug ("wc-sms-notification.php" instead of "sms.php")
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
There were no executable files found in this plugin622,788 lines of code in 1,513 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 1,489 | 5,259 | 19,678 | 609,170 |
JavaScript | 5 | 1,780 | 2,304 | 12,123 |
Markdown | 10 | 315 | 0 | 650 |
JSON | 5 | 1 | 0 | 399 |
Vuejs Component | 1 | 7 | 0 | 218 |
Ant | 1 | 36 | 0 | 187 |
XML | 1 | 3 | 1 | 25 |
YAML | 1 | 1 | 0 | 16 |
PHP code Passed 2 tests
Analyzing cyclomatic complexity and code structure
This plugin has no cyclomatic complexity problems
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.18 |
Average class complexity | 14.16 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 367.00 |
Average method complexity | 2.28 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 48.00 |
Code structure | ||
---|---|---|
Namespaces | 23 | |
Interfaces | 3 | |
Traits | 1 | |
Classes | 112 | |
▷ Abstract classes | 1 | 0.89% |
▷ Concrete classes | 111 | 99.11% |
▷ Final classes | 2 | 1.80% |
Methods | 1,170 | |
▷ Static methods | 173 | 14.79% |
▷ Public methods | 1,004 | 85.81% |
▷ Protected methods | 87 | 7.44% |
▷ Private methods | 79 | 6.75% |
Functions | 89 | |
▷ Named functions | 80 | 89.89% |
▷ Anonymous functions | 9 | 10.11% |
Constants | 196 | |
▷ Global constants | 12 | 6.12% |
▷ Class constants | 184 | 93.88% |
▷ Public constants | 184 | 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
PNG images were not found in this plugin