Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.01MB] [CPU: ▼5.05ms] Passed 4 tests
This is a short check of server-side resources used by TweetScroll Widget
This plugin has minimal impact on server resources
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.48 ▲0.02 | 41.04 ▼2.45 |
| Dashboard /wp-admin | 3.32 ▲0.01 | 50.53 ▼2.60 |
| Posts /wp-admin/edit.php | 3.37 ▲0.01 | 49.83 ▼0.13 |
| Add New Post /wp-admin/post-new.php | 5.90 ▲0.01 | 85.51 ▼15.03 |
| Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 36.65 ▲2.77 |
Server storage [IO: ▲0.07MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
No storage issues were detected
Filesystem: 7 new files
Database: no new tables, 7 new options
| New WordPress options |
|---|
| can_compress_scripts |
| widget_recent-posts |
| theysaidso_admin_options |
| widget_recent-comments |
| widget_theysaidso_widget |
| widget_pi_tweet_scroll |
| db_upgraded |
Browser metrics Passed 4 tests
An overview of browser requirements for TweetScroll Widget
Normal browser usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,900 ▲139 | 13.42 ▼0.94 | 8.68 ▲6.38 | 45.90 ▼0.10 |
| Dashboard /wp-admin | 2,198 ▲21 | 5.66 ▲0.12 | 92.22 ▼10.64 | 41.53 ▼1.60 |
| Posts /wp-admin/edit.php | 2,100 ▼0 | 1.97 ▼0.02 | 37.55 ▲0.05 | 36.09 ▲2.04 |
| Add New Post /wp-admin/post-new.php | 1,545 ▲14 | 23.40 ▲0.22 | 619.93 ▼48.14 | 51.81 ▼4.08 |
| Media Library /wp-admin/upload.php | 1,403 ▲6 | 4.22 ▼0.03 | 102.78 ▼9.71 | 42.61 ▼12.04 |
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
The following items require your attention
- Zombie WordPress options were found after uninstall: 7 options
- widget_recent-posts
- widget_theysaidso_widget
- widget_pi_tweet_scroll
- db_upgraded
- widget_recent-comments
- can_compress_scripts
- theysaidso_admin_options
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 | A shallow check of the single-responsibility principle; PHP files should perform no action - including output of placeholder text - and trigger no errors when accessed directly
Please fix the following
- 1× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Call to undefined function untrailingslashit() in wp-content/plugins/tweetscroll-widget/widget-tweetscroll.php:17
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
Everything seems fine on the user side
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file describes your plugin functionality and requirements and it is parsed to prepare the your plugin's listing
Attributes that require attention:
- Donate link: Invalid URI found ("")
tweetscroll-widget/widget-tweetscroll.php 92% from 13 tests
The main PHP file in "TweetScroll Widget" ver. 1.3.7 adds more information about the plugin and also serves as the entry point for this plugin
Please take the time to fix the following:
- Main file name: Please rename the main PHP file in this plugin to the plugin slug ("tweetscroll-widget.php" instead of "widget-tweetscroll.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is an overview of programming languages used in this plugin; dangerous file extensions are not allowed
Success! There were no dangerous files found in this plugin1,250 lines of code in 5 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 3 | 262 | 414 | 983 |
| JavaScript | 1 | 57 | 34 | 240 |
| CSS | 1 | 7 | 1 | 27 |
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.27 |
| Average class complexity | 9.31 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 29.00 |
| Average method complexity | 2.42 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 20.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 | 80 | |
| ▷ Static methods | 10 | 12.50% |
| ▷ Public methods | 69 | 86.25% |
| ▷ Protected methods | 2 | 2.50% |
| ▷ Private methods | 9 | 11.25% |
| Functions | 8 | |
| ▷ Named functions | 8 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 3 | |
| ▷ Global constants | 3 | 100.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
1 PNG file occupies 0.00MB with 0.00MB in potential savings
Potential savings
| Compression of 1 random PNG file using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| img/tweet.png | 1.25KB | 0.50KB | ▼ 59.75% |