Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
This plugin's installer ran successfully
Server metrics [RAM: ▲0.00MB] [CPU: ▼4.02ms] Passed 4 tests
Analyzing server-side resources used by WEBSMS.RU WooCommerce
No issues were detected with server-side resource usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.46 ▲0.00 | 38.45 ▼0.65 |
| Dashboard /wp-admin | 3.31 ▲0.00 | 45.53 ▲1.47 |
| Posts /wp-admin/edit.php | 3.36 ▲0.00 | 44.66 ▼4.23 |
| Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 80.31 ▼8.44 |
| Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 33.26 ▼2.75 |
Server storage [IO: ▲0.03MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
The plugin installed successfully
Filesystem: 4 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_recent-posts |
| widget_recent-comments |
| can_compress_scripts |
| db_upgraded |
| theysaidso_admin_options |
| widget_theysaidso_widget |
Browser metrics Passed 4 tests
An overview of browser requirements for WEBSMS.RU WooCommerce
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,825 ▲79 | 13.24 ▼1.34 | 1.81 ▲0.17 | 43.76 ▲3.66 |
| Dashboard /wp-admin | 2,206 ▲15 | 4.87 ▼0.06 | 107.66 ▲4.80 | 42.88 ▲2.93 |
| Posts /wp-admin/edit.php | 2,089 ▼0 | 2.05 ▼0.05 | 39.77 ▼0.24 | 34.53 ▼1.71 |
| Add New Post /wp-admin/post-new.php | 1,531 ▲3 | 23.39 ▲5.30 | 664.27 ▲35.28 | 51.35 ▼3.30 |
| Media Library /wp-admin/upload.php | 1,388 ▼0 | 4.22 ▼0.01 | 93.73 ▼14.02 | 41.13 ▼2.63 |
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
- Zombie WordPress options detected upon uninstall: 6 options
- widget_recent-posts
- theysaidso_admin_options
- db_upgraded
- widget_recent-comments
- can_compress_scripts
- widget_theysaidso_widget
Smoke tests 75% 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: PHP files have to remain inert when accessed directly, throwing no errors and performing no actions
Please take a closer look at the following
- 1× GET requests to PHP files return non-empty strings:
- > /wp-content/plugins/websms-ru-woocommerce/websms_woocommerce.php
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
No browser issues were found
Optimizations
Plugin configuration 96% from 29 tests
readme.txt Passed 16 tests
You should put a lot of thought into formatting readme.txt as it is used by WordPress.org to prepare the public listing of your plugin
4 plugin tags: sms, woocommerce, websms, sms notification
websms-ru-woocommerce/websms_woocommerce.php 92% from 13 tests
The main file in "WEBSMS.RU WooCommerce" v. 1.00 serves as a complement to information provided in readme.txt and as the entry point to the plugin
You should first fix the following items:
- Main file name: Name the main plugin file the same as the plugin slug ("websms-ru-woocommerce.php" instead of "websms_woocommerce.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short review of files and their extensions; it is not recommended to include executable files
Good job! No executable or dangerous file extensions detected430 lines of code in 2 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 2 | 30 | 44 | 430 |
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.49 |
| Average class complexity | 41.00 |
| ▷ Minimum class complexity | 32.00 |
| ▷ Maximum class complexity | 50.00 |
| Average method complexity | 6.00 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 24.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 2 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 2 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 16 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 16 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 2 | |
| ▷ Named functions | 2 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 0 | |
| ▷ Global constants | 0 | 0.00% |
| ▷ Class constants | 0 | 0.00% |
| ▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
Using a strong compression for your PNG files is a great way to speed-up your plugin
1 PNG file occupies 0.01MB with 0.00MB in potential savings
Potential savings
| Compression of 1 random PNG file using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| images/logo_websms.png | 7.99KB | 3.90KB | ▼ 51.14% |