Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
This plugin's installer ran successfully
Server metrics [RAM: ▼0.63MB] [CPU: ▼14.72ms] Passed 4 tests
This is a short check of server-side resources used by BTSE's Crypto Widget
This plugin has minimal impact on server resources
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.50 ▲0.04 | 34.84 ▼5.98 |
Dashboard /wp-admin | 3.35 ▲0.04 | 44.82 ▼0.48 |
Posts /wp-admin/edit.php | 3.46 ▲0.10 | 43.66 ▲0.41 |
Add New Post /wp-admin/post-new.php | 3.23 ▼2.66 | 35.71 ▼52.84 |
Media Library /wp-admin/upload.php | 3.27 ▲0.04 | 35.99 ▲1.10 |
BTSE WP Plugin /wp-admin/options-general.php?page=btse-crypto-widget-plugin-settings | 3.24 | 31.78 |
Server storage [IO: ▲2.79MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
No storage issues were detected
Filesystem: 12 new files
Database: no new tables, 6 new options
New WordPress options |
---|
theysaidso_admin_options |
widget_recent-posts |
can_compress_scripts |
db_upgraded |
widget_recent-comments |
widget_theysaidso_widget |
Browser metrics Passed 4 tests
Checking browser requirements for BTSE's Crypto Widget
There were no issues detected in relation to browser resource usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,818 ▲57 | 14.36 ▲0.01 | 1.92 ▼0.14 | 42.78 ▼17.91 |
Dashboard /wp-admin | 2,199 ▲19 | 5.50 ▼0.16 | 82.51 ▼5.29 | 39.17 ▼6.55 |
Posts /wp-admin/edit.php | 2,104 ▲4 | 2.00 ▼0.02 | 34.80 ▼1.58 | 32.12 ▼1.69 |
Add New Post /wp-admin/post-new.php | 1,529 ▼4 | 23.63 ▲0.79 | 637.77 ▼25.91 | 46.88 ▼7.49 |
Media Library /wp-admin/upload.php | 1,401 ▲1 | 4.18 ▼0.01 | 93.39 ▼16.87 | 43.43 ▼4.42 |
BTSE WP Plugin /wp-admin/options-general.php?page=btse-crypto-widget-plugin-settings | 1,257 | 5.40 | 117.23 | 125.07 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
The following items require your attention
- Zombie WordPress options detected upon uninstall: 6 options
- can_compress_scripts
- widget_recent-posts
- theysaidso_admin_options
- widget_theysaidso_widget
- db_upgraded
- widget_recent-comments
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
Even though everything seems fine, this is not 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
The following issues need your attention
- 1× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function register_uninstall_hook() in wp-content/plugins/btses-crypto-widget/index.php:234
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
No browser errors were detected
Optimizations
Plugin configuration 86% from 29 tests
readme.txt Passed 16 tests
The readme.txt file describes your plugin functionality and requirements and it is parsed to prepare the your plugin's listing
7 plugin tags: btse, bitcoin, widget, coin, cryptocurrency...
btses-crypto-widget/index.php 69% from 13 tests
The principal PHP file in "BTSE's Crypto Widget" v. 1.0.2 is loaded by WordPress automatically on each request
It is important to fix the following:
- Main file name: Please rename the main PHP file in this plugin to the plugin slug ("btses-crypto-widget.php" instead of "index.php")
- Text Domain: Since WordPress version 4.6 the text domain is optional; if specified, it must be the same as the plugin slug
- Description: The description should be shorter than 140 characters (currently 348 characters long)
- Domain Path: The domain path is invalid: folder "/languages" does not exist
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are considered dangerous and should not be included with any WordPress plugin
Good job! No executable or dangerous file extensions detected170 lines of code in 3 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 1 | 36 | 33 | 169 |
CSS | 1 | 0 | 8 | 1 |
JavaScript | 1 | 0 | 3 | 0 |
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.16 |
Average class complexity | 12.00 |
▷ Minimum class complexity | 12.00 |
▷ Maximum class complexity | 12.00 |
Average method complexity | 1.79 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 6.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 | 16 | |
▷ Static methods | 1 | 6.25% |
▷ Public methods | 15 | 93.75% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 1 | 6.25% |
Functions | 3 | |
▷ Named functions | 1 | 33.33% |
▷ Anonymous functions | 2 | 66.67% |
Constants | 5 | |
▷ Global constants | 5 | 100.00% |
▷ Class constants | 0 | 0.00% |
▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
PNG files should be compressed to save space and minimize bandwidth usage
1 PNG file occupies 0.40MB with 0.31MB in potential savings
Potential savings
Compression of 1 random PNG file using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
assets/img/imgOverView.png | 407.38KB | 95.03KB | ▼ 76.67% |