Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
Install script ran successfully
Server metrics [RAM: ▲0.09MB] [CPU: ▼6.43ms] Passed 4 tests
A check of server-side resources used by picowall
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.57 ▲0.11 | 35.30 ▼4.81 |
Dashboard /wp-admin | 3.40 ▲0.06 | 48.84 ▼13.77 |
Posts /wp-admin/edit.php | 3.52 ▲0.16 | 50.93 ▲1.88 |
Add New Post /wp-admin/post-new.php | 5.99 ▲0.10 | 95.38 ▼8.07 |
Media Library /wp-admin/upload.php | 3.32 ▲0.10 | 37.22 ▲0.92 |
Server storage [IO: ▲0.08MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
The plugin installed successfully
Filesystem: 22 new files
Database: no new tables, 6 new options
New WordPress options |
---|
can_compress_scripts |
db_upgraded |
widget_recent-comments |
widget_theysaidso_widget |
widget_recent-posts |
theysaidso_admin_options |
Browser metrics Passed 4 tests
picowall: an overview of browser usage
There were no issues detected in relation to browser resource usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,789 ▲43 | 14.36 ▲0.10 | 1.54 ▼0.05 | 38.39 ▼2.03 |
Dashboard /wp-admin | 2,189 ▲15 | 5.56 ▼0.11 | 91.30 ▲5.41 | 42.61 ▲0.93 |
Posts /wp-admin/edit.php | 2,100 ▼0 | 2.02 ▼0.00 | 38.72 ▲5.03 | 36.53 ▲0.11 |
Add New Post /wp-admin/post-new.php | 6,244 ▲4,718 | 19.23 ▼3.97 | 945.33 ▲260.85 | 58.31 ▼0.27 |
Media Library /wp-admin/upload.php | 1,400 ▼3 | 4.20 ▲0.00 | 105.22 ▲9.92 | 46.13 ▲5.92 |
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
Please fix the following items
- Zombie WordPress options were found after uninstall: 6 options
- widget_theysaidso_widget
- widget_recent-comments
- can_compress_scripts
- db_upgraded
- theysaidso_admin_options
- widget_recent-posts
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a short smoke test looking for server-side errors
Good news, no errors were detected
SRP 0% 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
Almost there! Just fix the following items
- 1× PHP files output text when accessed directly:
- > /wp-content/plugins/picowall/public/partials/picowall-output-view.php
- 5× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Call to undefined function _e() in wp-content/plugins/picowall/admin/partials/picowall-metabox-view.php:16
- > PHP Notice
Undefined variable: content_type in wp-content/plugins/picowall/public/partials/picowall-output-view.php on line 17
- > PHP Notice
Undefined variable: name in wp-content/plugins/picowall/public/partials/picowall-output-view.php on line 16
- > PHP Notice
Undefined variable: source in wp-content/plugins/picowall/public/partials/picowall-output-view.php on line 14
- > PHP Fatal error
Uncaught Error: Call to undefined function add_shortcode() in wp-content/plugins/picowall/public/picowall-public-functions.php:126
- > PHP Fatal error
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 93% from 29 tests
readme.txt 88% from 16 tests
Perhaps the most important file in your plugin readme.txt gets parsed in order to generate the public listing of your plugin
These attributes need to be fixed:
- Plugin Name: Please replace "Plugin Name" with the name of your plugin on the first line (
=== picowall ===
) - Screenshots: Screenshot #1 (Meta Box) image required
picowall/picowall.php Passed 13 tests
The main PHP file in "picowall" ver. 1.0.0 adds more information about the plugin and also serves as the entry point for this plugin
25 characters long description:
Resize images on the fly.
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are not allowed as they can serve as attack vectors
Everything looks great! No dangerous files found in this plugin682 lines of code in 15 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 14 | 236 | 505 | 647 |
PO File | 1 | 8 | 9 | 35 |
PHP code Passed 2 tests
A brief analysis of cyclomatic complexity and code structure for this plugin
There are no cyclomatic complexity problems detected for this plugin
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.24 |
Average class complexity | 6.38 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 20.00 |
Average method complexity | 2.13 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 11.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 8 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 8 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 38 | |
▷ Static methods | 2 | 5.26% |
▷ Public methods | 26 | 68.42% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 12 | 31.58% |
Functions | 7 | |
▷ Named functions | 7 | 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
No PNG files were detected