Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
Installer ran successfully
Server metrics [RAM: ▼0.13MB] [CPU: ▼10.17ms] Passed 4 tests
Server-side resources used by Frontend HTTP Auth Protection
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 2.84 ▼0.62 | 18.78 ▼24.37 |
| Dashboard /wp-admin | 3.33 ▲0.03 | 48.78 ▲1.02 |
| Posts /wp-admin/edit.php | 3.39 ▲0.03 | 45.26 ▼4.73 |
| Add New Post /wp-admin/post-new.php | 5.91 ▲0.03 | 88.28 ▼10.69 |
| Media Library /wp-admin/upload.php | 3.26 ▲0.03 | 36.00 ▼0.89 |
| Frontend HTTP Authentication /wp-admin/options-general.php?page=fhauth_setting | 3.28 | 38.11 |
Server storage [IO: ▲0.19MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
This plugin was installed successfully
Filesystem: 7 new files
Database: no new tables, 7 new options
| New WordPress options |
|---|
| widget_recent-posts |
| db_upgraded |
| fhauth_setting |
| widget_recent-comments |
| widget_theysaidso_widget |
| theysaidso_admin_options |
| can_compress_scripts |
Browser metrics Passed 4 tests
Frontend HTTP Auth Protection: an overview of browser usage
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,425 ▼346 | 14.70 ▲0.34 | 0.68 ▼1.44 | 3.56 ▼43.10 |
| Dashboard /wp-admin | 2,213 ▲25 | 4.85 ▼0.01 | 106.11 ▼3.91 | 40.09 ▼5.86 |
| Posts /wp-admin/edit.php | 2,096 ▲7 | 2.05 ▲0.01 | 35.71 ▼5.26 | 33.30 ▼5.66 |
| Add New Post /wp-admin/post-new.php | 1,517 ▼7 | 23.53 ▲0.09 | 667.45 ▼23.47 | 80.16 ▲28.25 |
| Media Library /wp-admin/upload.php | 1,386 ▲4 | 4.23 ▲0.05 | 100.45 ▲3.01 | 44.75 ▼1.29 |
| Frontend HTTP Authentication /wp-admin/options-general.php?page=fhauth_setting | 1,536 | 6.66 | 163.27 | 69.27 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
It is recommended to fix the following
- This plugin did not uninstall successfully, leaving 6 options in the database
- can_compress_scripts
- db_upgraded
- widget_recent-posts
- theysaidso_admin_options
- widget_recent-comments
- widget_theysaidso_widget
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
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
The following issues need your attention
- 1× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Fatal error
Uncaught Error: Call to undefined function register_activation_hook() in wp-content/plugins/frontend-http-authentication-protection/frontend-http-authentication-protection.php:16
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
There were no browser issues found
Optimizations
Plugin configuration 96% 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
5 plugin tags: frontend, protection, auth, security, http
frontend-http-authentication-protection/frontend-http-authentication-protection.php 92% from 13 tests
Analyzing the main PHP file in "Frontend HTTP Auth Protection" version 0.1
You should first fix the following items:
- Description: The description should be shorter than 140 characters (currently 471 characters long)
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short check of programming languages and file extensions; no executable files are allowed
No dangerous file extensions were detected168 lines of code in 2 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 2 | 27 | 52 | 168 |
PHP code Passed 2 tests
Analyzing cyclomatic complexity and code structure
Everything seems fine, there were no complexity issues found
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.30 |
| 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 | 11 | |
| ▷ Named functions | 11 | 100.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
All PNG images should be compressed to minimize bandwidth usage for end users
3 PNG files occupy 0.16MB with 0.10MB in potential savings
Potential savings
| Compression of 3 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/screenshot-1.png | 127.05KB | 39.24KB | ▼ 69.12% |
| assets/screenshot-2.png | 22.01KB | 8.69KB | ▼ 60.51% |
| assets/screenshot-3.png | 11.28KB | 4.17KB | ▼ 62.97% |