Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
Install script ran successfully
Server metrics [RAM: ▲0.05MB] [CPU: ▼1.53ms] Passed 4 tests
This is a short check of server-side resources used by Turbo SMS
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.77 ▲0.04 | 43.12 ▼2.90 |
Dashboard /wp-admin | 3.62 ▲0.05 | 49.42 ▼7.84 |
Posts /wp-admin/edit.php | 3.73 ▲0.05 | 53.74 ▲1.97 |
Add New Post /wp-admin/post-new.php | 6.20 ▲0.05 | 101.15 ▲3.89 |
Media Library /wp-admin/upload.php | 3.54 ▲0.05 | 41.35 ▲2.64 |
Turbo SMS /wp-admin/options-general.php?page=turbo_sms | 3.48 | 34.67 |
Server storage [IO: ▲0.25MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
This plugin was installed successfully
Filesystem: 9 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_recent-comments |
theysaidso_admin_options |
widget_recent-posts |
widget_theysaidso_widget |
can_compress_scripts |
db_upgraded |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Turbo SMS
Minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,795 ▲9 | 14.34 ▼0.04 | 1.85 ▼0.18 | 45.48 ▲2.68 |
Dashboard /wp-admin | 2,204 ▲24 | 5.64 ▲0.07 | 90.81 ▼1.50 | 36.88 ▼8.81 |
Posts /wp-admin/edit.php | 2,106 ▼0 | 2.04 ▼0.00 | 39.89 ▲1.38 | 36.05 ▲2.19 |
Add New Post /wp-admin/post-new.php | 1,531 ▲5 | 17.53 ▼0.18 | 684.69 ▲4.06 | 51.56 ▼5.68 |
Media Library /wp-admin/upload.php | 1,409 ▲9 | 4.23 ▲0.01 | 98.87 ▼6.51 | 45.65 ▼1.80 |
Turbo SMS /wp-admin/options-general.php?page=turbo_sms | 973 | 2.02 | 21.32 | 53.30 |
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
It is recommended to fix the following
- The uninstall procedure has failed, leaving 6 options in the database
- widget_recent-comments
- widget_theysaidso_widget
- can_compress_scripts
- widget_recent-posts
- theysaidso_admin_options
- db_upgraded
Smoke tests 50% from 4 tests
Server-side errors 0% from 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
Please fix the following server-side errors
- 12 occurences, only the last one shown
- > GET request to /wp-admin/options-general.php?page=turbo_sms
- > Notice in wp-content/plugins/turbo-sms/admin.php+255
Trying to access array offset on value of type bool
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
Please fix the following items
- 3× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/turbo-sms/admin.php:6
- > PHP Fatal error
Uncaught Error: Call to undefined function plugin_dir_path() in wp-content/plugins/turbo-sms/turbo-sms.php:17
- > PHP Fatal error
Uncaught Error: Call to undefined function apply_filters() in wp-content/plugins/turbo-sms/woocommerce.php:5
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the browser (console and network errors and warnings)
No browser issues were found
Optimizations
Plugin configuration 97% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file is undoubtedly the most important file in your plugin, preparing it for public listing on WordPress.org
Attributes that need to be fixed:
- Screenshots: Please add images for these screenshots: #1 (/assets/Plugin Interface.png), #2 (/assets/API KEY.png)
turbo-sms/turbo-sms.php Passed 13 tests
Analyzing the main PHP file in "Turbo SMS" version 2.0
63 characters long description:
Add Instant Order Status SMS Notifications Feature To Your Site
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short check of programming languages and file extensions; no executable files are allowed
Everything looks great! No dangerous files found in this plugin390 lines of code in 6 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 5 | 97 | 21 | 285 |
CSS | 1 | 18 | 0 | 105 |
PHP code Passed 2 tests
Cyclomatic complexity and code structure are the fingerprint of this plugin
Everything seems fine, there were no complexity issues found
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.09 |
Average class complexity | 0.00 |
▷ Minimum class complexity | 0.00 |
▷ Maximum class complexity | 0.00 |
Average method complexity | 0.00 |
▷ Minimum method complexity | 0.00 |
▷ Maximum method complexity | 0.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 0 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 0 | 0.00% |
▷ Final classes | 0 | 0.00% |
Methods | 0 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 0 | 0.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 22 | |
▷ Named functions | 22 | 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
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
2 PNG files occupy 0.23MB with 0.16MB in potential savings
Potential savings
Compression of 2 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
assets/API KEY.png | 109.46KB | 34.06KB | ▼ 68.88% |
assets/Plugin Interface.png | 127.34KB | 39.49KB | ▼ 68.99% |