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 gracefully, with no errors
Server metrics [RAM: ▼0.01MB] [CPU: ▼8.87ms] Passed 4 tests
This is a short check of server-side resources used by Block Specific Spam Woo Orders
This plugin does not affect your website's performance
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.47 ▲0.00 | 49.64 ▲9.80 |
| Dashboard /wp-admin | 3.31 ▼0.04 | 54.08 ▼12.41 |
| Posts /wp-admin/edit.php | 3.37 ▲0.00 | 48.48 ▼2.05 |
| Add New Post /wp-admin/post-new.php | 5.90 ▲0.00 | 84.48 ▼26.92 |
| Media Library /wp-admin/upload.php | 3.24 ▲0.00 | 44.70 ▲5.92 |
Server storage [IO: ▲0.00MB] [DB: ▲0.07MB] Passed 3 tests
A short overview of filesystem and database impact
This plugin installed successfully
Filesystem: 2 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| can_compress_scripts |
| db_upgraded |
| widget_recent-comments |
| widget_recent-posts |
| widget_theysaidso_widget |
| theysaidso_admin_options |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Block Specific Spam Woo Orders
Normal browser usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,789 ▲43 | 14.38 ▼0.29 | 1.81 ▲0.03 | 44.14 ▲1.39 |
| Dashboard /wp-admin | 2,195 ▲15 | 5.64 ▼0.04 | 82.76 ▼7.57 | 40.08 ▼5.54 |
| Posts /wp-admin/edit.php | 2,100 ▼0 | 2.03 ▲0.03 | 35.26 ▼2.97 | 33.77 ▼2.61 |
| Add New Post /wp-admin/post-new.php | 1,526 ▼5 | 17.39 ▼5.90 | 679.54 ▼5.04 | 55.15 ▼1.21 |
| Media Library /wp-admin/upload.php | 1,400 ▲3 | 4.23 ▲0.02 | 113.79 ▲15.37 | 49.13 ▲3.20 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.07MB] 75% from 4 tests
🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
These items require your attention
- This plugin does not fully uninstall, leaving 6 options in the database
- widget_recent-posts
- widget_recent-comments
- db_upgraded
- widget_theysaidso_widget
- can_compress_scripts
- theysaidso_admin_options
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
Good news, no errors were detected
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
Almost there! Just fix the following items
- 1× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Call to undefined function get_option() in wp-content/plugins/block-specific-spam-woo-orders/woo-block-spam-orders.php:17
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
No browser issues were found
Optimizations
Plugin configuration 86% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file uses markdown syntax to describe your plugin to the world
Attributes that require attention:
- Plugin Name: Please replace "Plugin Name" with the name of your plugin on the first line (
=== block-specific-spam-woo-orders ===)
block-specific-spam-woo-orders/woo-block-spam-orders.php 77% from 13 tests
The entry point to "Block Specific Spam Woo Orders" version 0.6 is a PHP file that has certain tags in its header comment area
You should first fix the following items:
- Main file name: The principal plugin file should be the same as the plugin slug ("block-specific-spam-woo-orders.php" instead of "woo-block-spam-orders.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
- Requires at least: The required version number did not match the one declared in readme.txt ("5.1" instead of "4.3")
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 plugin26 lines of code in 1 file:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 1 | 3 | 23 | 26 |
PHP code Passed 2 tests
A short review of cyclomatic complexity and code structure
There are no cyclomatic complexity problems detected for this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.71 |
| 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 | 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
All PNG images should be compressed to minimize bandwidth usage for end users
No PNG files were detected