Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.02MB] [CPU: ▼2.84ms] Passed 4 tests
This is a short check of server-side resources used by Blocks for Discogs
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.49 ▲0.03 | 37.90 ▼11.42 |
| Dashboard /wp-admin | 3.33 ▲0.02 | 46.39 ▼1.42 |
| Posts /wp-admin/edit.php | 3.38 ▲0.02 | 52.92 ▲0.82 |
| Add New Post /wp-admin/post-new.php | 5.91 ▲0.02 | 94.47 ▲2.00 |
| Media Library /wp-admin/upload.php | 3.25 ▲0.02 | 35.80 ▲0.65 |
Server storage [IO: ▲0.04MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
There were no storage issued detected upon installing this plugin
Filesystem: 10 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_recent-comments |
| widget_theysaidso_widget |
| db_upgraded |
| can_compress_scripts |
| theysaidso_admin_options |
| widget_recent-posts |
Browser metrics Passed 4 tests
Blocks for Discogs: an overview of browser usage
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,824 ▲78 | 13.18 ▼1.13 | 1.60 ▼0.28 | 40.14 ▼2.64 |
| Dashboard /wp-admin | 2,223 ▲38 | 5.86 ▲0.04 | 95.89 ▼8.04 | 81.92 ▲40.46 |
| Posts /wp-admin/edit.php | 2,109 ▲20 | 1.98 ▼0.01 | 39.66 ▲0.28 | 36.25 ▲1.63 |
| Add New Post /wp-admin/post-new.php | 6,439 ▲4,911 | 23.50 ▲5.20 | 889.51 ▲243.66 | 37.81 ▼14.65 |
| Media Library /wp-admin/upload.php | 1,408 ▲20 | 4.20 ▲0.01 | 97.52 ▼7.12 | 73.53 ▲29.83 |
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
These items require your attention
- Zombie WordPress options detected upon uninstall: 6 options
- theysaidso_admin_options
- can_compress_scripts
- widget_theysaidso_widget
- db_upgraded
- widget_recent-comments
- widget_recent-posts
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 | It is important to ensure that your PHP files perform no action when accessed directly, respecting the single-responsibility principle
Please fix the following items
- 1× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/blocks-for-discogs/blocks-for-discogs.php:28
- > PHP Fatal error
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
Attributes that need to be fixed:
- Plugin Name: You should set the name of your plugin on the first line (
=== blocks-for-discogs ===)
blocks-for-discogs/blocks-for-discogs.php 85% from 13 tests
The primary PHP file in "Blocks for Discogs" version 1.0.1 is used by WordPress to initiate all plugin functionality
It is important to fix the following:
- 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 PHP: Required version does not match the one declared in readme.txt ("7.0" instead of "7.4")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | There should be no dangerous file extensions present in any WordPress plugin
Everything looks great! No dangerous files found in this plugin421 lines of code in 7 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 3 | 58 | 15 | 252 |
| JavaScript | 2 | 29 | 15 | 155 |
| JSON | 1 | 0 | 0 | 13 |
| CSS | 1 | 0 | 0 | 1 |
PHP code Passed 2 tests
This plugin's cyclomatic complexity and code structure detailed below
Although this was not an exhaustive test, there were no cyclomatic complexity issues detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.32 |
| 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 | 15 | |
| ▷ Named functions | 15 | 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
Often times overlooked, PNG files can occupy unnecessary space in your plugin
2 PNG files occupy 0.02MB with 0.01MB in potential savings
Potential savings
| Compression of 2 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/noimage.png | 15.02KB | 6.17KB | ▼ 58.91% |
| assets/icon.png | 3.38KB | 0.46KB | ▼ 86.46% |