Benchmarks
Plugin footprint 40% from 16 tests
Installer 0% from 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
You still need to fix the following installer errors
- Install procedure had errors
- > Deprecated in wp-content/plugins/feed-reading-blogroll/feedreading_blogroll.php+2482
Methods with the same name as their class will not be constructors in a future version of PHP; FeedReadingBlogrollWidget has a deprecated constructor
Server metrics [RAM: ▼0.98MB] [CPU: ▼50.72ms] Passed 4 tests
Server-side resources used by WP Social Blogroll
This plugin does not affect your website's performance
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.01 ▼0.45 | 6.32 ▼35.16 |
| Dashboard /wp-admin | 3.03 ▼0.31 | 14.63 ▼44.05 |
| Posts /wp-admin/edit.php | 3.04 ▼0.32 | 8.88 ▼33.51 |
| Add New Post /wp-admin/post-new.php | 3.03 ▼2.85 | 8.88 ▼90.15 |
| Media Library /wp-admin/upload.php | 3.03 ▼0.19 | 8.37 ▼27.03 |
Server storage [IO: ▲0.96MB] [DB: ▲0.00MB] 67% from 3 tests
How much does this plugin use your filesystem and database?
Just a few items left to fix
- Illegal file modification found: 1 file (4.53KB) outside of "wp-content/plugins/feed-reading-blogroll/" and "wp-content/uploads/"
- (new file) wp-content/feedreading_blogroll.js
Filesystem: 47 new files
Database: no new tables, 8 new options
| New WordPress options |
|---|
| theysaidso_admin_options |
| widget_feedreadingblogroll |
| feedreading_blogroll_settings |
| db_upgraded |
| widget_theysaidso_widget |
| can_compress_scripts |
| widget_recent-posts |
| widget_recent-comments |
Browser metrics Passed 4 tests
Checking browser requirements for WP Social Blogroll
Normal browser usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,913 ▲167 | 13.66 ▼0.70 | 6.09 ▲4.28 | 36.94 ▼2.10 |
| Dashboard /wp-admin | 2,214 ▲22 | 5.80 ▲0.82 | 96.41 ▼14.55 | 75.38 ▲31.18 |
| Posts /wp-admin/edit.php | 2,097 ▲8 | 1.97 ▼0.06 | 34.83 ▲1.29 | 34.09 ▼2.22 |
| Add New Post /wp-admin/post-new.php | 1,527 ▼1 | 18.27 ▼4.96 | 691.40 ▲13.52 | 59.97 ▲5.61 |
| Media Library /wp-admin/upload.php | 1,393 ▲2 | 4.09 ▼0.06 | 96.63 ▼9.66 | 73.80 ▲30.55 |
| WP Social Blogroll /wp-admin/feedreading_blogroll.php | 26 | 0.44 | 0.09 | 14.09 |
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
Please fix the following items
- Uninstall procedure validation failed for this plugin
- > Deprecated in wp-content/plugins/feed-reading-blogroll/feedreading_blogroll.php+2482
Methods with the same name as their class will not be constructors in a future version of PHP; FeedReadingBlogrollWidget has a deprecated constructor
- This plugin does not fully uninstall, leaving 7 options in the database
- widget_theysaidso_widget
- can_compress_scripts
- widget_recent-posts
- db_upgraded
- widget_feedreadingblogroll
- widget_recent-comments
- theysaidso_admin_options
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
Even though no errors were found, this is by no means 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 take a closer look at the following
- 1× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function get_option() in wp-content/plugins/feed-reading-blogroll/feedreading_blogroll.php:46
- > PHP Fatal error
User-side errors 0% from 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the browser (console and network errors and warnings)
Please fix the following user-side errors
- > GET request to /wp-admin/feedreading_blogroll.php
- > Network (severe)
wp-admin/feedreading_blogroll.php - Failed to load resource: the server responded with a status of 404 (Not Found)
Optimizations
Plugin configuration 87% from 29 tests
readme.txt 88% 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
Please fix the following attributes:
- Tags: Please reduce the number of tags, currently 19 tag instead of maximum 10
- Screenshots: Please add images for these screenshots: #1 (This is an example of what the Blogroll might look like, when you have installed this plugin. Notice that the entries are sorted by the latest update of the bookmark.), #2 (This is a screenshot of the settings-page. It shows the Options-tab. Notice that you can change the order of the categories by draggging and dropping them with your mouse.), #3 (This is a screenshot of the remaining settings you can perform.), #4 (Use snapshot-services like snap.com with WP Social Blogroll.)
feed-reading-blogroll/feedreading_blogroll.php 85% from 13 tests
The main file in "WP Social Blogroll" v. 1.5.9.2 serves as a complement to information provided in readme.txt and as the entry point to the plugin
The following require your attention:
- Description: Please don't use more than 140 characters for the plugin description (currently 148 characters long)
- Main file name: It is recommended to name the main PHP file as the plugin slug ("feed-reading-blogroll.php" instead of "feedreading_blogroll.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
No dangerous file extensions were detected7,574 lines of code in 25 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PO File | 16 | 1,851 | 2,804 | 4,138 |
| PHP | 2 | 224 | 364 | 2,288 |
| JavaScript | 4 | 144 | 193 | 998 |
| CSS | 2 | 42 | 98 | 123 |
| XML | 1 | 0 | 0 | 27 |
PHP code Passed 2 tests
Analyzing logical lines of code, cyclomatic complexity, and other code metrics
This plugin has no cyclomatic complexity issues
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.34 |
| Average class complexity | 22.00 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 63.00 |
| Average method complexity | 6.25 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 24.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 3 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 3 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 12 | |
| ▷ Static methods | 1 | 8.33% |
| ▷ Public methods | 6 | 50.00% |
| ▷ Protected methods | 6 | 50.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 39 | |
| ▷ Named functions | 39 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 9 | |
| ▷ Global constants | 7 | 77.78% |
| ▷ Class constants | 2 | 22.22% |
| ▷ Public constants | 2 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
All PNG images should be compressed to minimize bandwidth usage for end users
4 PNG files occupy 0.18MB with 0.09MB in potential savings
Potential savings
| Compression of 4 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| screenshot-1.png | 9.40KB | 5.73KB | ▼ 39.05% |
| screenshot-2.png | 50.17KB | 25.30KB | ▼ 49.57% |
| screenshot-3.png | 36.26KB | 22.57KB | ▼ 37.77% |
| screenshot-4.png | 92.56KB | 34.44KB | ▼ 62.80% |