Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
Install script ran successfully
Server metrics [RAM: ▼0.13MB] [CPU: ▼12.96ms] Passed 4 tests
A check of server-side resources used by Blocking for Yandex.Advisor
This plugin does not affect your website's performance
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.50 ▲0.03 | 37.72 ▼3.06 |
Dashboard /wp-admin | 3.23 ▼0.07 | 36.16 ▼16.36 |
Posts /wp-admin/edit.php | 3.30 ▼0.06 | 38.80 ▼9.34 |
Add New Post /wp-admin/post-new.php | 5.47 ▼0.41 | 74.47 ▼23.08 |
Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 32.15 ▼2.19 |
Server storage [IO: ▲0.03MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
No storage issues were detected
Filesystem: 11 new files
Database: no new tables, 7 new options
New WordPress options |
---|
widget_theysaidso_widget |
antisovet_domain |
can_compress_scripts |
theysaidso_admin_options |
widget_recent-posts |
widget_recent-comments |
db_upgraded |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Blocking for Yandex.Advisor
Normal browser usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,861 ▲115 | 13.74 ▼0.64 | 5.71 ▲3.93 | 41.96 ▼2.45 |
Dashboard /wp-admin | 2,226 ▲35 | 5.87 ▲0.96 | 139.92 ▲25.85 | 84.47 ▲37.84 |
Posts /wp-admin/edit.php | 2,123 ▲34 | 2.03 ▲0.03 | 37.59 ▼1.63 | 32.79 ▼1.50 |
Add New Post /wp-admin/post-new.php | 1,542 ▲23 | 23.08 ▼0.19 | 723.85 ▲50.90 | 55.44 ▼5.24 |
Media Library /wp-admin/upload.php | 1,417 ▲26 | 4.22 ▲0.05 | 105.53 ▼2.09 | 82.84 ▲31.54 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
These items require your attention
- Zombie WordPress options were found after uninstall: 7 options
- widget_recent-comments
- antisovet_domain
- theysaidso_admin_options
- can_compress_scripts
- widget_theysaidso_widget
- widget_recent-posts
- db_upgraded
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
Even though everything seems fine, this is not an exhaustive test
SRP 0% 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 fix the following
- 1× PHP files output non-empty strings when accessed directly via GET requests:
- > /wp-content/plugins/block-for-yandex-sovetnik/antisovet.php
- 4× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Fatal error
Uncaught Error: Call to undefined function _e() in wp-content/plugins/block-for-yandex-sovetnik/templates/info.php:2
- > PHP Fatal error
Uncaught Error: Call to undefined function _e() in wp-content/plugins/block-for-yandex-sovetnik/templates/error.php:2
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_url() in wp-content/plugins/block-for-yandex-sovetnik/templates/register.php:3
- > PHP Fatal error
Uncaught Error: Call to undefined function _e() in wp-content/plugins/block-for-yandex-sovetnik/templates/support.php:2
- > PHP Fatal error
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 on the user side
Optimizations
Plugin configuration 93% 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
8 plugin tags: yandex, blocking, yandex sovetnik, advisor, hide...
block-for-yandex-sovetnik/antisovet.php 85% from 13 tests
The main PHP file in "Blocking for Yandex.Advisor" ver. 1.2 adds more information about the plugin and also serves as the entry point for this plugin
The following require your attention:
- Main file name: Name the main plugin file the same as the plugin slug ("block-for-yandex-sovetnik.php" instead of "antisovet.php")
- 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 | 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 detected284 lines of code in 8 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 5 | 33 | 12 | 201 |
PO File | 1 | 19 | 5 | 52 |
CSS | 1 | 0 | 0 | 18 |
SVG | 1 | 0 | 0 | 13 |
PHP code Passed 2 tests
An overview of cyclomatic complexity and code structure
There were no cyclomatic complexity issued detected
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.28 |
Average class complexity | 20.00 |
▷ Minimum class complexity | 20.00 |
▷ Maximum class complexity | 20.00 |
Average method complexity | 4.17 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 14.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 | 6 | |
▷ Static methods | 1 | 16.67% |
▷ Public methods | 2 | 33.33% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 4 | 66.67% |
Functions | 8 | |
▷ Named functions | 8 | 100.00% |
▷ Anonymous functions | 0 | 0.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
All PNG images should be compressed to minimize bandwidth usage for end users
1 compressed PNG file occupies 0.00MB
Potential savings
Compression of 1 random PNG file using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
assets/icon.png | 0.72KB | 0.83KB | 0.00% |