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
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.02MB] [CPU: ▼6.92ms] Passed 4 tests
Analyzing server-side resources used by WooCommerce Plivo SMS notifications
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.49 ▲0.02 | 41.70 ▼4.34 |
| Dashboard /wp-admin | 3.33 ▲0.03 | 52.73 ▼4.26 |
| Posts /wp-admin/edit.php | 3.44 ▲0.09 | 51.76 ▼3.46 |
| Add New Post /wp-admin/post-new.php | 5.91 ▲0.02 | 87.99 ▼15.62 |
| Media Library /wp-admin/upload.php | 3.25 ▲0.02 | 37.80 ▲3.24 |
Server storage [IO: ▲0.32MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
This plugin was installed successfully
Filesystem: 40 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| db_upgraded |
| widget_recent-posts |
| widget_recent-comments |
| can_compress_scripts |
| theysaidso_admin_options |
| widget_theysaidso_widget |
Browser metrics Passed 4 tests
A check of browser resources used by WooCommerce Plivo SMS notifications
This plugin renders optimally with no browser resource issues detected
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,800 ▲54 | 14.47 ▲0.47 | 2.04 ▲0.24 | 43.26 ▲0.12 |
| Dashboard /wp-admin | 2,206 ▲15 | 4.85 ▼1.04 | 112.69 ▲8.85 | 40.95 ▼4.19 |
| Posts /wp-admin/edit.php | 2,089 ▼3 | 1.99 ▼0.03 | 36.46 ▼7.38 | 33.52 ▼1.76 |
| Add New Post /wp-admin/post-new.php | 1,533 ▲4 | 23.24 ▲5.03 | 692.71 ▲74.61 | 56.96 ▲1.34 |
| Media Library /wp-admin/upload.php | 1,388 ▼3 | 4.22 ▼0.01 | 93.79 ▼9.96 | 42.86 ▼5.14 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
The following items require your attention
- The uninstall procedure has failed, leaving 6 options in the database
- theysaidso_admin_options
- db_upgraded
- widget_recent-posts
- widget_theysaidso_widget
- widget_recent-comments
- can_compress_scripts
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
Even though no errors were found, this is by no means an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | SRP (Single-Responsibility Principle) - PHP files must act as libraries and never output text or perform any action when accessed directly in a browser
Almost there! Just fix the following items
- 26× PHP files trigger server errors when accessed directly (only 10 are shown):
- > PHP Warning
require_once(HTTP/Request2/SocketWrapper.php): failed to open stream: No such file or directory in wp-content/plugins/woocommerce-plivo/library/HTTP/Request2/SOCKS5.php on line 22
- > PHP Fatal error
require_once(): Failed opening required 'HTTP/Request2/Exception.php' (include_path='.:/usr/share/php') in wp-content/plugins/woocommerce-plivo/library/HTTP/Request2/MultipartBody.php on line 22
- > PHP Warning
require_once(HTTP/Request2.php): failed to open stream: No such file or directory in wp-content/plugins/woocommerce-plivo/library/HTTP/Request2/CookieJar.php on line 22
- > PHP Warning
require_once(HTTP/Request2.php): failed to open stream: No such file or directory in wp-content/plugins/woocommerce-plivo/library/plivo/plivo.php on line 2
- > PHP Warning
require_once(HTTP/Request2/Response.php): failed to open stream: No such file or directory in wp-content/plugins/woocommerce-plivo/library/HTTP/Request2/Adapter.php on line 24
- > PHP Warning
require_once(HTTP/Request2/Exception.php): failed to open stream: No such file or directory in wp-content/plugins/woocommerce-plivo/library/HTTP/Request2/Response.php on line 24
- > PHP Warning
require_once(Net/URL2.php): failed to open stream: No such file or directory in wp-content/plugins/woocommerce-plivo/library/HTTP/Request2.php on line 24
- > PHP Fatal error
require_once(): Failed opening required 'HTTP/Request2/SocketWrapper.php' (include_path='.:/usr/share/php') in wp-content/plugins/woocommerce-plivo/library/HTTP/Request2/SOCKS5.php on line 22
- > PHP Warning
require_once(PEAR/Exception.php): failed to open stream: No such file or directory in wp-content/plugins/woocommerce-plivo/library/HTTP/Request2/Exception.php on line 24
- > PHP Warning
require_once(HTTP/Request2/Exception.php): failed to open stream: No such file or directory in wp-content/plugins/woocommerce-plivo/library/HTTP/Request2/MultipartBody.php on line 22
- > PHP Warning
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration Passed 29 tests
readme.txt Passed 16 tests
The readme.txt file is an important file in your plugin as it is parsed by WordPress.org to prepare the public listing of your plugin
10 plugin tags: support, plivo, status, update, notifications...
woocommerce-plivo/woocommerce-plivo.php Passed 13 tests
The main file in "WooCommerce Plivo SMS notifications" v. 2.1.0 serves as a complement to information provided in readme.txt and as the entry point to the plugin
87 characters long description:
Send SMS update notifications to your customers with this Plivo plugin for WooCommerce.
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | An overview of files in this plugin; executable files are not allowed
Success! There were no dangerous files found in this plugin5,063 lines of code in 33 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 29 | 869 | 3,178 | 4,826 |
| PO File | 1 | 39 | 46 | 123 |
| JavaScript | 2 | 15 | 13 | 65 |
| Markdown | 1 | 18 | 0 | 49 |
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.48 |
| Average class complexity | 18.33 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 199.00 |
| Average method complexity | 3.34 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 44.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 48 | |
| ▷ Abstract classes | 1 | 2.08% |
| ▷ Concrete classes | 47 | 97.92% |
| ▷ Final classes | 1 | 2.13% |
| Methods | 357 | |
| ▷ Static methods | 29 | 8.12% |
| ▷ Public methods | 295 | 82.63% |
| ▷ Protected methods | 38 | 10.64% |
| ▷ Private methods | 24 | 6.72% |
| Functions | 3 | |
| ▷ Named functions | 3 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 31 | |
| ▷ Global constants | 0 | 0.00% |
| ▷ Class constants | 31 | 100.00% |
| ▷ Public constants | 31 | 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
2 PNG files occupy 0.00MB with 0.00MB in potential savings
Potential savings
| Compression of 2 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/images/ok.png | 0.48KB | 0.35KB | ▼ 26.99% |
| assets/images/fail.png | 0.52KB | 0.35KB | ▼ 32.14% |