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
- > Notice in wp-content/plugins/twiget/twiget.php+61
Trying to access array offset on value of type bool
Server metrics [RAM: ▼1.71MB] [CPU: ▼46.09ms] Passed 4 tests
An overview of server-side resources used by Twiget Twitter Widget
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 2.28 ▼1.18 | 8.87 ▼31.07 |
| Dashboard /wp-admin | 2.30 ▼1.00 | 10.51 ▼39.22 |
| Posts /wp-admin/edit.php | 2.30 ▼1.06 | 11.90 ▼27.79 |
| Add New Post /wp-admin/post-new.php | 2.30 ▼3.59 | 11.93 ▼86.28 |
| Media Library /wp-admin/upload.php | 2.30 ▼0.93 | 10.87 ▼22.01 |
| Twiget Settings /wp-admin/options-general.php?page=twiget/options.php | 2.30 | 12.16 |
Server storage [IO: ▲0.19MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
There were no storage issued detected upon installing this plugin
Filesystem: 19 new files
Database: no new tables, 8 new options
| New WordPress options |
|---|
| widget_theysaidso_widget |
| theysaidso_admin_options |
| widget_recent-comments |
| can_compress_scripts |
| twiget_options |
| db_upgraded |
| widget_twiget-widget |
| widget_recent-posts |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Twiget Twitter Widget
Normal browser usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,813 ▲67 | 13.30 ▼1.49 | 1.80 ▼0.06 | 42.27 ▼3.92 |
| Dashboard /wp-admin | 2,219 ▲28 | 5.82 ▼0.04 | 105.90 ▼8.62 | 39.27 ▼2.74 |
| Posts /wp-admin/edit.php | 2,105 ▲16 | 1.99 ▼0.06 | 39.56 ▼3.06 | 35.10 ▼1.41 |
| Add New Post /wp-admin/post-new.php | 1,558 ▲39 | 18.15 ▼4.99 | 597.70 ▼22.84 | 77.77 ▲14.53 |
| Media Library /wp-admin/upload.php | 1,401 ▲16 | 4.22 ▲0.02 | 105.30 ▲4.20 | 43.72 ▲0.02 |
| Twiget Settings /wp-admin/options-general.php?page=twiget/options.php | 995 | 2.07 | 23.97 | 32.88 |
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
You still need to fix the following
- Uninstall procedure had uncaught errors
- > User deprecated in wp-includes/functions.php+5546
The called constructor method for WP_Widget class in Twiget_Twitter_Widget is deprecated since version 4.3.0! Use __construct() instead.
- This plugin does not fully uninstall, leaving 7 options in the database
- widget_recent-posts
- widget_theysaidso_widget
- db_upgraded
- theysaidso_admin_options
- widget_recent-comments
- widget_twiget-widget
- can_compress_scripts
Smoke tests 50% from 4 tests
Server-side errors 0% from 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the server (in the Apache logs)
These server-side errors were triggered
- > GET request to /wp-admin/options-general.php?page=twiget/options.php
- > User deprecated in wp-includes/functions.php+5546
The called constructor method for WP_Widget class in Twiget_Twitter_Widget is deprecated since version 4.3.0! Use __construct() instead.
SRP 50% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle applies for WordPress plugins as well - please make sure your PHP files perform no actions when accessed directly
Please take a closer look at the following
- 3× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Fatal error
Uncaught Error: Class 'WP_Widget' not found in wp-content/plugins/twiget/widgets.php:8
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/twiget/options.php:8
- > PHP Fatal error
Uncaught Error: Call to undefined function untrailingslashit() in wp-content/plugins/twiget/twiget.php:27
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
Everything seems fine on the user side
Optimizations
Plugin configuration Passed 29 tests
readme.txt Passed 16 tests
The readme.txt file is undoubtedly the most important file in your plugin, preparing it for public listing on WordPress.org
5 plugin tags: twitter widget, widget, tweets, sidebar, twitter
twiget/twiget.php Passed 13 tests
The main file in "Twiget Twitter Widget" v. 1.1.3 serves as a complement to information provided in readme.txt and as the entry point to the plugin
54 characters long description:
A widget to display the latest Twitter status updates.
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short check of programming languages and file extensions; no executable files are allowed
No dangerous file extensions were detected1,320 lines of code in 9 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 6 | 225 | 396 | 1,022 |
| PO File | 1 | 63 | 63 | 190 |
| JavaScript | 1 | 13 | 7 | 68 |
| CSS | 1 | 0 | 0 | 40 |
PHP code Passed 2 tests
Cyclomatic complexity and code structure are the fingerprint of this plugin
No cyclomatic complexity issues were detected for this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.25 |
| Average class complexity | 8.85 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 29.00 |
| Average method complexity | 2.34 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 12.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 | 14 | |
| ▷ Named functions | 14 | 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
All PNG images should be compressed to minimize bandwidth usage for end users
4 PNG files occupy 0.06MB with 0.01MB in potential savings
Potential savings
| Compression of 4 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| screenshot-2.png | 32.59KB | 11.83KB | ▼ 63.71% |
| screenshot-3.png | 14.58KB | 14.06KB | ▼ 3.55% |
| screenshot-4.png | 8.59KB | 8.53KB | ▼ 0.78% |
| screenshot-1.png | 10.78KB | 10.67KB | ▼ 1.08% |