Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.01MB] [CPU: ▼4.17ms] Passed 4 tests
Server-side resources used by Ungapped Widgets
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.47 ▲0.01 | 41.26 ▼1.92 |
| Dashboard /wp-admin | 3.31 ▲0.01 | 45.81 ▼3.34 |
| Posts /wp-admin/edit.php | 3.36 ▲0.01 | 47.01 ▲2.58 |
| Add New Post /wp-admin/post-new.php | 5.89 ▲0.01 | 80.24 ▼9.42 |
| Media Library /wp-admin/upload.php | 3.23 ▲0.01 | 32.13 ▼2.00 |
Server storage [IO: ▲0.00MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
The plugin installed successfully
Filesystem: 2 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| db_upgraded |
| can_compress_scripts |
| widget_recent-comments |
| theysaidso_admin_options |
| widget_theysaidso_widget |
| widget_recent-posts |
Browser metrics Passed 4 tests
An overview of browser requirements for Ungapped Widgets
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,800 ▲54 | 14.44 ▲0.08 | 1.90 ▲0.10 | 44.20 ▲0.31 |
| Dashboard /wp-admin | 2,206 ▲15 | 5.96 ▲0.06 | 107.03 ▲3.26 | 36.63 ▼4.21 |
| Posts /wp-admin/edit.php | 2,089 ▼0 | 2.01 ▲0.02 | 38.97 ▲4.37 | 35.23 ▼1.04 |
| Add New Post /wp-admin/post-new.php | 1,533 ▼0 | 23.29 ▲0.31 | 670.59 ▼21.79 | 55.50 ▼1.02 |
| Media Library /wp-admin/upload.php | 1,388 ▲3 | 4.26 ▲0.06 | 95.02 ▼5.12 | 38.97 ▼12.46 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
It is recommended to fix the following
- The uninstall procedure has failed, leaving 6 options in the database
- can_compress_scripts
- widget_recent-posts
- widget_recent-comments
- widget_theysaidso_widget
- db_upgraded
- theysaidso_admin_options
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a short smoke test looking for server-side errors
Everything seems fine, however this is by no means an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle: PHP files have to remain inert when accessed directly, throwing no errors and performing no actions
Please take a closer look at the following
- 1× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_shortcode() in wp-content/plugins/ungapped-widgets/ungapped-widgets-plugin.php:40
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
There were no browser issues found
Optimizations
Plugin configuration 83% from 29 tests
readme.txt Passed 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
5 plugin tags: marketing automation, sms marketing, e-mail marketing, forms, surveys
ungapped-widgets/ungapped-widgets-plugin.php 62% from 13 tests
The main file in "Ungapped Widgets" v. 1... serves as a complement to information provided in readme.txt and as the entry point to the plugin
Please take the time to fix the following:
- Domain Path: Note that the domain path follows the same naming rules as the domain name, using only dashes and lowercase characters ("")
- Domain Path: Prefix the domain path with a forward slash character ("/")
- Version: Use only periods and digits for the version number (ex. "1.0.3" instead of "1...")
- Text Domain: The text domain should only use lowercase characters and dashes
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("ungapped-widgets.php" instead of "ungapped-widgets-plugin.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
Good job! No executable or dangerous file extensions detected26 lines of code in 1 file:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 1 | 10 | 15 | 26 |
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.17 |
| Average class complexity | 0.00 |
| ▷ Minimum class complexity | 0.00 |
| ▷ Maximum class complexity | 0.00 |
| Average method complexity | 0.00 |
| ▷ Minimum method complexity | 0.00 |
| ▷ Maximum method complexity | 0.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 0 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 0 | 0.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 0 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 0 | 0.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 2 | |
| ▷ Named functions | 2 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 0 | |
| ▷ Global constants | 0 | 0.00% |
| ▷ Class constants | 0 | 0.00% |
| ▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
Often times overlooked, PNG files can occupy unnecessary space in your plugin
PNG images were not found in this plugin