Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
Install script ran successfully
Server metrics [RAM: ▲0.02MB] [CPU: ▼6.45ms] Passed 4 tests
This is a short check of server-side resources used by JP Important Days Ribbon
This plugin has minimal impact on server resources
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.47 ▲0.01 | 41.60 ▼3.68 |
Dashboard /wp-admin | 3.33 ▲0.02 | 49.74 ▼3.73 |
Posts /wp-admin/edit.php | 3.38 ▲0.02 | 47.33 ▼2.39 |
Add New Post /wp-admin/post-new.php | 5.91 ▲0.02 | 85.76 ▼15.98 |
Media Library /wp-admin/upload.php | 3.25 ▲0.02 | 35.66 ▼1.83 |
Important Days Ribbon Settings /wp-admin/options-general.php?page=jp_important_days_ribbon_settings | 3.25 | 38.12 |
Server storage [IO: ▲0.06MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
There were no storage issued detected upon installing this plugin
Filesystem: 6 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_theysaidso_widget |
db_upgraded |
widget_recent-comments |
theysaidso_admin_options |
can_compress_scripts |
widget_recent-posts |
Browser metrics Passed 4 tests
Checking browser requirements for JP Important Days Ribbon
This plugin renders optimally with no browser resource issues detected
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,818 ▲32 | 14.75 ▲0.54 | 1.94 ▼0.13 | 45.62 ▲0.40 |
Dashboard /wp-admin | 2,202 ▲25 | 5.59 ▼0.02 | 84.82 ▼8.40 | 39.37 ▼5.09 |
Posts /wp-admin/edit.php | 2,104 ▲1 | 1.98 ▲0.01 | 38.80 ▲2.36 | 33.20 ▼2.46 |
Add New Post /wp-admin/post-new.php | 1,529 ▲3 | 23.13 ▲0.10 | 687.19 ▲32.93 | 56.17 ▲3.82 |
Media Library /wp-admin/upload.php | 1,398 ▼2 | 4.27 ▲0.08 | 103.97 ▲4.57 | 45.64 ▼0.42 |
Important Days Ribbon Settings /wp-admin/options-general.php?page=jp_important_days_ribbon_settings | 1,090 | 3.23 | 53.19 | 29.81 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
The following items require your attention
- Zombie WordPress options detected upon uninstall: 6 options
- theysaidso_admin_options
- db_upgraded
- widget_theysaidso_widget
- can_compress_scripts
- widget_recent-posts
- 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 no errors were found, this is by no means an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle applies for WordPress plugins as well - please make sure your PHP files perform no actions when accessed directly
Almost there! Just fix the following items
- 1× PHP files perform the action of outputting non-empty strings when accessed directly:
- > /wp-content/plugins/jp-important-days-ribbon/index.php
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
Everything seems fine on the user side
Optimizations
Plugin configuration 86% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file is undoubtedly the most important file in your plugin, preparing it for public listing on WordPress.org
Attributes that need to be fixed:
- Screenshots: Screenshot #1 (Screenshot-1.jpg) image required
jp-important-days-ribbon/index.php 77% from 13 tests
The main PHP file in "JP Important Days Ribbon" ver. 1.0 adds more information about the plugin and also serves as the entry point for this plugin
Please make the necessary changes and fix the following:
- Description: Keep the plugin description shorter than 140 characters (currently 318 characters long)
- Requires at least: Required version does not match the one declared in readme.txt ("2.6.0" instead of "3.0")
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("jp-important-days-ribbon.php" instead of "index.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is an overview of programming languages used in this plugin; dangerous file extensions are not allowed
Everything looks great! No dangerous files found in this plugin482 lines of code in 3 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 2 | 71 | 70 | 416 |
JavaScript | 1 | 24 | 13 | 66 |
PHP code Passed 2 tests
A short review of cyclomatic complexity and code structure
Everything seems fine, there were no complexity issues found
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.59 |
Average class complexity | 37.00 |
▷ Minimum class complexity | 37.00 |
▷ Maximum class complexity | 37.00 |
Average method complexity | 4.27 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 29.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 | 11 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 10 | 90.91% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 1 | 9.09% |
Functions | 1 | |
▷ Named functions | 1 | 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
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 |
assets/sk.png | 4.75KB | 1.15KB | ▼ 75.70% |