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
This plugin's installer ran successfully
Server metrics [RAM: ▲0.07MB] [CPU: ▼6.05ms] Passed 4 tests
A check of server-side resources used by Captain Up
Normal server usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.55 ▲0.09 | 36.97 ▼1.30 |
Dashboard /wp-admin | 3.39 ▲0.04 | 43.54 ▼17.41 |
Posts /wp-admin/edit.php | 3.50 ▲0.15 | 49.98 ▲4.95 |
Add New Post /wp-admin/post-new.php | 5.97 ▲0.08 | 91.73 ▼9.46 |
Media Library /wp-admin/upload.php | 3.31 ▲0.08 | 35.29 ▲3.99 |
Server storage [IO: ▲0.48MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
This plugin installed successfully
Filesystem: 23 new files
Database: no new tables, 7 new options
New WordPress options |
---|
widget_theysaidso_widget |
widget_recent-comments |
widget_recent-posts |
db_upgraded |
theysaidso_admin_options |
can_compress_scripts |
widget_cptup_widget |
Browser metrics Passed 4 tests
An overview of browser requirements for Captain Up
This plugin has a minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,816 ▲70 | 14.47 ▲0.15 | 1.61 ▼0.17 | 39.41 ▼3.04 |
Dashboard /wp-admin | 2,219 ▲37 | 5.79 ▼0.09 | 93.44 ▼13.87 | 40.02 ▼3.68 |
Posts /wp-admin/edit.php | 2,105 ▲16 | 2.06 ▲0.01 | 39.93 ▲1.16 | 35.01 ▲2.21 |
Add New Post /wp-admin/post-new.php | 1,549 ▲7 | 23.58 ▲5.09 | 609.55 ▲10.03 | 57.72 ▲6.37 |
Media Library /wp-admin/upload.php | 1,401 ▲16 | 4.19 ▲0.02 | 93.05 ▼6.42 | 43.58 ▼2.56 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
These items require your attention
- This plugin does not fully uninstall, leaving 7 options in the database
- widget_theysaidso_widget
- theysaidso_admin_options
- db_upgraded
- widget_recent-comments
- can_compress_scripts
- widget_cptup_widget
- widget_recent-posts
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
Good news, no errors were detected
SRP 50% 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
Almost there! Just fix the following items
- 1× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_filter() in wp-content/plugins/captain-up/captainup.php:36
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
There were no browser issues found
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 94% from 16 tests
Don't ignore readme.txt as it is the file that instructs WordPress.org on how to present your plugin to the world
Attributes that need to be fixed:
- Tags: Please delete some tags, you are using 12 tag instead of maximum 10
captain-up/captainup.php 85% from 13 tests
The primary PHP file in "Captain Up" version 3.0.10 is used by WordPress to initiate all plugin functionality
You should first fix the following items:
- Description: If Twitter did it, so should we! Keep the description under 140 characters (currently 253 characters long)
- Main file name: Please rename the main PHP file in this plugin to the plugin slug ("captain-up.php" instead of "captainup.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short check of programming languages and file extensions; no executable files are allowed
No dangerous file extensions were detected1,383 lines of code in 9 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 5 | 133 | 267 | 593 |
CSS | 1 | 40 | 41 | 558 |
Markdown | 1 | 118 | 0 | 127 |
JavaScript | 2 | 26 | 90 | 105 |
PHP code Passed 2 tests
This plugin's cyclomatic complexity and code structure detailed below
There are no cyclomatic complexity problems detected for this plugin
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.34 |
Average class complexity | 7.00 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 12.00 |
Average method complexity | 2.64 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 11.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 3 | |
▷ Abstract classes | 1 | 33.33% |
▷ Concrete classes | 2 | 66.67% |
▷ Final classes | 0 | 0.00% |
Methods | 11 | |
▷ Static methods | 7 | 63.64% |
▷ Public methods | 11 | 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 | 4 | |
▷ Global constants | 0 | 0.00% |
▷ Class constants | 4 | 100.00% |
▷ Public constants | 4 | 100.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
12 PNG files occupy 0.35MB with 0.20MB in potential savings
Potential savings
Compression of 5 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
img/getting-started-points.png | 14.33KB | 5.23KB | ▼ 63.49% |
img/cptup_logo_64.png | 3.58KB | 1.63KB | ▼ 54.39% |
banner-1544x500.png | 76.74KB | 35.33KB | ▼ 53.96% |
banner-772x250.png | 20.28KB | 8.67KB | ▼ 57.23% |
img/grandpa-captain.png | 47.86KB | 20.90KB | ▼ 56.33% |