Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
Installer ran successfully
Server metrics [RAM: ▲0.00MB] [CPU: ▼4.33ms] Passed 4 tests
A check of server-side resources used by Buddypress Twitter Post
No issues were detected with server-side resource usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.46 ▲0.00 | 38.89 ▼0.95 |
| Dashboard /wp-admin | 3.31 ▲0.00 | 47.45 ▼4.74 |
| Posts /wp-admin/edit.php | 3.36 ▲0.00 | 50.06 ▼1.85 |
| Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 89.40 ▼9.78 |
| Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 39.23 ▲3.25 |
Server storage [IO: ▲0.84MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
No storage issues were detected
Filesystem: 28 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| can_compress_scripts |
| widget_theysaidso_widget |
| theysaidso_admin_options |
| widget_recent-comments |
| db_upgraded |
| widget_recent-posts |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Buddypress Twitter Post
This plugin renders optimally with no browser resource issues detected
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,814 ▲53 | 14.24 ▼0.14 | 1.85 ▲0.10 | 42.10 ▼4.11 |
| Dashboard /wp-admin | 2,192 ▲12 | 5.59 ▼0.03 | 93.88 ▲1.13 | 40.36 ▼2.90 |
| Posts /wp-admin/edit.php | 2,100 ▼0 | 1.94 ▼0.05 | 37.41 ▼5.53 | 34.18 ▼3.63 |
| Add New Post /wp-admin/post-new.php | 1,526 ▼0 | 21.47 ▼1.65 | 663.58 ▼37.45 | 71.47 ▲18.54 |
| Media Library /wp-admin/upload.php | 1,403 ▲6 | 4.17 ▼0.12 | 97.98 ▼4.70 | 42.31 ▼2.91 |
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
- The uninstall procedure has failed, leaving 6 options in the database
- can_compress_scripts
- widget_recent-posts
- widget_recent-comments
- theysaidso_admin_options
- db_upgraded
- widget_theysaidso_widget
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
The smoke test was a success, however most plugin functionality was not tested
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
- 11× GET requests to PHP files have triggered server-side errors or warnings (only 10 are shown):
- > PHP Fatal error
require_once(): Failed opening required 'BP_TWI_POST_PLUGIN_DIR/includes/twitter-api/src/TwitterOAuths.php' (include_path='.:/usr/share/php') in wp-content/plugins/buddypress-twitter-post/includes/twitter_post_action.php on line 2
- > PHP Warning
Use of undefined constant BP_TWI_POST_PLUGIN_DIR - assumed 'BP_TWI_POST_PLUGIN_DIR' (this will throw an Error in a future version of PHP) in wp-content/plugins/buddypress-twitter-post/includes/twitter_setting_action.php on line 2
- > PHP Warning
require_once(BP_TWI_POST_PLUGIN_DIR/includes/twitter-api/autoload.php): failed to open stream: No such file or directory in wp-content/plugins/buddypress-twitter-post/includes/twitter_setting_action.php on line 2
- > PHP Warning
require_once(BP_TWI_POST_PLUGIN_DIR/includes/twitter-api/src/TwitterOAuths.php): failed to open stream: No such file or directory in wp-content/plugins/buddypress-twitter-post/includes/twitter_post_action.php on line 2
- > PHP Warning
Use of undefined constant BP_TWI_POST_PLUGIN_DIR - assumed 'BP_TWI_POST_PLUGIN_DIR' (this will throw an Error in a future version of PHP) in wp-content/plugins/buddypress-twitter-post/includes/twitter_post_action.php on line 2
- > PHP Warning
Use of undefined constant BP_TWI_POST_PLUGIN_DIR - assumed 'BP_TWI_POST_PLUGIN_DIR' (this will throw an Error in a future version of PHP) in wp-content/plugins/buddypress-twitter-post/includes/twitter-api/src/TwitterOAuths.php on line 14
- > PHP Fatal error
require_once(): Failed opening required 'BP_TWI_POST_PLUGIN_DIR/includes/twitter-api/autoload.php' (include_path='.:/usr/share/php') in wp-content/plugins/buddypress-twitter-post/includes/twitter_setting_action.php on line 2
- > PHP Warning
require_once(BP_TWI_POST_PLUGIN_DIR/includes/twitter-api/src/Exception/TwitterException.php): failed to open stream: No such file or directory in wp-content/plugins/buddypress-twitter-post/includes/twitter-api/src/TwitterOAuths.php on line 14
- > PHP Fatal error
Uncaught Error: Class 'Abraham\\TwitterOAuth\\SignatureMethod' not found in wp-content/plugins/buddypress-twitter-post/includes/twitter-api/src/HmacSha1.php:15
- > PHP Fatal error
Uncaught Error: Class 'Abraham\\TwitterOAuth\\Config' not found in wp-content/plugins/buddypress-twitter-post/includes/twitter-api/src/TwitterOAuth.php:16
- > 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 90% 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: These screenshots do not have images: #1 (My Twitter link), #2 (Twitter key setting), #3 (Post on twitter)
buddypress-twitter-post/buddypress_twitter_post.php 85% from 13 tests
The entry point to "Buddypress Twitter Post" version 1.0.0 is a PHP file that has certain tags in its header comment area
The following require your attention:
- Main file name: It is recommended to name the main PHP file as the plugin slug ("buddypress-twitter-post.php" instead of "buddypress_twitter_post.php")
- Requires at least: Please use periods and digits for the required version (ex. "7.0" instead of "WP 4.9.8, BuddyPress 1.5")
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 plugin5,675 lines of code in 22 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| CSS | 1 | 1 | 11 | 4,347 |
| PHP | 21 | 261 | 777 | 1,328 |
PHP code Passed 2 tests
This plugin's cyclomatic complexity and code structure detailed below
No complexity issues detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.31 |
| Average class complexity | 12.38 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 89.00 |
| Average method complexity | 2.49 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 18.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 2 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 13 | |
| ▷ Abstract classes | 1 | 7.69% |
| ▷ Concrete classes | 12 | 92.31% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 101 | |
| ▷ Static methods | 7 | 6.93% |
| ▷ Public methods | 73 | 72.28% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 28 | 27.72% |
| Functions | 9 | |
| ▷ Named functions | 8 | 88.89% |
| ▷ Anonymous functions | 1 | 11.11% |
| Constants | 10 | |
| ▷ Global constants | 6 | 60.00% |
| ▷ Class constants | 4 | 40.00% |
| ▷ Public constants | 4 | 100.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
3 PNG files occupy 0.23MB with 0.13MB in potential savings
Potential savings
| Compression of 3 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| screenshot-2.png | 80.73KB | 35.42KB | ▼ 56.12% |
| screenshot-1.png | 79.26KB | 36.20KB | ▼ 54.33% |
| screenshot-3.png | 75.40KB | 33.35KB | ▼ 55.77% |