Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.01MB] [CPU: ▼4.85ms] Passed 4 tests
An overview of server-side resources used by Browser Update Ribbon
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.93 ▲0.47 | 40.89 ▼0.36 |
Dashboard /wp-admin | 3.31 ▲0.01 | 44.91 ▼4.75 |
Posts /wp-admin/edit.php | 3.36 ▲0.01 | 41.03 ▼0.80 |
Add New Post /wp-admin/post-new.php | 5.89 ▲0.01 | 77.76 ▼13.48 |
Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 32.95 ▼0.03 |
Update Ribbon /wp-admin/options-general.php?page=browser_update_ribbon_options | 3.24 | 40.46 |
Server storage [IO: ▲0.10MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
This plugin installed successfully
Filesystem: 11 new files
Database: no new tables, 6 new options
New WordPress options |
---|
theysaidso_admin_options |
widget_theysaidso_widget |
db_upgraded |
widget_recent-posts |
widget_recent-comments |
can_compress_scripts |
Browser metrics Passed 4 tests
Checking browser requirements for Browser Update Ribbon
This plugin has a minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,793 ▲32 | 14.19 ▼0.08 | 1.70 ▲0.02 | 42.03 ▼4.31 |
Dashboard /wp-admin | 2,199 ▲22 | 5.60 ▲0.02 | 87.86 ▼14.03 | 42.10 ▼2.65 |
Posts /wp-admin/edit.php | 2,104 ▲4 | 2.00 ▼0.01 | 33.78 ▼1.62 | 33.92 ▼2.29 |
Add New Post /wp-admin/post-new.php | 1,529 ▲3 | 23.54 ▲0.34 | 677.48 ▼11.97 | 66.03 ▲16.19 |
Media Library /wp-admin/upload.php | 1,404 ▲10 | 4.18 ▼0.00 | 93.60 ▼3.90 | 42.46 ▼4.06 |
Update Ribbon /wp-admin/options-general.php?page=browser_update_ribbon_options | 1,274 | 3.01 | 39.96 | 53.60 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
You still need to fix the following
- This plugin did not uninstall successfully, leaving 6 options in the database
- db_upgraded
- can_compress_scripts
- widget_recent-posts
- theysaidso_admin_options
- widget_theysaidso_widget
- widget_recent-comments
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting 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
Please fix the following
- 1× PHP files output non-empty strings when accessed directly via GET requests:
- > /wp-content/plugins/browser-update-ribbon/browser_update_ribbon.php
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 87% from 29 tests
readme.txt 88% from 16 tests
Often overlooked, readme.txt is one of the most important files in your plugin
These attributes need your attention:
- Screenshots: Add a description for screenshot #3 in browser-update-ribbon/assets to your readme.txt
- Tags: Please reduce the number of tags, currently 25 tag instead of maximum 10
browser-update-ribbon/browser_update_ribbon.php 85% from 13 tests
This is the main PHP file of "Browser Update Ribbon" version 1.4.3, providing information about the plugin in the header fields and serving as the principal entry point to the plugin's functions
Please make the necessary changes and fix the following:
- Text Domain: If you choose to specify the text domain, it must be the same as the plugin slug; optional since WordPress version 4.6
- Main file name: It is recommended to name the main PHP file as the plugin slug ("browser-update-ribbon.php" instead of "browser_update_ribbon.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short review of files and their extensions; it is not recommended to include executable files
No dangerous file extensions were detected1,284 lines of code in 6 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 4 | 151 | 351 | 1,133 |
PO File | 1 | 40 | 42 | 110 |
JavaScript | 1 | 6 | 0 | 41 |
PHP code Passed 2 tests
Cyclomatic complexity and code structure are the fingerprint of this plugin
There are no cyclomatic complexity problems detected for this plugin
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.36 |
Average class complexity | 141.00 |
▷ Minimum class complexity | 141.00 |
▷ Maximum class complexity | 141.00 |
Average method complexity | 3.15 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 33.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 | 65 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 21 | 32.31% |
▷ Protected methods | 44 | 67.69% |
▷ Private methods | 0 | 0.00% |
Functions | 9 | |
▷ Named functions | 9 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 58 | |
▷ Global constants | 1 | 1.72% |
▷ Class constants | 57 | 98.28% |
▷ Public constants | 57 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
Often times overlooked, PNG files can occupy unnecessary space in your plugin
2 PNG files occupy 0.02MB with 0.01MB in potential savings
Potential savings
Compression of 2 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
default_ribbon_top.png | 11.72KB | 5.69KB | ▼ 51.43% |
default_ribbon_bottom.png | 12.23KB | 5.86KB | ▼ 52.09% |