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.78MB] [CPU: ▼53.59ms] Passed 4 tests
Server-side resources used by Outgrow
This plugin does not affect your website's performance
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 2.21 ▼1.25 | 4.86 ▼43.95 |
Dashboard /wp-admin | 2.23 ▼1.07 | 10.72 ▼41.40 |
Posts /wp-admin/edit.php | 2.23 ▼1.13 | 8.19 ▼38.10 |
Add New Post /wp-admin/post-new.php | 2.23 ▼3.66 | 6.31 ▼90.90 |
Media Library /wp-admin/upload.php | 2.23 ▼1.00 | 6.30 ▼25.31 |
Server storage [IO: ▲1.57MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
There were no storage issued detected upon installing this plugin
Filesystem: 33 new files
Database: 2 new tables, 6 new options
New tables |
---|
wp_outgrow_calci_table |
wp_outgrow_calci_api_table |
New WordPress options |
---|
widget_recent-posts |
can_compress_scripts |
widget_recent-comments |
db_upgraded |
widget_theysaidso_widget |
theysaidso_admin_options |
Browser metrics Passed 4 tests
An overview of browser requirements for Outgrow
This plugin has a minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 3,629 ▲894 | 15.75 ▲1.09 | 15.92 ▲13.98 | 39.86 ▼6.20 |
Dashboard /wp-admin | 2,420 ▲232 | 5.94 ▲1.05 | 105.27 ▼14.50 | 38.67 ▼8.56 |
Posts /wp-admin/edit.php | 2,312 ▲223 | 2.85 ▲0.85 | 40.64 ▲5.16 | 37.70 ▲3.45 |
Add New Post /wp-admin/post-new.php | 1,397 ▼126 | 17.59 ▼5.55 | 594.50 ▼94.31 | 30.84 ▼22.91 |
Media Library /wp-admin/upload.php | 1,603 ▲212 | 5.11 ▲0.90 | 100.26 ▲0.53 | 38.02 ▼7.99 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 50% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
These items require your attention
- Uninstall procedure validation failed for this plugin
- > User notice in wp-includes/functions.php+5905
Function wp_register_script 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 my_plugin_script handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- Zombie WordPress options were found after uninstall: 6 options
- widget_theysaidso_widget
- theysaidso_admin_options
- can_compress_scripts
- widget_recent-posts
- db_upgraded
- widget_recent-comments
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
Even though everything seems fine, this is not an exhaustive test
SRP 0% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle: PHP files have to remain inert when accessed directly, throwing no errors and performing no actions
The following issues need your attention
- 1× PHP files perform the action of outputting non-empty strings when accessed directly:
- > /wp-content/plugins/outgrow/view.php
- 3× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to a member function get_results() on null in wp-content/plugins/outgrow/callingDb.php:3
- > PHP Fatal error
Uncaught Error: Call to undefined function is_admin() in wp-content/plugins/outgrow/outgrow-api.php:22
- > PHP Fatal error
Uncaught Error: Call to a member function get_results() on null in wp-content/plugins/outgrow/cookies.php:3
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
No browser errors were detected
Optimizations
Plugin configuration 90% 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:
- Screenshots: These screenshots need descriptions #5, #6 in outgrow/assets to your readme.txt
- Tags: There are too many tags (13 tag instead of maximum 10)
outgrow/outgrow-api.php 92% from 13 tests
"Outgrow" version 2.0's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
Please make the necessary changes and fix the following:
- Main file name: Please rename the main PHP file in this plugin to the plugin slug ("outgrow.php" instead of "outgrow-api.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is an overview of file extensions present in this plugin and a short test that no dangerous files are bundled with this plugin
Good job! No executable or dangerous file extensions detected19,819 lines of code in 18 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
JavaScript | 4 | 226 | 250 | 12,103 |
CSS | 7 | 233 | 172 | 4,415 |
SVG | 1 | 1 | 3 | 2,624 |
PHP | 5 | 49 | 91 | 565 |
HTML | 1 | 29 | 4 | 112 |
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.38 |
Average class complexity | 5.00 |
▷ Minimum class complexity | 5.00 |
▷ Maximum class complexity | 5.00 |
Average method complexity | 1.80 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 4.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 | 5 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 5 | 100.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 14 | |
▷ Named functions | 14 | 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
All PNG images should be compressed to minimize bandwidth usage for end users
9 PNG files occupy 0.24MB with 0.20MB in potential savings
Potential savings
Compression of 5 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
images/select.png | 2.82KB | 0.18KB | ▼ 93.46% |
images/icon-2.png | 3.15KB | 0.37KB | ▼ 88.34% |
images/icon6.png | 1.07KB | 0.21KB | ▼ 80.35% |
images/logo.png | 3.40KB | 0.74KB | ▼ 78.25% |
images/icon-4.png | 3.15KB | 0.35KB | ▼ 88.93% |