Benchmarks
Plugin footprint 65% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | All plugins must install correctly, without throwing any errors, warnings, or notices
This plugin's installer ran successfully
Server metrics [RAM: ▼0.79MB] [CPU: ▼32.62ms] Passed 4 tests
A check of server-side resources used by Spider Blocker
This plugin does not affect your website's performance
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.60 ▲0.14 | 37.50 ▼6.97 |
| Dashboard /wp-admin | 3.16 ▼0.15 | 23.95 ▼30.45 |
| Posts /wp-admin/edit.php | 3.16 ▼0.20 | 31.04 ▼13.78 |
| Add New Post /wp-admin/post-new.php | 3.16 ▼2.73 | 26.70 ▼70.52 |
| Media Library /wp-admin/upload.php | 3.16 ▼0.07 | 23.22 ▼15.72 |
| SpiderBlocker /wp-admin/tools.php?page=ni_spider_block | 3.16 | 22.97 |
Server storage [IO: ▲0.03MB] [DB: ▲0.01MB] 67% from 3 tests
Analyzing filesystem and database footprints of this plugin
These are issues you should consider
- The plugin illegally modified 1 file (2.84KB) outside of "wp-content/plugins/spiderblocker/" and "wp-content/uploads/"
- (modified) .htaccess
Filesystem: 4 new files
Database: no new tables, 7 new options
| New WordPress options |
|---|
| can_compress_scripts |
| widget_recent-comments |
| widget_theysaidso_widget |
| theysaidso_admin_options |
| db_upgraded |
| Niteoweb.SpiderBlocker.Bots |
| widget_recent-posts |
Browser metrics Passed 4 tests
Spider Blocker: an overview of browser usage
This plugin renders optimally with no browser resource issues detected
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,804 ▲69 | 13.25 ▼1.15 | 1.58 ▼0.56 | 40.35 ▼6.32 |
| Dashboard /wp-admin | 2,210 ▲22 | 5.79 ▼0.10 | 101.53 ▲0.22 | 38.14 ▼3.64 |
| Posts /wp-admin/edit.php | 2,093 ▲4 | 1.99 ▲0.00 | 50.91 ▲8.19 | 45.15 ▲7.79 |
| Add New Post /wp-admin/post-new.php | 1,550 ▲31 | 18.25 ▼4.97 | 616.77 ▼28.46 | 66.02 ▲14.92 |
| Media Library /wp-admin/upload.php | 1,386 ▼2 | 4.24 ▲0.10 | 98.59 ▼9.61 | 42.69 ▼10.43 |
| SpiderBlocker /wp-admin/tools.php?page=ni_spider_block | 2,397 | 3.73 | 85.48 | 31.91 |
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
You still need to fix the following
- This plugin cannot be uninstalled
- > Notice in wp-content/plugins/spiderblocker/index.php+940
Undefined index: SERVER_SOFTWARE
- This plugin does not fully uninstall, leaving 6 options in the database
- widget_theysaidso_widget
- widget_recent-comments
- can_compress_scripts
- db_upgraded
- widget_recent-posts
- theysaidso_admin_options
Smoke tests 75% from 4 tests
Server-side errors 0% from 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
Smoke test failed, please fix the following
- 2 occurences, only the last one shown
- > GET request to /wp-admin/tools.php?page=ni_spider_block
- > POST request to /wp-admin/admin-ajax.php
- > Notice in wp-content/plugins/spiderblocker/index.php+940
Undefined index: SERVER_SOFTWARE
SRP Passed 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
The SRP test was a success
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
Everything seems fine on the user side
Optimizations
Plugin configuration 86% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file is an important file in your plugin as it is parsed by WordPress.org to prepare the public listing of your plugin
Please fix the following attributes:
- Plugin Name: Please replace "Plugin Name" with the name of your plugin on the first line (
=== spiderblocker ===)
spiderblocker/index.php 77% from 13 tests
This is the main PHP file of "Spider Blocker" version 1.3.5, providing information about the plugin in the header fields and serving as the principal entry point to the plugin's functions
It is important to fix the following:
- Domain Path: You should use only dashes and lowercase characters for the domain path ("i18n")
- Main file name: The principal plugin file should be the same as the plugin slug ("spiderblocker.php" instead of "index.php")
- Domain Path: The domain path should be prefixed with a forward slash character ("/i18n")
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
Good job! No executable or dangerous file extensions detected809 lines of code in 2 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 2 | 120 | 222 | 809 |
PHP code Passed 2 tests
Analyzing cyclomatic complexity and code structure
Great job! No cyclomatic complexity issues were detected in this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.24 |
| Average class complexity | 35.00 |
| ▷ Minimum class complexity | 35.00 |
| ▷ Maximum class complexity | 35.00 |
| Average method complexity | 1.92 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 5.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 1 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 1 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 1 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 37 | |
| ▷ Static methods | 1 | 2.70% |
| ▷ Public methods | 32 | 86.49% |
| ▷ Protected methods | 3 | 8.11% |
| ▷ Private methods | 2 | 5.41% |
| Functions | 0 | |
| ▷ Named functions | 0 | 0.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 8 | |
| ▷ Global constants | 0 | 0.00% |
| ▷ Class constants | 8 | 100.00% |
| ▷ Public constants | 8 | 100.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
There were not PNG files found in your plugin