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
Install script ran successfully
Server metrics [RAM: ▲0.01MB] [CPU: ▲0.01ms] Passed 4 tests
A check of server-side resources used by TW Recent Posts Widget
This plugin has minimal impact on server resources
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.47 ▲0.01 | 39.63 ▼2.45 |
| Dashboard /wp-admin | 3.32 ▲0.01 | 46.90 ▼2.29 |
| Posts /wp-admin/edit.php | 3.37 ▲0.01 | 48.43 ▲3.26 |
| Add New Post /wp-admin/post-new.php | 5.90 ▲0.01 | 95.99 ▲10.50 |
| Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 35.68 ▲1.53 |
Server storage [IO: ▲0.18MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
This plugin installed successfully
Filesystem: 6 new files
Database: no new tables, 7 new options
| New WordPress options |
|---|
| can_compress_scripts |
| widget_tw-recent-posts |
| widget_theysaidso_widget |
| widget_recent-comments |
| db_upgraded |
| theysaidso_admin_options |
| widget_recent-posts |
Browser metrics Passed 4 tests
Checking browser requirements for TW Recent Posts Widget
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,802 ▲67 | 13.59 ▼0.84 | 1.72 ▼0.56 | 43.62 ▼0.98 |
| Dashboard /wp-admin | 2,209 ▲21 | 5.88 ▲0.95 | 107.32 ▲3.98 | 41.44 ▼4.74 |
| Posts /wp-admin/edit.php | 2,089 ▼0 | 2.02 ▲0.02 | 39.21 ▲1.12 | 35.14 ▲0.61 |
| Add New Post /wp-admin/post-new.php | 1,536 ▲1 | 23.25 ▲0.05 | 578.40 ▼49.21 | 47.47 ▼7.66 |
| Media Library /wp-admin/upload.php | 1,388 ▲3 | 4.19 ▼0.04 | 101.88 ▲0.41 | 40.79 ▼4.30 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
Please fix the following items
- The uninstall procedure has failed, leaving 7 options in the database
- db_upgraded
- widget_recent-comments
- widget_recent-posts
- theysaidso_admin_options
- widget_theysaidso_widget
- can_compress_scripts
- widget_tw-recent-posts
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
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
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 get_option() in wp-content/plugins/tw-recent-posts-widget/tw-recent-posts-widget.php:13
- > 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
Perhaps the most important file in your plugin readme.txt gets parsed in order to generate the public listing of your plugin
These attributes need to be fixed:
- Screenshots: Add an image for screenshot #1 (The widget configuration dialog.2. The widget output based on it's settings)
tw-recent-posts-widget/tw-recent-posts-widget.php 92% from 13 tests
"TW Recent Posts Widget" version 1.0.5's primary PHP file adds more information about the plugin and serves as the entry point for WordPress
You should first fix the following items:
- Description: If Twitter did it, so should we! Keep the description under 140 characters (currently 162 characters long)
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is a short overview of programming languages used in this plugin, detecting executable files
No dangerous file extensions were detected270 lines of code in 2 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 1 | 46 | 41 | 235 |
| CSS | 1 | 10 | 10 | 35 |
PHP code Passed 2 tests
A brief analysis of cyclomatic complexity and code structure for this plugin
This plugin has no cyclomatic complexity problems
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.44 |
| Average class complexity | 60.00 |
| ▷ Minimum class complexity | 60.00 |
| ▷ Maximum class complexity | 60.00 |
| Average method complexity | 10.83 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 29.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 1 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 1 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 6 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 5 | 83.33% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 1 | 16.67% |
| Functions | 1 | |
| ▷ Named functions | 0 | 0.00% |
| ▷ Anonymous functions | 1 | 100.00% |
| Constants | 4 | |
| ▷ Global constants | 4 | 100.00% |
| ▷ Class constants | 0 | 0.00% |
| ▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
2 PNG files occupy 0.15MB with 0.10MB in potential savings
Potential savings
| Compression of 2 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| screenshot-2.png | 96.23KB | 30.60KB | ▼ 68.21% |
| screenshot-1.png | 58.20KB | 18.95KB | ▼ 67.44% |