Benchmarks
Plugin footprint 65% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices
This plugin's installer ran successfully
Server metrics [RAM: ▼1.87MB] [CPU: ▼189.22ms] Passed 4 tests
Analyzing server-side resources used by Portfolio Wall
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 1.76 ▼1.07 | 5.67 ▼28.40 |
Dashboard /wp-admin | 1.78 ▼1.27 | 5.22 ▼46.29 |
Posts /wp-admin/edit.php | 1.78 ▼1.33 | 5.15 ▼36.88 |
Add New Post /wp-admin/post-new.php | 1.78 ▼3.65 | 5.84 ▼645.29 |
Media Library /wp-admin/upload.php | 1.78 ▼1.22 | 5.28 ▼27.26 |
Tags /wp-admin/edit-tags.php?taxonomy=post_tag&post_type=filterable_portfolio | 1.78 | 5.25 |
Categories /wp-admin/edit-tags.php?taxonomy=category&post_type=filterable_portfolio | 1.78 | 5.89 |
All Portfolio /wp-admin/edit.php?post_type=filterable_portfolio | 1.78 | 5.17 |
Add New Portfolio /wp-admin/post-new.php?post_type=filterable_portfolio | 1.78 | 5.60 |
Server storage [IO: ▲0.02MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
There were no storage issued detected upon installing this plugin
Filesystem: 5 new files
Database: no new tables, 1 new option
New WordPress options |
---|
category_children |
Browser metrics Passed 4 tests
Checking browser requirements for Portfolio Wall
This plugin has a minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 3,890 ▲294 | 16.65 ▲1.29 | 14.61 ▲3.98 | 46.22 ▼0.16 |
Dashboard /wp-admin | 3,049 ▲115 | 6.74 ▲0.73 | 145.30 ▼11.77 | 127.10 ▲6.90 |
Posts /wp-admin/edit.php | 2,846 ▲107 | 2.81 ▲0.11 | 69.30 ▲1.63 | 101.33 ▲14.93 |
Add New Post /wp-admin/post-new.php | 1,748 ▲133 | 15.57 ▼5.92 | 419.31 ▲119.22 | 111.95 ▼9.46 |
Media Library /wp-admin/upload.php | 1,834 ▲27 | 5.44 ▲0.40 | 187.23 ▲24.26 | 134.44 ▲9.17 |
Tags /wp-admin/edit-tags.php?taxonomy=post_tag&post_type=filterable_portfolio | 1,922 | 2.69 | 64.17 | 80.15 |
Categories /wp-admin/edit-tags.php?taxonomy=category&post_type=filterable_portfolio | 2,003 | 2.68 | 68.88 | 87.66 |
All Portfolio /wp-admin/edit.php?post_type=filterable_portfolio | 1,570 | 2.64 | 66.76 | 88.16 |
Add New Portfolio /wp-admin/post-new.php?post_type=filterable_portfolio | 3,267 | 9.29 | 226.30 | 155.06 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.01MB] 50% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
You still need to fix the following
- Uninstall procedure had uncaught errors
- > User notice in wp-includes/functions.php+5663
wp_enqueue_style was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the portfolio-wall-main handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- This plugin did not uninstall successfully, leaving 1 option in the database
- category_children
Smoke tests 50% from 4 tests
Server-side errors 0% from 1 test
🔹 Test weight: 20 | This is a short smoke test looking for server-side errors
These server-side errors were triggered
- 5 occurences, only the last one shown
- > GET request to /wp-admin/post-new.php?post_type=filterable_portfolio
- > User notice in wp-includes/functions.php+5663
wp_enqueue_style was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the portfolio-wall-main handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
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
- 1× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/portfolio-wall/portfolio-wall.php:33
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
No browser issues were found
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file describes your plugin functionality and requirements and it is parsed to prepare the your plugin's listing
These attributes need to be fixed:
- Contributors: The plugin contributors field is not present
portfolio-wall/portfolio-wall.php 85% from 13 tests
The main PHP file in "Portfolio Wall" ver. 1.0 adds more information about the plugin and also serves as the entry point for this plugin
It is important to fix the following:
- Description: The description should be shorter than 140 characters (currently 199 characters long)
- Text Domain: If you choose to specify the text domain, it must be the same as the plugin slug; optional since WordPress version 4.6
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is a short overview of programming languages used in this plugin, detecting executable files
Everything looks great! No dangerous files found in this plugin374 lines of code in 3 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 1 | 69 | 45 | 230 |
CSS | 1 | 29 | 4 | 141 |
JavaScript | 1 | 0 | 0 | 3 |
PHP code Passed 2 tests
This is a short overview of cyclomatic complexity and code structure for this plugin
There were no cyclomatic complexity issued detected
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.06 |
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 | 12 | |
▷ Named functions | 12 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 1 | |
▷ Global constants | 1 | 100.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.00MB with 0.00MB in potential savings
Potential savings
Compression of 1 random PNG file using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
images/icon.png | 1.45KB | 0.64KB | ▼ 55.47% |