Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
This plugin's installer ran successfully
Server metrics [RAM: ▲0.01MB] [CPU: ▼0.51ms] Passed 4 tests
Server-side resources used by Custom Post Type Sticky
No issues were detected with server-side resource usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.48 ▲0.02 | 44.04 ▲5.03 |
| Dashboard /wp-admin | 3.32 ▲0.02 | 48.46 ▼2.24 |
| Posts /wp-admin/edit.php | 3.37 ▲0.01 | 47.16 ▼2.23 |
| Add New Post /wp-admin/post-new.php | 5.90 ▲0.01 | 115.57 ▲19.27 |
| Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 33.30 ▼2.61 |
Server storage [IO: ▲0.10MB] [DB: ▲0.07MB] Passed 3 tests
A short overview of filesystem and database impact
There were no storage issued detected upon installing this plugin
Filesystem: 11 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_recent-comments |
| widget_theysaidso_widget |
| widget_recent-posts |
| db_upgraded |
| can_compress_scripts |
| theysaidso_admin_options |
Browser metrics Passed 4 tests
Checking browser requirements for Custom Post Type Sticky
This plugin renders optimally with no browser resource issues detected
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,800 ▲65 | 13.25 ▼1.15 | 1.61 ▼0.16 | 41.97 ▼2.54 |
| Dashboard /wp-admin | 2,206 ▲18 | 4.89 ▼1.08 | 122.23 ▲5.60 | 46.63 ▼3.33 |
| Posts /wp-admin/edit.php | 2,089 ▼0 | 2.01 ▼0.05 | 36.09 ▼2.63 | 33.30 ▼2.56 |
| Add New Post /wp-admin/post-new.php | 1,411 ▼126 | 17.91 ▼5.19 | 628.89 ▼51.90 | 54.13 ▲1.02 |
| Media Library /wp-admin/upload.php | 1,388 ▼3 | 4.22 ▼0.04 | 99.05 ▼5.82 | 42.73 ▼4.44 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.07MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
You still need to fix the following
- Zombie WordPress options detected upon uninstall: 6 options
- widget_theysaidso_widget
- can_compress_scripts
- db_upgraded
- widget_recent-posts
- theysaidso_admin_options
- widget_recent-comments
Smoke tests 75% 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 50% 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
Almost there! Just fix the following items
- 1× PHP files trigger server errors when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/custom-post-type-sticky/custom-post-type-sticky.php:17
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file uses markdown syntax to describe your plugin to the world
Attributes that need to be fixed:
- Screenshots: Screenshot #1 (screenshot-2.jpg) image missing
custom-post-type-sticky/custom-post-type-sticky.php 92% from 13 tests
"Custom Post Type Sticky" version 1.2's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
You should first fix the following items:
- Text Domain: The text domain follows the same naming rules as the plugin slug: lowercase characters and dashes
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
No dangerous file extensions were detected142 lines of code in 5 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PO File | 2 | 18 | 18 | 67 |
| PHP | 1 | 11 | 16 | 42 |
| JavaScript | 2 | 10 | 6 | 33 |
PHP code Passed 2 tests
Analyzing logical lines of code, cyclomatic complexity, and other code metrics
Everything seems fine, there were no complexity issues found
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.38 |
| 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 | 2 | |
| ▷ Named functions | 2 | 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
Using a strong compression for your PNG files is a great way to speed-up your plugin
2 PNG files occupy 0.09MB with 0.06MB in potential savings
Potential savings
| Compression of 2 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| screenshot-1.png | 63.82KB | 22.87KB | ▼ 64.17% |
| screenshot-2.png | 26.46KB | 9.62KB | ▼ 63.63% |