Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.10MB] [CPU: ▼5.22ms] Passed 4 tests
This is a short check of server-side resources used by WiniShip
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.56 ▲0.09 | 38.72 ▼9.09 |
Dashboard /wp-admin | 3.40 ▲0.09 | 45.85 ▼2.98 |
Posts /wp-admin/edit.php | 3.51 ▲0.15 | 51.13 ▲2.45 |
Add New Post /wp-admin/post-new.php | 6.00 ▲0.11 | 94.85 ▼4.05 |
Media Library /wp-admin/upload.php | 3.32 ▲0.09 | 37.31 ▼4.77 |
Server storage [IO: ▲0.05MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
This plugin installed successfully
Filesystem: 22 new files
Database: no new tables, 7 new options
New WordPress options |
---|
widget_recent-posts |
theysaidso_admin_options |
can_compress_scripts |
db_upgraded |
winiship_settings |
widget_theysaidso_widget |
widget_recent-comments |
Browser metrics Passed 4 tests
An overview of browser requirements for WiniShip
Minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,932 ▲186 | 13.95 ▼0.43 | 8.22 ▲6.30 | 38.79 ▼7.25 |
Dashboard /wp-admin | 2,255 ▲67 | 5.80 ▲0.89 | 97.61 ▼14.40 | 38.53 ▼3.66 |
Posts /wp-admin/edit.php | 2,145 ▲56 | 2.05 ▼0.06 | 45.53 ▲11.80 | 38.54 ▲1.81 |
Add New Post /wp-admin/post-new.php | 1,535 ▲12 | 23.53 ▲0.23 | 606.16 ▼103.52 | 53.77 ▲10.14 |
Media Library /wp-admin/upload.php | 1,440 ▲55 | 4.29 ▲0.08 | 93.48 ▼7.50 | 42.55 ▼1.37 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
It is recommended to fix the following
- Zombie WordPress options were found after uninstall: 6 options
- db_upgraded
- theysaidso_admin_options
- can_compress_scripts
- widget_theysaidso_widget
- widget_recent-comments
- widget_recent-posts
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 | A shallow check of the single-responsibility principle; PHP files should perform no action - including output of placeholder text - and trigger no errors when accessed directly
The following issues need your attention
- 2× PHP files perform the action of outputting non-empty strings when accessed directly:
- > /wp-content/plugins/winiship/admin/partials/wini-ship-admin-display.php
- > /wp-content/plugins/winiship/public/partials/wini-ship-public-display.php
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 94% from 16 tests
It's important to format your readme.txt file correctly as it is parsed for the public listing of your plugin
These attributes need to be fixed:
- Plugin Name: "Plugin Name" should be replaced with the name of your plugin on the first line (
=== winiship ===
)
winiship/wini-ship.php 85% from 13 tests
"WiniShip" version 1.2.0's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
You should first fix the following items:
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("winiship.php" instead of "wini-ship.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
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short glimpse at programming languages used with this plugin and a check that no dangerous files are present
There were no executable files found in this plugin406 lines of code in 16 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 12 | 184 | 574 | 400 |
JavaScript | 2 | 4 | 54 | 6 |
CSS | 2 | 0 | 8 | 0 |
PHP code Passed 2 tests
Analyzing cyclomatic complexity and code structure
All good! No complexity issues found
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.19 |
Average class complexity | 4.29 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 15.00 |
Average method complexity | 1.64 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 7.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 7 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 7 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 37 | |
▷ Static methods | 2 | 5.41% |
▷ Public methods | 32 | 86.49% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 5 | 13.51% |
Functions | 4 | |
▷ Named functions | 3 | 75.00% |
▷ Anonymous functions | 1 | 25.00% |
Constants | 2 | |
▷ Global constants | 2 | 100.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
There were not PNG files found in your plugin