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.01MB] [CPU: ▼5.60ms] Passed 4 tests
Analyzing server-side resources used by Widget Instance
No issues were detected with server-side resource usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.48 ▲0.02 | 42.37 ▲1.32 |
Dashboard /wp-admin | 3.32 ▼0.02 | 50.43 ▼12.74 |
Posts /wp-admin/edit.php | 3.37 ▲0.02 | 49.45 ▼1.14 |
Add New Post /wp-admin/post-new.php | 5.90 ▲0.02 | 89.11 ▼9.36 |
Media Library /wp-admin/upload.php | 3.24 ▲0.02 | 37.66 ▲0.86 |
Server storage [IO: ▲0.04MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
This plugin was installed successfully
Filesystem: 13 new files
Database: no new tables, 6 new options
New WordPress options |
---|
db_upgraded |
can_compress_scripts |
widget_theysaidso_widget |
theysaidso_admin_options |
widget_recent-posts |
widget_recent-comments |
Browser metrics Passed 4 tests
An overview of browser requirements for Widget Instance
This plugin renders optimally with no browser resource issues detected
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,814 ▲68 | 14.40 ▲0.03 | 2.00 ▲0.18 | 44.63 ▲4.21 |
Dashboard /wp-admin | 2,198 ▲24 | 5.65 ▲0.09 | 96.27 ▲9.55 | 41.71 ▲1.41 |
Posts /wp-admin/edit.php | 2,103 ▼0 | 2.00 ▼0.05 | 34.47 ▼23.32 | 34.28 ▼9.41 |
Add New Post /wp-admin/post-new.php | 1,531 ▼14 | 23.02 ▼0.21 | 614.16 ▼0.84 | 57.74 ▲8.30 |
Media Library /wp-admin/upload.php | 1,403 ▼0 | 4.21 ▲0.13 | 99.69 ▼2.10 | 47.23 ▲1.82 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
These items require your attention
- The uninstall procedure has failed, leaving 6 options in the database
- widget_recent-comments
- can_compress_scripts
- db_upgraded
- widget_theysaidso_widget
- theysaidso_admin_options
- widget_recent-posts
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
Even though everything seems fine, this is not an exhaustive test
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 fix the following items
- 1× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Fatal error
Uncaught Error: Call to undefined function plugin_dir_path() in wp-content/plugins/widget-instance/index.php:21
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the browser (console and network errors and warnings)
There were no browser issues found
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 88% from 16 tests
The readme.txt file is an important file in your plugin as it is parsed by WordPress.org to prepare the public listing of your plugin
Attributes that require attention:
- Plugin Name: "Plugin Name" should be replaced with the name of your plugin on the first line (
=== widget-instance ===
) - Screenshots: Add images for these screenshots: #1 (The Widget Instance editor button), #2 (The editor dialog for inserting a specific widget instance)
widget-instance/index.php 92% from 13 tests
The entry point to "Widget Instance" version 0.9.4 is a PHP file that has certain tags in its header comment area
The following require your attention:
- Main file name: The principal plugin file should be the same as the plugin slug ("widget-instance.php" instead of "index.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | There should be no dangerous file extensions present in any WordPress plugin
Good job! No executable or dangerous file extensions detected395 lines of code in 9 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 4 | 33 | 40 | 149 |
CSS | 1 | 4 | 0 | 114 |
JavaScript | 3 | 5 | 6 | 79 |
HTML | 1 | 0 | 0 | 53 |
PHP code Passed 2 tests
Analyzing cyclomatic complexity and code structure
Everything seems fine, there were no complexity issues found
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.30 |
Average class complexity | 6.00 |
▷ Minimum class complexity | 3.00 |
▷ Maximum class complexity | 11.00 |
Average method complexity | 2.25 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 11.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 | 0 | 0.00% |
▷ Public methods | 12 | 100.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 2 | |
▷ Named functions | 2 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 3 | |
▷ Global constants | 3 | 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
3 PNG files occupy 0.02MB with 0.01MB in potential savings
Potential savings
Compression of 3 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
screenshot-1.png | 3.03KB | 1.88KB | ▼ 37.97% |
tinymce.png | 0.74KB | 0.71KB | ▼ 4.07% |
screenshot-2.png | 17.88KB | 7.18KB | ▼ 59.85% |