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: ▼5.04ms] Passed 4 tests
Server-side resources used by Block Plugin Update
Normal server usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.47 ▲0.00 | 39.02 ▼0.53 |
Dashboard /wp-admin | 3.31 ▲0.01 | 45.59 ▼1.55 |
Posts /wp-admin/edit.php | 3.37 ▲0.01 | 46.76 ▲2.35 |
Add New Post /wp-admin/post-new.php | 5.89 ▲0.01 | 83.27 ▼14.98 |
Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 30.72 ▼3.10 |
Block Plugin Update /wp-admin/options-general.php?page=block-specific-plugin-updates/plugin_interface.php | 3.24 | 29.94 |
Server storage [IO: ▲0.15MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
There were no storage issued detected upon installing this plugin
Filesystem: 7 new files
Database: no new tables, 6 new options
New WordPress options |
---|
theysaidso_admin_options |
can_compress_scripts |
widget_recent-comments |
widget_theysaidso_widget |
db_upgraded |
widget_recent-posts |
Browser metrics Passed 4 tests
A check of browser resources used by Block Plugin Update
This plugin has a minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,829 ▲58 | 13.19 ▼1.20 | 1.98 ▲0.02 | 44.26 ▼0.36 |
Dashboard /wp-admin | 2,207 ▲16 | 5.82 ▼0.07 | 101.55 ▼4.55 | 39.03 ▲1.68 |
Posts /wp-admin/edit.php | 2,093 ▲1 | 2.04 ▼0.01 | 34.60 ▼5.60 | 33.13 ▼3.21 |
Add New Post /wp-admin/post-new.php | 1,536 ▲3 | 23.24 ▲0.03 | 628.36 ▲8.76 | 42.39 ▼19.91 |
Media Library /wp-admin/upload.php | 1,392 ▲1 | 4.24 ▲0.07 | 98.65 ▲4.41 | 42.91 ▲0.31 |
Block Plugin Update /wp-admin/options-general.php?page=block-specific-plugin-updates/plugin_interface.php | 1,009 | 2.03 | 25.64 | 25.02 |
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
- can_compress_scripts
- widget_recent-posts
- theysaidso_admin_options
- db_upgraded
- widget_recent-comments
- widget_theysaidso_widget
Smoke tests 25% from 4 tests
Server-side errors 0% from 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
These errors were triggered by the plugin
- > GET request to /wp-admin/options-general.php?page=block-specific-plugin-updates/plugin_interface.php
- > Notice in wp-content/plugins/block-specific-plugin-updates/includes/bspu_plugin_select.php+2
Undefined index: submit-bpu
SRP 0% from 2 tests
🔹 Tests weight: 20 | SRP (Single-Responsibility Principle) - PHP files must act as libraries and never output text or perform any action when accessed directly in a browser
Please take a closer look at the following
- 1× GET requests to PHP files return non-empty strings:
- > /wp-content/plugins/block-specific-plugin-updates/includes/bspu_header.php
- 4× PHP files trigger server errors when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/block-specific-plugin-updates/plugin_interface.php:3
- > PHP Fatal error
Uncaught Error: Call to undefined function add_filter() in wp-content/plugins/block-specific-plugin-updates/block-specific-plugin-updates.php:27
- > PHP Fatal error
Uncaught Error: Call to undefined function admin_url() in wp-content/plugins/block-specific-plugin-updates/includes/bspu_footer.php:51
- > PHP Fatal error
Uncaught Error: Call to undefined function _e() in wp-content/plugins/block-specific-plugin-updates/includes/bspu_plugin_select.php:38
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the browser (console and network errors and warnings)
Everything seems fine on the user side
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 88% from 16 tests
The readme.txt file is an important file in your plugin as it is parsed by WordPress.org to prepare the public listing of your plugin
Please fix the following attributes:
- Requires at least: Version format is invalid
- Screenshots: Screenshot #1 (Admin Setting) image not found
block-specific-plugin-updates/block-specific-plugin-updates.php Passed 13 tests
The entry point to "Block Plugin Update" version 3.3 is a PHP file that has certain tags in its header comment area
105 characters long description:
This plugin blocks the updates for specific plugins. You can select the plugins from plugin setting page.
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are considered dangerous and should not be included with any WordPress plugin
Good job! No executable or dangerous file extensions detected183 lines of code in 5 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 5 | 29 | 21 | 183 |
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.29 |
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
1 PNG file occupies 0.14MB with 0.11MB in potential savings
Potential savings
Compression of 1 random PNG file using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
screenshot-1.png | 139.83KB | 28.04KB | ▼ 79.95% |