Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices
This plugin's installer ran successfully
Server metrics [RAM: ▲0.00MB] [CPU: ▼3.75ms] Passed 4 tests
A check of server-side resources used by HTTP/1.1 403 Forbidden header on a failed login
This plugin has minimal impact on server resources
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.47 ▲0.00 | 39.07 ▼1.72 |
Dashboard /wp-admin | 3.31 ▲0.01 | 53.74 ▲2.13 |
Posts /wp-admin/edit.php | 3.36 ▲0.00 | 54.22 ▼3.47 |
Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 97.62 ▼7.46 |
Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 35.75 ▼2.35 |
Server storage [IO: ▲0.00MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
This plugin was installed successfully
Filesystem: 2 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_recent-comments |
widget_recent-posts |
theysaidso_admin_options |
db_upgraded |
widget_theysaidso_widget |
can_compress_scripts |
Browser metrics Passed 4 tests
A check of browser resources used by HTTP/1.1 403 Forbidden header on a failed login
This plugin renders optimally with no browser resource issues detected
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,800 ▲54 | 14.47 ▲0.23 | 1.81 ▲0.14 | 39.78 ▼2.04 |
Dashboard /wp-admin | 2,209 ▲30 | 5.90 ▼0.12 | 107.27 ▲1.37 | 42.14 ▼4.27 |
Posts /wp-admin/edit.php | 2,089 ▼3 | 1.99 ▼0.00 | 40.89 ▼3.36 | 36.35 ▼5.21 |
Add New Post /wp-admin/post-new.php | 1,529 ▲10 | 18.08 ▼5.01 | 644.27 ▼49.31 | 53.30 ▼10.07 |
Media Library /wp-admin/upload.php | 1,391 ▲3 | 4.19 ▲0.10 | 98.65 ▼7.80 | 43.22 ▼10.66 |
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 detected upon uninstall: 6 options
- widget_recent-comments
- can_compress_scripts
- widget_recent-posts
- widget_theysaidso_widget
- db_upgraded
- theysaidso_admin_options
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
Everything seems fine, however this is by no means an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | A shallow check of the single-responsibility principle; PHP files should perform no action - including output of placeholder text - and trigger no errors when accessed directly
Please fix the following items
- 1× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/http11-403-forbidden-header-on-a-failed-login/403-headers.php:12
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 93% 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
These attributes need your attention:
- Plugin Name: Please replace "Plugin Name" with the name of your plugin on the first line (
=== http11-403-forbidden-header-on-a-failed-login ===
)
http11-403-forbidden-header-on-a-failed-login/403-headers.php 92% from 13 tests
"HTTP/1.1 403 Forbidden header on a failed login" version 1.0'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:
- Main file name: Please rename the main PHP file in this plugin to the plugin slug ("http11-403-forbidden-header-on-a-failed-login.php" instead of "403-headers.php")
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
There were no executable files found in this plugin4 lines of code in 1 file:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 1 | 1 | 9 | 4 |
PHP code Passed 2 tests
A brief analysis 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.00 |
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 | 1 | |
▷ Named functions | 0 | 0.00% |
▷ Anonymous functions | 1 | 100.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
Using a strong compression for your PNG files is a great way to speed-up your plugin
PNG images were not found in this plugin