Benchmarks
Plugin footprint 65% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
The plugin installed gracefully, with no errors
Server metrics [RAM: ▼0.90MB] [CPU: ▼33.51ms] Passed 4 tests
An overview of server-side resources used by TweetButton
This plugin has minimal impact on server resources
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.48 ▲0.01 | 37.07 ▼3.96 |
| Dashboard /wp-admin | 3.04 ▼0.26 | 26.12 ▼23.83 |
| Posts /wp-admin/edit.php | 3.04 ▼0.31 | 22.15 ▼28.54 |
| Add New Post /wp-admin/post-new.php | 3.04 ▼2.84 | 23.43 ▼74.04 |
| Media Library /wp-admin/upload.php | 3.04 ▼0.18 | 28.05 ▼7.64 |
Server storage [IO: ▲0.45MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
The plugin installed successfully
Filesystem: 6 new files
Database: no new tables, 17 new options
| New WordPress options |
|---|
| widget_recent-posts |
| tb_display_page |
| widget_theysaidso_widget |
| tb_rss_where |
| theysaidso_admin_options |
| tb_style |
| tb_hashtag |
| tb_ping |
| tb_lang |
| tb_where |
| ... |
Browser metrics Passed 4 tests
TweetButton: 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,830 ▲44 | 13.24 ▼1.51 | 1.65 ▼0.93 | 37.79 ▼4.86 |
| Dashboard /wp-admin | 2,221 ▲18 | 4.98 ▲0.11 | 112.50 ▼9.34 | 82.61 ▲35.87 |
| Posts /wp-admin/edit.php | 2,121 ▲21 | 1.97 ▼0.00 | 38.77 ▼1.59 | 33.90 ▼3.92 |
| Add New Post /wp-admin/post-new.php | 1,693 ▲148 | 22.50 ▼0.73 | 789.96 ▲160.81 | 59.34 ▲0.67 |
| Media Library /wp-admin/upload.php | 1,412 ▲12 | 4.13 ▼0.07 | 110.37 ▲0.79 | 73.78 ▲28.79 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 50% from 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
It is recommended to fix the following
- This plugin cannot be uninstalled
- > User deprecated in wp-includes/functions.php+5737
Function has_cap was called with an argument that is deprecated since version 2.0.0! Usage of user levels is deprecated. Use capabilities instead.
- This plugin does not fully uninstall, leaving 17 options in the database
- widget_theysaidso_widget
- can_compress_scripts
- tb_rss_where
- tb_via
- tb_display_rss
- tb_related
- tb_ping
- tb_display_page
- tb_lang
- tb_where
- ...
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
Good news, no errors were detected
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
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 is_admin() in wp-content/plugins/tweetbutton-for-wordpress/tweetbutton.php:308
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the browser (console and network errors and warnings)
Everything seems fine on the user side
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 94% from 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
Attributes that need to be fixed:
- Screenshots: Please add images for these screenshots: #1 (TweetButton Settings Page), #2 (TweetButton)
tweetbutton-for-wordpress/tweetbutton.php 92% from 13 tests
The main file in "TweetButton" v. 3.1.0 serves as a complement to information provided in readme.txt and as the entry point to the plugin
You should first fix the following items:
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("tweetbutton-for-wordpress.php" instead of "tweetbutton.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | There should be no dangerous file extensions present in any WordPress plugin
Success! There were no dangerous files found in this plugin266 lines of code in 1 file:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 1 | 14 | 52 | 266 |
PHP code Passed 2 tests
Analyzing logical lines of code, cyclomatic complexity, and other code metrics
All good! No complexity issues found
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.47 |
| Average class complexity | 0.00 |
| ▷ Minimum class complexity | 0.00 |
| ▷ Maximum class complexity | 0.00 |
| Average method complexity | 0.00 |
| ▷ Minimum method complexity | 0.00 |
| ▷ Maximum method complexity | 0.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 0 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 0 | 0.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 0 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 0 | 0.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 12 | |
| ▷ Named functions | 12 | 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
Using a strong compression for your PNG files is a great way to speed-up your plugin
4 PNG files occupy 0.44MB with 0.42MB in potential savings
Potential savings
| Compression of 4 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| tweetbutton-icon.png | 47.05KB | 0.44KB | ▼ 99.06% |
| screenshot-2.png | 51.06KB | 1.11KB | ▼ 97.82% |
| images/tweet.png | 52.77KB | 0.84KB | ▼ 98.40% |
| screenshot-1.png | 298.21KB | 47.37KB | ▼ 84.12% |