Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | All plugins must install correctly, without throwing any errors, warnings, or notices
This plugin's installer ran successfully
Server metrics [RAM: ▲0.03MB] [CPU: ▼4.73ms] Passed 4 tests
This is a short check of server-side resources used by wooSMS Techno71
Normal server usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.49 ▲0.02 | 35.61 ▼5.58 |
Dashboard /wp-admin | 3.33 ▲0.03 | 49.48 ▼9.46 |
Posts /wp-admin/edit.php | 3.38 ▲0.03 | 51.55 ▼4.07 |
Add New Post /wp-admin/post-new.php | 5.91 ▲0.03 | 94.81 ▲2.23 |
Media Library /wp-admin/upload.php | 3.25 ▲0.03 | 36.95 ▲0.19 |
Techno71 SMS Integration /wp-admin/admin.php?page=naims-techno-sms-integration | 3.22 | 34.36 |
Server storage [IO: ▲0.09MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
This plugin was installed successfully
Filesystem: 12 new files
Database: no new tables, 6 new options
New WordPress options |
---|
db_upgraded |
can_compress_scripts |
widget_theysaidso_widget |
widget_recent-posts |
theysaidso_admin_options |
widget_recent-comments |
Browser metrics Passed 4 tests
An overview of browser requirements for wooSMS Techno71
This plugin renders optimally with no browser resource issues detected
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,800 ▲54 | 13.29 ▼0.95 | 1.69 ▼0.06 | 42.20 ▼1.25 |
Dashboard /wp-admin | 2,206 ▲21 | 5.88 ▼0.01 | 103.03 ▼6.53 | 37.78 ▼4.27 |
Posts /wp-admin/edit.php | 2,089 ▼0 | 2.01 ▼0.04 | 39.68 ▲3.41 | 35.91 ▲4.42 |
Add New Post /wp-admin/post-new.php | 1,538 ▲10 | 22.99 ▲4.67 | 652.92 ▲24.50 | 53.39 ▲0.07 |
Media Library /wp-admin/upload.php | 1,388 ▼3 | 4.19 ▼0.02 | 97.87 ▼2.44 | 41.55 ▼0.78 |
Techno71 SMS Integration /wp-admin/admin.php?page=naims-techno-sms-integration | 873 | 2.03 | 22.85 | 26.57 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
Please fix the following items
- Zombie WordPress options were found after uninstall: 6 options
- theysaidso_admin_options
- widget_recent-posts
- can_compress_scripts
- widget_recent-comments
- db_upgraded
- widget_theysaidso_widget
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the server (in the Apache logs)
Everything seems fine, however 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
The following issues need your attention
- 1× PHP files output text when accessed directly:
- > /wp-content/plugins/sms-on-order-place-and-order-status-change/woo-sms-for-order-status.php
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
There were no browser issues found
Optimizations
Plugin configuration 83% from 29 tests
readme.txt 94% from 16 tests
Often overlooked, readme.txt is one of the most important files in your plugin
Attributes that require attention:
- Screenshots: Please add images for these screenshots: #1 (assets/screenshot-1.png), #2 (assets/screenshot-2.png), #3 (assets/screenshot-3.png)
sms-on-order-place-and-order-status-change/woo-sms-for-order-status.php 69% from 13 tests
Analyzing the main PHP file in "wooSMS Techno71" version 1.1
Please make the necessary changes and fix the following:
- Domain Path: The domain path is invalid: folder "/languages" does not exist
- Main file name: The principal plugin file should be the same as the plugin slug ("sms-on-order-place-and-order-status-change.php" instead of "woo-sms-for-order-status.php")
- Text Domain: The text domain is optional since WordPress version 4.6; if you do specify it, it must be the same as the plugin slug
- Description: Please keep the plugin description shorter than 140 characters (currently 159 characters long)
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are considered dangerous and should not be included with any WordPress plugin
No dangerous file extensions were detected162 lines of code in 8 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 8 | 41 | 24 | 162 |
PHP code Passed 2 tests
Cyclomatic complexity and code structure are the fingerprint of this plugin
All good! No complexity issues found
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.19 |
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 | 6 | |
▷ Named functions | 6 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 1 | |
▷ Global constants | 1 | 100.00% |
▷ Class constants | 0 | 0.00% |
▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
Often times overlooked, PNG files can occupy unnecessary space in your plugin
3 PNG files occupy 0.08MB with 0.04MB in potential savings
Potential savings
Compression of 3 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
assets/Screenshot-3.png | 44.50KB | 24.39KB | ▼ 45.20% |
assets/Screenshot-1.png | 24.54KB | 12.79KB | ▼ 47.87% |
assets/Screenshot-2.png | 16.48KB | 9.37KB | ▼ 43.15% |