Benchmarks
Plugin footprint 40% from 16 tests
Installer 0% from 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
Please fix the following installer errors
- Install procedure had errors
- > Notice in wp-content/plugins/banman/banman.php+20
Undefined index: bman_click_id
Server metrics [RAM: ▼1.81MB] [CPU: ▼56.89ms] Passed 4 tests
Analyzing server-side resources used by BanMan
No issues were detected with server-side resource usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 2.18 ▼1.28 | 5.23 ▼40.63 |
Dashboard /wp-admin | 2.20 ▼1.14 | 6.60 ▼57.31 |
Posts /wp-admin/edit.php | 2.21 ▼1.15 | 8.12 ▼42.26 |
Add New Post /wp-admin/post-new.php | 2.20 ▼3.68 | 6.71 ▼87.35 |
Media Library /wp-admin/upload.php | 2.21 ▼1.02 | 6.26 ▼30.14 |
Server storage [IO: ▲0.11MB] [DB: ▲0.00MB] 67% from 3 tests
Input-output and database impact of this plugin
Please fix the following
- There were 1 file (4.00KB) illegally modified outside of "wp-content/plugins/banman/" and "wp-content/uploads/"
- (new file) wp-content/mgd_mirror/mgd_maximinodotpy-gitdown-test-repository
Filesystem: 16 new files
Database: 1 new table, 7 new options
New tables |
---|
wp_banman |
New WordPress options |
---|
can_compress_scripts |
db_upgraded |
theysaidso_admin_options |
widget_banman |
widget_recent-posts |
widget_theysaidso_widget |
widget_recent-comments |
Browser metrics Passed 4 tests
This is an overview of browser requirements for BanMan
Minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 3,083 ▲297 | 15.58 ▲1.20 | 5.55 ▲3.78 | 37.52 ▼2.69 |
Dashboard /wp-admin | 2,385 ▲179 | 6.51 ▲0.60 | 132.90 ▲26.88 | 44.54 ▲0.80 |
Posts /wp-admin/edit.php | 2,287 ▲187 | 3.44 ▲1.40 | 55.05 ▲14.26 | 34.10 ▼6.18 |
Add New Post /wp-admin/post-new.php | 1,567 ▲34 | 23.26 ▲0.17 | 597.25 ▼17.17 | 34.67 ▼17.38 |
Media Library /wp-admin/upload.php | 1,421 ▲21 | 4.03 ▼0.23 | 87.94 ▼22.55 | 42.96 ▲0.11 |
Add new /wp-admin/banman.php?page=edit | 26 | 0.44 | 0.10 | 16.34 |
List of banners /wp-admin/banman.php | 26 | 0.44 | 0.14 | 8.07 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 50% from 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
Please fix the following items
- This plugin cannot be uninstalled
- > Notice in wp-content/plugins/banman/banman.php+20
Undefined index: bman_click_id
- Zombie WordPress options were found after uninstall: 7 options
- widget_theysaidso_widget
- can_compress_scripts
- widget_banman
- widget_recent-comments
- db_upgraded
- theysaidso_admin_options
- widget_recent-posts
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
Even though no errors were found, this is by no means an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | It is important to ensure that your PHP files perform no action when accessed directly, respecting the single-responsibility principle
Please fix the following items
- 8× 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/banman/includes/banman.widget.php:3
- > PHP Notice
Undefined variable: isNew in wp-content/plugins/banman/tmpl/edit.php on line 9
- > PHP Fatal error
Uncaught Error: Call to undefined function plugin_dir_path() in wp-content/plugins/banman/banman.php:15
- > PHP Fatal error
Uncaught Error: Class 'WP_List_Table' not found in wp-content/plugins/banman/includes/admin.list_table.php:3
- > PHP Warning
Use of undefined constant ABSPATH - assumed 'ABSPATH' (this will throw an Error in a future version of PHP) in wp-content/plugins/banman/tmpl/admin.php on line 1
- > PHP Warning
require_once(ABSPATHwp-admin/includes/class-wp-list-table.php): failed to open stream: No such file or directory in wp-content/plugins/banman/tmpl/admin.php on line 1
- > PHP Fatal error
Uncaught Error: Call to undefined function __() in wp-content/plugins/banman/tmpl/edit.php:9
- > PHP Fatal error
require_once(): Failed opening required 'ABSPATHwp-admin/includes/class-wp-list-table.php' (include_path='.:/usr/share/php') in wp-content/plugins/banman/tmpl/admin.php on line 1
- > PHP Fatal error
User-side errors 0% from 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
Please take a look at the following user-side issues
- > GET request to /wp-admin/banman.php?page=edit
- > Network (severe)
wp-admin/banman.php?page=edit - Failed to load resource: the server responded with a status of 404 (Not Found)
- > GET request to /wp-admin/banman.php
- > Network (severe)
wp-admin/banman.php - Failed to load resource: the server responded with a status of 404 (Not Found)
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 81% from 16 tests
The readme.txt file is important because it is parsed by WordPress.org for the public listing of your plugin
These attributes need to be fixed:
- Donate link: Please fix this invalid url: ""
- Screenshots: These screenshots require images: #1 (Страница создания нового баннера), #2 (Page to create a new banner), #3 (Страница управления баннерами (Список баннеров)), #4 (List of banners), #5 (Виджет для создании новой позиции вывода баннера), #6 (Widget for creating a new position of the output banner), #7 (Пример Pop-up баннера), #8 (Example Pop-up banner)
- Tags: You are using too many tags: 21 tag instead of maximum 10
banman/banman.php Passed 13 tests
The primary PHP file in "BanMan" version 1.0.1.0 is used by WordPress to initiate all plugin functionality
139 characters long description:
Простой и удобный плагин для управления баннерами на сайте. Managing banners on your site
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is a short overview of programming languages used in this plugin, detecting executable files
No dangerous file extensions were detected1,411 lines of code in 13 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 8 | 95 | 16 | 819 |
CSS | 1 | 39 | 65 | 385 |
PO File | 1 | 74 | 76 | 164 |
JavaScript | 3 | 0 | 7 | 43 |
PHP code Passed 2 tests
A short review of cyclomatic complexity and code structure
Everything seems fine, there were no complexity issues found
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.39 |
Average class complexity | 26.00 |
▷ Minimum class complexity | 9.00 |
▷ Maximum class complexity | 49.00 |
Average method complexity | 3.21 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 14.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 | 34 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 34 | 100.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 4 | |
▷ Named functions | 3 | 75.00% |
▷ Anonymous functions | 1 | 25.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
Using a strong compression for your PNG files is a great way to speed-up your plugin
1 compressed PNG file occupies 0.00MB
Potential savings
Compression of 1 random PNG file using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
images/close.png | 0.66KB | 0.60KB | ▼ 8.04% |