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
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.08MB] [CPU: ▼0.30ms] Passed 4 tests
An overview of server-side resources used by Recent Tweets Widget
No issues were detected with server-side resource usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.55 ▲0.08 | 41.04 ▼0.90 |
| Dashboard /wp-admin | 3.39 ▲0.08 | 48.40 ▼1.72 |
| Posts /wp-admin/edit.php | 3.50 ▲0.15 | 53.07 ▲0.86 |
| Add New Post /wp-admin/post-new.php | 5.97 ▲0.08 | 98.22 ▲6.32 |
| Media Library /wp-admin/upload.php | 3.31 ▲0.08 | 35.34 ▲0.54 |
| Recent Tweets /wp-admin/admin.php?page=recent-tweets | 3.29 | 33.78 |
| AppSumo /wp-admin/admin.php?page=recent_tweets_go_appsumo_pro | 3.11 | 27.17 |
| Other Tools /wp-admin/admin.php?page=recent-tweets-plugin-other-tools | 3.28 | 30.73 |
Server storage [IO: ▲0.30MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
There were no storage issued detected upon installing this plugin
Filesystem: 26 new files
Database: no new tables, 8 new options
| New WordPress options |
|---|
| tp_twitter_global_notification |
| widget_tp_widget_recent_tweets |
| can_compress_scripts |
| widget_theysaidso_widget |
| widget_recent-comments |
| widget_recent-posts |
| db_upgraded |
| theysaidso_admin_options |
Browser metrics Passed 4 tests
Checking browser requirements for Recent Tweets Widget
This plugin has a minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,829 ▲68 | 14.08 ▼0.20 | 1.86 ▲0.29 | 30.89 ▼17.94 |
| Dashboard /wp-admin | 2,233 ▲56 | 5.59 ▲0.00 | 84.02 ▼6.00 | 41.22 ▼3.88 |
| Posts /wp-admin/edit.php | 2,141 ▲41 | 1.98 ▼0.05 | 41.47 ▲4.73 | 37.60 ▼3.48 |
| Add New Post /wp-admin/post-new.php | 1,566 ▲38 | 24.87 ▲1.50 | 627.39 ▲12.00 | 70.52 ▲23.45 |
| Media Library /wp-admin/upload.php | 1,438 ▲38 | 4.24 ▲0.18 | 101.55 ▼2.16 | 47.67 ▲0.76 |
| Recent Tweets /wp-admin/admin.php?page=recent-tweets | 972 | 2.04 | 23.59 | 52.01 |
| AppSumo /wp-admin/admin.php?page=recent_tweets_go_appsumo_pro | 1,348 | 14.15 | 568.74 | 162.45 |
| Other Tools /wp-admin/admin.php?page=recent-tweets-plugin-other-tools | 1,010 | 2.01 | 26.55 | 40.56 |
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
- Zombie WordPress options were found after uninstall: 7 options
- widget_theysaidso_widget
- db_upgraded
- widget_recent-posts
- widget_recent-comments
- theysaidso_admin_options
- widget_tp_widget_recent_tweets
- can_compress_scripts
Smoke tests 25% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
Good news, no errors were detected
SRP 0% from 2 tests
🔹 Tests weight: 20 | SRP (Single-Responsibility Principle) - PHP files must act as libraries and never output text or perform any action when accessed directly in a browser
Almost there! Just fix the following items
- 2× GET requests to PHP files return non-empty strings:
- > /wp-content/plugins/recent-tweets-widget/appsumo-capture-form.php
- > /wp-content/plugins/recent-tweets-widget/recent-tweets.php
- 4× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Uncaught Error: Class 'WP_Widget' not found in wp-content/plugins/recent-tweets-widget/widget.php:4
- > PHP Fatal error
Uncaught Error: Call to undefined function add_thickbox() in wp-content/plugins/recent-tweets-widget/settings.php:2
- > PHP Fatal error
Uncaught Error: Call to undefined function add_thickbox() in wp-content/plugins/recent-tweets-widget/other_tools.php:2
- > PHP Fatal error
Uncaught Error: Call to undefined function add_thickbox() in wp-content/plugins/recent-tweets-widget/other_plugins.php:1
- > PHP Fatal error
User-side errors 0% from 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
There are user-side issues you should fix
- > GET request to /wp-admin/admin.php?page=recent_tweets_go_appsumo_pro
- > Network (severe)
https://appsumo.com/tools/wordpress/?utm_source=sumo&utm_medium=wp-widget&utm_campaign=recent_tweets - Failed to load resource: the server responded with a status of 404 ()
- > GET request to /wp-admin/admin.php?page=recent_tweets_go_appsumo_pro
- > Javascript (severe) in unknown
https://appsumo2-cdn.appsumo.com/static/dist/js/vue_bridge.61ea1a9c.js 6:75186 Uncaught TypeError: (void 0) is not a function
- > GET request to /wp-admin/admin.php?page=recent_tweets_go_appsumo_pro
- > Console-api (warning) in unknown
https://accounts.google.com/gsi/client 41:457 "[GSI_LOGGER]: Relative login_uri was provided. Use absolute url instead. Relative login_uri may be considered invalid in the future."
Optimizations
Plugin configuration 93% from 29 tests
readme.txt Passed 16 tests
The readme.txt file uses markdown syntax to describe your plugin to the world
7 plugin tags: cache, recent tweets, tweets, social media, twitter api v11...
recent-tweets-widget/recent-tweets.php 85% from 13 tests
The principal PHP file in "Recent Tweets Widget" v. 1.6.8 is loaded by WordPress automatically on each request
You should first fix the following items:
- Description: If Twitter did it, so should we! Keep the description under 140 characters (currently 322 characters long)
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("recent-tweets-widget.php" instead of "recent-tweets.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short review of files and their extensions; it is not recommended to include executable files
No dangerous file extensions were detected1,551 lines of code in 16 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 8 | 277 | 364 | 1,016 |
| CSS | 3 | 38 | 10 | 344 |
| SVG | 3 | 0 | 2 | 104 |
| PO File | 1 | 31 | 31 | 80 |
| JavaScript | 1 | 0 | 0 | 7 |
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.31 |
| Average class complexity | 8.77 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 29.00 |
| Average method complexity | 2.18 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 9.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 | 15 | |
| ▷ Named functions | 15 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 2 | |
| ▷ Global constants | 2 | 100.00% |
| ▷ Class constants | 0 | 0.00% |
| ▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
Often times overlooked, PNG files can occupy unnecessary space in your plugin
8 PNG files occupy 0.22MB with 0.10MB in potential savings
Potential savings
| Compression of 5 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/icon-128x128.png | 12.40KB | 8.62KB | ▼ 30.46% |
| assets/screenshot-1.png | 60.91KB | 34.65KB | ▼ 43.10% |
| assets/screenshot-2.png | 42.32KB | 16.22KB | ▼ 61.67% |
| assets/icon-256x256.png | 35.59KB | 26.00KB | ▼ 26.96% |
| assets/banner-772x250.png | 63.24KB | 28.90KB | ▼ 54.30% |