Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.07MB] [CPU: ▼17.72ms] Passed 4 tests
A check of server-side resources used by WP Twitter widget by rYokiNG
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.77 ▲0.31 | 41.70 ▼2.50 |
| Dashboard /wp-admin | 3.42 ▲0.11 | 36.31 ▼22.49 |
| Posts /wp-admin/edit.php | 3.55 ▲0.19 | 41.11 ▼18.24 |
| Add New Post /wp-admin/post-new.php | 5.66 ▼0.23 | 77.72 ▼27.65 |
| Media Library /wp-admin/upload.php | 3.43 ▲0.19 | 38.75 ▲3.73 |
| WP Twitter Widget Options /wp-admin/options-general.php?page=wptw_options | 3.40 | 33.00 |
Server storage [IO: ▲0.40MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
There were no storage issued detected upon installing this plugin
Filesystem: 8 new files
Database: no new tables, 7 new options
| New WordPress options |
|---|
| theysaidso_admin_options |
| widget_theysaidso_widget |
| can_compress_scripts |
| widget_recent-comments |
| widget_wptw |
| widget_recent-posts |
| db_upgraded |
Browser metrics Passed 4 tests
This is an overview of browser requirements for WP Twitter widget by rYokiNG
This plugin has a minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,803 ▲17 | 14.35 ▼0.18 | 1.81 ▼0.08 | 44.09 ▼2.55 |
| Dashboard /wp-admin | 2,207 ▲33 | 5.55 ▼0.12 | 82.88 ▼11.35 | 39.57 ▲1.66 |
| Posts /wp-admin/edit.php | 2,115 ▲15 | 1.98 ▲0.02 | 39.10 ▲0.18 | 38.06 ▲1.84 |
| Add New Post /wp-admin/post-new.php | 1,537 ▲9 | 23.16 ▲0.29 | 681.92 ▲75.11 | 50.47 ▼7.07 |
| Media Library /wp-admin/upload.php | 1,412 ▲9 | 4.18 ▼0.01 | 96.50 ▼3.67 | 50.01 ▲5.39 |
| WP Twitter Widget Options /wp-admin/options-general.php?page=wptw_options | 1,113 | 2.23 | 41.04 | 35.56 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
Please fix the following items
- This plugin does not fully uninstall, leaving 7 options in the database
- db_upgraded
- widget_recent-posts
- widget_wptw
- can_compress_scripts
- widget_theysaidso_widget
- theysaidso_admin_options
- widget_recent-comments
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=wptw_options
- > Notice in wp-content/plugins/wp-twitter-widget-by-ryoking/wp_twitter_widget_by_ryoking.php+275
Undefined index: wptw_safefrm
- > GET request to /wp-admin/options-general.php?page=wptw_options
- > User deprecated in wp-includes/functions.php+5463
Function screen_icon is deprecated since version 3.8.0 with no alternative available.
- > GET request to /wp-admin/options-general.php?page=wptw_options
- > User deprecated in wp-includes/functions.php+5463
Function get_screen_icon is deprecated since version 3.8.0 with no alternative available.
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 errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/wp-twitter-widget-by-ryoking/wp_twitter_widget_by_ryoking.php:19
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
Everything seems fine on the user side
Optimizations
Plugin configuration 93% 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:
- Plugin Name: Please specify the plugin name on the first line (
=== wp-twitter-widget-by-ryoking ===)
wp-twitter-widget-by-ryoking/wp_twitter_widget_by_ryoking.php 92% from 13 tests
The main file in "WP Twitter widget by rYokiNG" v. 1.1 serves as a complement to information provided in readme.txt and as the entry point to the plugin
It is important to fix the following:
- Main file name: Name the main plugin file the same as the plugin slug ("wp-twitter-widget-by-ryoking.php" instead of "wp_twitter_widget_by_ryoking.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short glimpse at programming languages used with this plugin and a check that no dangerous files are present
Success! There were no dangerous files found in this plugin1,132 lines of code in 4 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 3 | 315 | 396 | 1,114 |
| CSS | 1 | 0 | 0 | 18 |
PHP code Passed 2 tests
An overview of cyclomatic complexity and code structure
Although this was not an exhaustive test, there were no cyclomatic complexity issues detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.31 |
| Average class complexity | 10.15 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 37.00 |
| Average method complexity | 2.55 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 22.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 13 | |
| ▷ Abstract classes | 2 | 15.38% |
| ▷ Concrete classes | 11 | 84.62% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 81 | |
| ▷ Static methods | 10 | 12.35% |
| ▷ Public methods | 70 | 86.42% |
| ▷ Protected methods | 2 | 2.47% |
| ▷ Private methods | 9 | 11.11% |
| Functions | 16 | |
| ▷ Named functions | 16 | 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
All PNG images should be compressed to minimize bandwidth usage for end users
3 PNG files occupy 0.34MB with 0.23MB in potential savings
Potential savings
| Compression of 3 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/screenshot-2.png | 78.32KB | 21.71KB | ▼ 72.28% |
| assets/screenshot-1.png | 226.18KB | 39.72KB | ▼ 82.44% |
| assets/banner-772x250.png | 46.25KB | 25.83KB | ▼ 44.15% |