Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.03MB] [CPU: ▼10.89ms] Passed 4 tests
Server-side resources used by Portfolio Block - Make and display your portfolio in a professional way
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.51 ▲0.04 | 35.99 ▼5.47 |
Dashboard /wp-admin | 3.34 ▼0.01 | 49.70 ▼15.86 |
Posts /wp-admin/edit.php | 3.39 ▲0.03 | 45.32 ▼3.11 |
Add New Post /wp-admin/post-new.php | 5.95 ▲0.06 | 81.72 ▼19.11 |
Media Library /wp-admin/upload.php | 3.27 ▲0.03 | 36.28 ▲2.39 |
Server storage [IO: ▲1.37MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
The plugin installed successfully
Filesystem: 18 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_recent-posts |
db_upgraded |
theysaidso_admin_options |
can_compress_scripts |
widget_recent-comments |
widget_theysaidso_widget |
Browser metrics Passed 4 tests
Portfolio Block - Make and display your portfolio in a professional way: an overview of browser usage
Normal browser usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,814 ▲68 | 14.24 ▼0.48 | 1.86 ▲0.01 | 37.67 ▼6.38 |
Dashboard /wp-admin | 2,198 ▲17 | 5.56 ▼0.15 | 92.56 ▼11.36 | 42.17 ▼1.17 |
Posts /wp-admin/edit.php | 2,100 ▼0 | 1.99 ▲0.05 | 36.77 ▲0.45 | 33.41 ▼2.60 |
Add New Post /wp-admin/post-new.php | 6,200 ▲4,665 | 19.66 ▲1.45 | 928.34 ▲301.06 | 38.92 ▼25.28 |
Media Library /wp-admin/upload.php | 1,391 ▼0 | 4.21 ▼0.05 | 98.11 ▼2.54 | 41.47 ▲1.43 |
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
You still need to fix the following
- This plugin did not uninstall successfully, leaving 6 options in the database
- widget_recent-comments
- db_upgraded
- can_compress_scripts
- widget_theysaidso_widget
- widget_recent-posts
- 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
The smoke test was a success, however most plugin functionality was not tested
SRP 50% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle applies for WordPress plugins as well - please make sure your PHP files perform no actions when accessed directly
The following issues need your attention
- 2× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/portfolio-block/inc/block.php:4
- > PHP Warning
Use of undefined constant PFB_PLUGIN_VERSION - assumed 'PFB_PLUGIN_VERSION' (this will throw an Error in a future version of PHP) in wp-content/plugins/portfolio-block/dist/editor.asset.php on line 4
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
Everything seems fine on the user side
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 94% from 16 tests
Often overlooked, readme.txt is one of the most important files in your plugin
Attributes that require attention:
- Requires at least: Version not formatted correctly
portfolio-block/index.php 92% from 13 tests
The main file in "Portfolio Block - Make and display your portfolio in a professional way" v. 1.0.3 serves as a complement to information provided in readme.txt and as the entry point to the plugin
You should first fix the following items:
- Main file name: The principal plugin file should be the same as the plugin slug ("portfolio-block.php" instead of "index.php")
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 detected309 lines of code in 11 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
JSON | 2 | 0 | 0 | 153 |
PO File | 1 | 45 | 47 | 108 |
PHP | 3 | 12 | 12 | 42 |
JavaScript | 3 | 1 | 11 | 4 |
CSS | 2 | 0 | 2 | 2 |
PHP code Passed 2 tests
A brief analysis of cyclomatic complexity and code structure for this plugin
Although this was not an exhaustive test, there were no cyclomatic complexity issues detected
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.12 |
Average class complexity | 1.00 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 1.00 |
Average method complexity | 1.00 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 1.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 1 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 1 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 4 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 4 | 100.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 0 | |
▷ Named functions | 0 | 0.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 3 | |
▷ Global constants | 3 | 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
PNG images were not found in this plugin