Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
Installer ran successfully
Server metrics [RAM: ▲0.02MB] [CPU: ▼3.16ms] Passed 4 tests
Analyzing server-side resources used by WP Image Cropper
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.48 ▲0.02 | 41.39 ▼1.47 |
| Dashboard /wp-admin | 3.32 ▲0.02 | 50.54 ▼0.61 |
| Posts /wp-admin/edit.php | 3.37 ▲0.01 | 48.48 ▼4.33 |
| Add New Post /wp-admin/post-new.php | 5.92 ▲0.03 | 87.47 ▼6.21 |
| Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 45.67 ▲10.56 |
Server storage [IO: ▲1.44MB] [DB: ▲0.07MB] Passed 3 tests
Input-output and database impact of this plugin
There were no storage issued detected upon installing this plugin
Filesystem: 49 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| theysaidso_admin_options |
| widget_recent-comments |
| can_compress_scripts |
| db_upgraded |
| widget_theysaidso_widget |
| widget_recent-posts |
Browser metrics Passed 4 tests
WP Image Cropper: an overview of browser usage
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,937 ▲176 | 13.84 ▼0.82 | 10.21 ▲8.59 | 50.95 ▲6.64 |
| Dashboard /wp-admin | 2,217 ▲42 | 5.78 ▼0.02 | 93.24 ▼16.82 | 40.25 ▼2.75 |
| Posts /wp-admin/edit.php | 2,119 ▲19 | 2.41 ▲0.39 | 37.72 ▲1.09 | 33.71 ▼1.15 |
| Add New Post /wp-admin/post-new.php | 1,701 ▲170 | 23.03 ▼0.15 | 682.07 ▲26.48 | 42.01 ▼14.48 |
| Media Library /wp-admin/upload.php | 1,425 ▲25 | 4.47 ▲0.20 | 102.30 ▲2.89 | 47.24 ▲1.59 |
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 did not uninstall successfully, leaving 6 options in the database
- can_compress_scripts
- widget_theysaidso_widget
- widget_recent-comments
- widget_recent-posts
- db_upgraded
- 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 | 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 task of outputting text when accessed with GET requests:
- > /wp-content/plugins/wp-image-cropper/public/partials/wp-image-cropper-public-display.php
- > /wp-content/plugins/wp-image-cropper/admin/partials/wp-image-cropper-admin-display.php
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
There were no browser issues found
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 81% from 16 tests
The readme.txt file is important because it is parsed by WordPress.org for the public listing of your plugin
These attributes need to be fixed:
- Screenshots: Add descriptions for screenshots #3, #4, #5, #6 in wp-image-cropper/assets to your readme.txt
- Tags: Too many tags (23 tag instead of maximum 10); only the first 5 tags are used in your directory listing
- Requires at least: Version format is invalid
wp-image-cropper/wp-image-cropper.php Passed 13 tests
"WP Image Cropper" version 1.0.0's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
96 characters long description:
This is a short description of what the plugin does. It's displayed in the WordPress admin area.
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | An overview of files in this plugin; executable files are not allowed
No dangerous file extensions were detected2,168 lines of code in 28 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| JavaScript | 7 | 362 | 149 | 1,426 |
| CSS | 9 | 120 | 47 | 588 |
| PHP | 12 | 139 | 951 | 154 |
PHP code Passed 2 tests
An overview of cyclomatic complexity and code structure
All good! No complexity issues found
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.07 |
| Average class complexity | 1.86 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 5.00 |
| Average method complexity | 1.24 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 5.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 | 25 | |
| ▷ Static methods | 2 | 8.00% |
| ▷ Public methods | 20 | 80.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 5 | 20.00% |
| Functions | 3 | |
| ▷ Named functions | 3 | 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
PNG files should be compressed to save space and minimize bandwidth usage
1 PNG file occupies 0.10MB with 0.07MB in potential savings
Potential savings
| Compression of 1 random PNG file using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| admin/img/icon.png | 99.16KB | 23.76KB | ▼ 76.04% |