Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
Install script ran successfully
Server metrics [RAM: ▲0.05MB] [CPU: ▼145.69ms] Passed 4 tests
A check of server-side resources used by Wadvisor plugin
No issues were detected with server-side resource usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 2.88 ▲0.05 | 42.65 ▲7.76 |
| Dashboard /wp-admin | 3.11 ▲0.05 | 48.89 ▼1.36 |
| Posts /wp-admin/edit.php | 3.16 ▲0.05 | 46.40 ▲0.26 |
| Add New Post /wp-admin/post-new.php | 5.47 ▲0.04 | 94.81 ▼573.95 |
| Media Library /wp-admin/upload.php | 3.05 ▲0.04 | 31.06 ▼7.69 |
Server storage [IO: ▲3.63MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
There were no storage issued detected upon installing this plugin
Filesystem: 14 new files
Database: no new tables, 1 new option
| New WordPress options |
|---|
| widget_wadvisor_page_widget |
Browser metrics Passed 4 tests
An overview of browser requirements for Wadvisor plugin
This plugin has a minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 522 ▼3,074 | 5.22 ▼10.32 | 8.85 ▼1.68 | 48.73 ▼1.97 |
| Dashboard /wp-admin | 2,967 ▲36 | 5.91 ▼0.03 | 140.23 ▼13.57 | 111.46 ▼8.59 |
| Posts /wp-admin/edit.php | 2,739 ▼0 | 2.70 ▼0.03 | 77.53 ▲10.88 | 88.52 ▼1.38 |
| Add New Post /wp-admin/post-new.php | 1,683 ▼0 | 18.73 ▼0.19 | 373.95 ▼14.43 | 104.17 ▼4.18 |
| Media Library /wp-admin/upload.php | 1,810 ▲3 | 5.02 ▼0.02 | 157.75 ▲5.62 | 114.60 ▼6.15 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
These items require your attention
- This plugin does not fully uninstall, leaving 1 option in the database
- widget_wadvisor_page_widget
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 no errors were found, this is by no means an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | SRP (Single-Responsibility Principle) - PHP files must act as libraries and never output text or perform any action when accessed directly in a browser
Please take a closer look at the following
- 1× PHP files perform the action of outputting non-empty strings when accessed directly:
- > /wp-content/plugins/wp-wadvisor/widget-wadvisor.php
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 94% 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
These attributes need your attention:
- Screenshots: These screenshots do not have images: #1 (Page Widget - Configuration example), #2 (Page Widget - Display example), #3 (Question Widget - Display example)
wp-wadvisor/widget-wadvisor.php 92% from 13 tests
"Wadvisor plugin" version 1.0.1.2's primary PHP file adds more information about the plugin and serves as the entry point for WordPress
It is important to fix the following:
- Main file name: It is recommended to name the main PHP file as the plugin slug ("wp-wadvisor.php" instead of "widget-wadvisor.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is an overview of file extensions present in this plugin and a short test that no dangerous files are bundled with this plugin
No dangerous file extensions were detected249 lines of code in 4 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 2 | 23 | 50 | 188 |
| PO File | 1 | 15 | 17 | 50 |
| XML | 1 | 0 | 0 | 11 |
PHP code Passed 2 tests
An overview of cyclomatic complexity and code structure
There are no cyclomatic complexity problems detected for this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.49 |
| Average class complexity | 54.00 |
| ▷ Minimum class complexity | 54.00 |
| ▷ Maximum class complexity | 54.00 |
| Average method complexity | 14.25 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 32.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 | 5 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 5 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 2 | |
| ▷ Named functions | 0 | 0.00% |
| ▷ Anonymous functions | 2 | 100.00% |
| Constants | 1 | |
| ▷ Global constants | 0 | 0.00% |
| ▷ Class constants | 1 | 100.00% |
| ▷ Public constants | 1 | 100.00% |
Plugin size 50% from 2 tests
Image compression 50% from 2 tests
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
3 PNG files occupy 0.66MB with 0.43MB in potential savings
Potential savings
| Compression of 3 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| screenshot-3.png | 251.20KB | 78.29KB | ▼ 68.83% |
| screenshot-1.png | 16.43KB | 7.35KB | ▼ 55.26% |
| screenshot-2.png | 409.92KB | 125.11KB | ▼ 69.48% |