Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | All plugins must install correctly, without throwing any errors, warnings, or notices
Installer ran successfully
Server metrics [RAM: ▲0.04MB] [CPU: ▼0.37ms] Passed 4 tests
This is a short check of server-side resources used by Twitter Hashtag Blaster
No issues were detected with server-side resource usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.49 ▲0.03 | 35.22 ▼1.39 |
| Dashboard /wp-admin | 3.35 ▲0.04 | 49.05 ▼0.00 |
| Posts /wp-admin/edit.php | 3.40 ▲0.04 | 47.09 ▼1.06 |
| Add New Post /wp-admin/post-new.php | 5.93 ▲0.04 | 92.14 ▲0.96 |
| Media Library /wp-admin/upload.php | 3.27 ▲0.04 | 35.34 ▲2.61 |
| Twitter Hashtag Blaster /wp-admin/options-general.php?page=twitter_hashtag_blaster | 3.23 | 29.97 |
Server storage [IO: ▲0.74MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
This plugin installed successfully
Filesystem: 10 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| db_upgraded |
| widget_recent-comments |
| can_compress_scripts |
| theysaidso_admin_options |
| widget_recent-posts |
| widget_theysaidso_widget |
Browser metrics Passed 4 tests
Twitter Hashtag Blaster: an overview of browser usage
This plugin renders optimally with no browser resource issues detected
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,804 ▲69 | 14.48 ▲0.10 | 1.69 ▲0.14 | 42.39 ▼2.43 |
| Dashboard /wp-admin | 2,210 ▲25 | 4.81 ▼0.02 | 104.25 ▼14.02 | 38.55 ▼6.33 |
| Posts /wp-admin/edit.php | 2,093 ▲4 | 2.03 ▲0.02 | 34.74 ▼5.36 | 33.32 ▼3.13 |
| Add New Post /wp-admin/post-new.php | 1,545 ▲3 | 23.23 ▲0.21 | 593.17 ▼71.44 | 47.25 ▼5.47 |
| Media Library /wp-admin/upload.php | 1,392 ▲4 | 4.22 ▲0.02 | 94.91 ▼13.94 | 41.53 ▼8.31 |
| Twitter Hashtag Blaster /wp-admin/options-general.php?page=twitter_hashtag_blaster | 726 | 1.53 | 6.78 | 23.49 |
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
- This plugin did not uninstall successfully, leaving 6 options in the database
- widget_recent-posts
- widget_recent-comments
- can_compress_scripts
- db_upgraded
- widget_theysaidso_widget
- theysaidso_admin_options
Smoke tests 50% from 4 tests
Server-side errors 0% from 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
These server-side errors were triggered
- > GET request to /wp-admin/options-general.php?page=twitter_hashtag_blaster
- > Error in wp-admin/includes/template.php+1801
Uncaught ArgumentCountError: Too few arguments to function do_settings_fields(), 1 passed in wp-content/plugins/twitter-hashtag-blaster/templates/settings.php on line 24 and exactly 2 expected in wp-admin/includes/template.php:1801
Stack trace:
#0 wp-content/plugins/twitter-hashtag-blaster/templates/settings.php(24): do_settings_fields()
#1 wp-content/plugins/twitter-hashtag-blaster/settings.php(125): include('/var/www/wordpr...')
#2 wp-includes/class-wp-hook.php(310): Twitter_Hashtag_Blaster_Settings->twitter_hashtag_blaster_settings_page()
#3 wp-includes/class-wp-hook.php(334): WP_Hook->apply_filters()
#4 wp-includes/plugin.php(517): WP_Hook->do_action()
#5 wp-admin/admin.php(259): do_action()
#6 wp-admin/options-general.php(10): require_once('/var/www/wordpr...')
#7 {main}
thrown
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 take a closer look at the following
- 2× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Call to undefined function wp_enqueue_style() in wp-content/plugins/twitter-hashtag-blaster/templates/settings.php:2
- > PHP Fatal error
Uncaught Error: Call to undefined function register_activation_hook() in wp-content/plugins/twitter-hashtag-blaster/twitter_hashtag_blaster.php:158
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
No browser issues were found
Optimizations
Plugin configuration 93% from 29 tests
readme.txt Passed 16 tests
You should put a lot of thought into formatting readme.txt as it is used by WordPress.org to prepare the public listing of your plugin
5 plugin tags: bitly, twitter, traffic, hashtag, shortlink
twitter-hashtag-blaster/twitter_hashtag_blaster.php 85% from 13 tests
The primary PHP file in "Twitter Hashtag Blaster" version 1.0 is used by WordPress to initiate all plugin functionality
The following require your attention:
- Main file name: The principal plugin file should be the same as the plugin slug ("twitter-hashtag-blaster.php" instead of "twitter_hashtag_blaster.php")
- Description: Keep the plugin description shorter than 140 characters (currently 412 characters long)
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 detected262 lines of code in 5 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 4 | 102 | 63 | 249 |
| CSS | 1 | 6 | 0 | 13 |
PHP code Passed 2 tests
This is a short overview of cyclomatic complexity and code structure for this plugin
There are no cyclomatic complexity problems detected for this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.20 |
| Average class complexity | 4.50 |
| ▷ Minimum class complexity | 3.00 |
| ▷ Maximum class complexity | 6.00 |
| Average method complexity | 1.50 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 5.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 2 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 2 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 14 | |
| ▷ Static methods | 2 | 14.29% |
| ▷ Public methods | 14 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 1 | |
| ▷ Named functions | 1 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 2 | |
| ▷ Global constants | 0 | 0.00% |
| ▷ Class constants | 2 | 100.00% |
| ▷ Public constants | 2 | 100.00% |
Plugin size 50% from 2 tests
Image compression 50% from 2 tests
PNG files should be compressed to save space and minimize bandwidth usage
4 PNG files occupy 0.73MB with 0.54MB in potential savings
Potential savings
| Compression of 4 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| img/checkmark.png | 3.17KB | 0.35KB | ▼ 88.93% |
| img/hashtag-blaster-pro-logo.png | 307.33KB | 76.66KB | ▼ 75.06% |
| img/hashtag-blaster-logo.png | 296.92KB | 73.87KB | ▼ 75.12% |
| img/blue-pattern.png | 135.08KB | 57.52KB | ▼ 57.42% |