Benchmarks
Plugin footprint 58% from 16 tests
Installer 0% from 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
It is recommended to fix the following installer errors
- This plugin did not install gracefully
- > Warning in wp-includes/functions.php+6461
fopen(wp-content/plugins/patro/lib/../patro.php): failed to open stream: No such file or directory
Server metrics [RAM: ▲0.02MB] [CPU: ▼140.57ms] Passed 4 tests
Server-side resources used by Patro
This plugin does not affect your website's performance
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 2.87 ▲0.15 | 41.23 ▲14.82 |
| Dashboard /wp-admin | 3.08 ▲0.03 | 53.97 ▲3.74 |
| Posts /wp-admin/edit.php | 3.13 ▲0.03 | 53.77 ▲0.43 |
| Add New Post /wp-admin/post-new.php | 5.44 ▲0.01 | 103.16 ▼562.77 |
| Media Library /wp-admin/upload.php | 3.03 ▲0.02 | 38.63 ▼3.67 |
Server storage [IO: ▲0.05MB] [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: 17 new files
Database: no new tables, 1 new option
| New WordPress options |
|---|
| widget_patro_widget_id |
Browser metrics Passed 4 tests
Checking browser requirements for Patro
This plugin renders optimally with no browser resource issues detected
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 3,807 ▲211 | 16.42 ▲0.79 | 15.98 ▲5.67 | 49.85 ▼1.82 |
| Dashboard /wp-admin | 2,967 ▲36 | 5.99 ▲0.05 | 178.60 ▲0.02 | 122.11 ▼3.17 |
| Posts /wp-admin/edit.php | 2,739 ▼0 | 2.72 ▲0.00 | 77.90 ▼0.48 | 90.06 ▼13.83 |
| Add New Post /wp-admin/post-new.php | 1,683 ▲68 | 18.69 ▼2.80 | 452.39 ▲112.64 | 109.67 ▼3.37 |
| Media Library /wp-admin/upload.php | 1,807 ▼0 | 5.04 ▼0.01 | 170.09 ▼13.87 | 123.30 ▼10.26 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
These items require your attention
- Zombie WordPress options were found after uninstall: 1 option
- widget_patro_widget_id
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
Good news, no errors were detected
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
- 2× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Uncaught Error: Class 'WP_Widget' not found in wp-content/plugins/patro/PatroWidget.php:3
- > PHP Fatal error
Uncaught Error: Call to undefined function plugins_url() in wp-content/plugins/patro/lib/patroooo_lib.php:12
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 88% 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 to be fixed:
- Plugin Name: Please replace "Plugin Name" with the name of your plugin on the first line (
=== patro ===) - Tags: Please delete some tags, you are using 17 tag instead of maximum 10
patro/Patro.php 92% from 13 tests
The main PHP file in "Patro" ver. 1.4 adds more information about the plugin and also serves as the entry point for this plugin
The following require your attention:
- Main file name: The principal plugin file should be the same as the plugin slug ("patro.php" instead of "Patro.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
Success! There were no dangerous files found in this plugin937 lines of code in 9 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| JavaScript | 2 | 415 | 13 | 537 |
| PHP | 5 | 190 | 37 | 299 |
| CSS | 2 | 44 | 1 | 101 |
PHP code Passed 2 tests
Analyzing logical lines of code, cyclomatic complexity, and other code metrics
There were no cyclomatic complexity issued detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.16 |
| Average class complexity | 4.00 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 9.00 |
| Average method complexity | 1.71 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 8.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 5 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 5 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 21 | |
| ▷ Static methods | 10 | 47.62% |
| ▷ Public methods | 21 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 0 | |
| ▷ Named functions | 0 | 0.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
4 PNG files occupy 0.01MB with 0.01MB in potential savings
Potential savings
| Compression of 4 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| images/prev.png | 1.96KB | 0.68KB | ▼ 65.61% |
| images/next.png | 1.94KB | 0.63KB | ▼ 67.24% |
| images/next_hover.png | 1.86KB | 0.62KB | ▼ 66.79% |
| images/prev_hover.png | 1.95KB | 0.63KB | ▼ 67.90% |