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.01MB] [CPU: ▼8.61ms] Passed 4 tests
A check of server-side resources used by Woo SMS Login Validator
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.46 ▲0.00 | 37.50 ▲2.17 |
| Dashboard /wp-admin | 3.31 ▲0.01 | 44.28 ▼1.66 |
| Posts /wp-admin/edit.php | 3.36 ▲0.01 | 47.53 ▼19.52 |
| Add New Post /wp-admin/post-new.php | 5.89 ▲0.01 | 89.48 ▼15.41 |
| Media Library /wp-admin/upload.php | 3.23 ▲0.01 | 37.85 ▲3.20 |
Server storage [IO: ▲0.62MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
This plugin installed successfully
Filesystem: 12 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_recent-comments |
| widget_recent-posts |
| widget_theysaidso_widget |
| can_compress_scripts |
| theysaidso_admin_options |
| db_upgraded |
Browser metrics Passed 4 tests
A check of browser resources used by Woo SMS Login Validator
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,841 ▲95 | 14.47 ▲0.06 | 1.89 ▲0.27 | 39.95 ▲1.30 |
| Dashboard /wp-admin | 2,222 ▲36 | 4.80 ▼0.16 | 106.11 ▼8.25 | 43.55 ▲4.21 |
| Posts /wp-admin/edit.php | 2,102 ▲6 | 2.04 ▲0.03 | 39.25 ▼0.46 | 36.32 ▼4.25 |
| Add New Post /wp-admin/post-new.php | 1,561 ▲19 | 18.32 ▲0.02 | 609.32 ▼11.30 | 66.25 ▲7.83 |
| Media Library /wp-admin/upload.php | 1,407 ▲22 | 4.19 ▼0.00 | 95.03 ▼5.88 | 42.38 ▼0.79 |
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
- Zombie WordPress options detected upon uninstall: 6 options
- widget_recent-posts
- widget_theysaidso_widget
- theysaidso_admin_options
- can_compress_scripts
- widget_recent-comments
- db_upgraded
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
Good news, no errors were detected
SRP 50% from 2 tests
🔹 Tests weight: 20 | It is important to ensure that your PHP files perform no action when accessed directly, respecting the single-responsibility principle
Please take a closer look at the following
- 1× 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/woo-sms-login-validator/woo-sms-login.php:17
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
There were no browser issues found
Optimizations
Plugin configuration 83% from 29 tests
readme.txt 88% from 16 tests
The readme.txt file is important because it is parsed by WordPress.org for the public listing of your plugin
Please fix the following attributes:
- Screenshots: These screenshots have no corresponding images in /assets: #1 (myaccount login), #2 (checkout login), #3 (插件后台 - General Settings)
- Donate link: Please fix this invalid url: ""
woo-sms-login-validator/woo-sms-login.php 77% from 13 tests
"Woo SMS Login Validator" version 0.5's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
The following require your attention:
- Main file name: It is recommended to name the main PHP file as the plugin slug ("woo-sms-login-validator.php" instead of "woo-sms-login.php")
- Description: If Twitter did it, so should we! Keep the description under 140 characters (currently 159 characters long)
- Text Domain: The text domain follows the same naming rules as the plugin slug: lowercase characters and dashes
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
Good job! No executable or dangerous file extensions detected85 lines of code in 3 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 1 | 8 | 11 | 47 |
| PO File | 1 | 10 | 0 | 36 |
| Markdown | 1 | 1 | 0 | 2 |
PHP code Passed 2 tests
This plugin's cyclomatic complexity and code structure detailed below
No cyclomatic complexity issues were detected for this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.12 |
| 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 | 5 | |
| ▷ Named functions | 5 | 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
6 PNG files occupy 0.32MB with 0.24MB in potential savings
Potential savings
| Compression of 5 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| screenshot-3.png | 80.00KB | 20.75KB | ▼ 74.06% |
| screenshot-1.png | 42.58KB | 10.79KB | ▼ 74.65% |
| images/screenshot-1.png | 42.58KB | 10.79KB | ▼ 74.65% |
| screenshot-2.png | 41.59KB | 10.59KB | ▼ 74.53% |
| images/screenshot-3.png | 80.00KB | 20.75KB | ▼ 74.06% |