Benchmarks
Plugin footprint Passed 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | All plugins must install correctly, without throwing any errors, warnings, or notices
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.04MB] [CPU: ▼328.24ms] 75% from 4 tests
This is a short check of server-side resources used by Worthless Plugin
The following require your attention
- CPU: The total CPU usage must kept under 500.00ms (currently 1,728.81ms on /wp-admin/options-general.php?page=worthless-plugin)
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.58 ▲0.07 | 88.13 ▲36.55 |
Dashboard /wp-admin | 3.47 ▲0.06 | 32.96 ▼84.56 |
Posts /wp-admin/edit.php | 3.70 ▲0.06 | 37.24 ▼2.55 |
Add New Post /wp-admin/post-new.php | 6.94 ▼0.03 | 91.44 ▼1,219.80 |
Media Library /wp-admin/upload.php | 3.35 ▲0.06 | 24.41 ▼6.05 |
Worthless Plugin /wp-admin/options-general.php?page=worthless-plugin | 4.46 | 1,728.81 |
Server storage [IO: ▲0.08MB] [DB: ▲0.05MB] Passed 3 tests
Filesystem and database footprint
No storage issues were detected
Filesystem: 10 new files
Database: no new tables, no new options
Browser metrics Passed 4 tests
Checking browser requirements for Worthless Plugin
This plugin has a minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 3,794 ▲40 | 15.69 ▼0.08 | 8.66 ▲2.97 | 2.79 ▼0.08 |
Dashboard /wp-admin | 2,920 ▲59 | 5.99 ▼0.10 | 128.54 ▼7.83 | 179.78 ▲14.28 |
Posts /wp-admin/edit.php | 2,698 ▲14 | 3.25 ▲0.00 | 64.37 ▼44.92 | 144.57 ▼22.67 |
Add New Post /wp-admin/post-new.php | 1,678 ▲12 | 15.61 ▼5.44 | 425.14 ▼62.41 | 158.60 ▼5.68 |
Media Library /wp-admin/upload.php | 1,731 ▲33 | 5.49 ▼0.01 | 137.90 ▼27.30 | 227.08 ▲34.21 |
Worthless Plugin /wp-admin/options-general.php?page=worthless-plugin | 1,299 | 2.53 | 82.30 | 164.63 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.05MB] Passed 4 tests
🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
Uninstaller ran successfully
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the server (in the Apache logs)
The smoke test was a success, however most plugin functionality was not tested
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
- 1× PHP files perform the task of outputting text when accessed with GET requests:
- > /wp-content/plugins/worthless-plugin/worthless-plugin.php
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)
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 96% from 29 tests
readme.txt Passed 16 tests
Perhaps the most important file in your plugin readme.txt gets parsed in order to generate the public listing of your plugin
10 plugin tags: useful, email, fun, plugin, stats...
worthless-plugin/worthless-plugin.php 92% from 13 tests
"Worthless Plugin" version 3.3.2's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
It is important to fix the following:
- Text Domain: The text domain is optional since WordPress version 4.6; if you do specify it, it must be the same as the plugin slug
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short review of files and their extensions; it is not recommended to include executable files
Everything looks great! No dangerous files found in this plugin199 lines of code in 2 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 1 | 20 | 37 | 164 |
CSS | 1 | 7 | 3 | 35 |
PHP code Passed 2 tests
This is a short overview of cyclomatic complexity and code structure for this plugin
Although this was not an exhaustive test, there were no cyclomatic complexity issues detected
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.09 |
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 | 6 | |
▷ Named functions | 6 | 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
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 |
images/buttons/2.png | 7.27KB | 3.36KB | ▼ 53.83% |
images/buttons/1.png | 8.33KB | 3.44KB | ▼ 58.73% |
images/buttons/3.png | 4.08KB | 2.03KB | ▼ 50.28% |