Benchmarks
Plugin footprint Passed 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
Installer ran successfully
Server metrics [RAM: ▲0.04MB] [CPU: ▼141.50ms] Passed 4 tests
Server-side resources used by Protect Login Page
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 2.88 ▲0.16 | 40.58 ▲16.47 |
| Dashboard /wp-admin | 3.10 ▲0.05 | 48.19 ▲0.78 |
| Posts /wp-admin/edit.php | 3.16 ▲0.05 | 46.78 ▼1.44 |
| Add New Post /wp-admin/post-new.php | 5.46 ▲0.03 | 94.20 ▼567.28 |
| Media Library /wp-admin/upload.php | 3.05 ▲0.05 | 37.53 ▲1.93 |
| Login Page PIN /wp-admin/options-general.php?page=ee-protect-login-page | 2.99 | 31.87 |
Server storage [IO: ▲0.09MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
There were no storage issued detected upon installing this plugin
Filesystem: 17 new files
Database: no new tables, no new options
Browser metrics Passed 4 tests
Checking browser requirements for Protect Login Page
Normal browser usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 3,684 ▲88 | 15.91 ▼0.04 | 8.42 ▲0.00 | 51.16 ▼1.70 |
| Dashboard /wp-admin | 2,972 ▲42 | 6.02 ▲0.07 | 159.98 ▲3.66 | 119.04 ▼6.46 |
| Posts /wp-admin/edit.php | 2,744 ▲5 | 2.69 ▲0.00 | 71.61 ▲1.37 | 91.96 ▲5.96 |
| Add New Post /wp-admin/post-new.php | 1,686 ▲3 | 18.77 ▲0.05 | 376.22 ▼22.43 | 118.25 ▲5.88 |
| Media Library /wp-admin/upload.php | 1,815 ▲8 | 5.02 ▲0.02 | 161.93 ▲4.94 | 128.74 ▲2.95 |
| Login Page PIN /wp-admin/options-general.php?page=ee-protect-login-page | 1,097 | 2.34 | 58.44 | 110.57 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] Passed 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
This plugin's uninstaller ran successfully
Smoke tests 50% from 4 tests
Server-side errors 0% from 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
These errors were triggered by the plugin
- > GET request to /wp-admin/options-general.php?page=ee-protect-login-page
- > Notice in wp-content/plugins/protect-login-page/ee-protect-login-page.php+84
Undefined index: eePLP
- > GET request to /wp-admin/options-general.php?page=ee-protect-login-page
- > Notice in wp-content/plugins/protect-login-page/ee-protect-login-page.php+259
Undefined variable: eeOutput
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
The following issues need your attention
- 4× PHP files perform the action of outputting non-empty strings when accessed directly:
- > /wp-content/plugins/protect-login-page/support/ee-plugin-author.php
- > /wp-content/plugins/protect-login-page/support/ee-donations.php
- > /wp-content/plugins/protect-login-page/support/ee-support-functions.php
- > /wp-content/plugins/protect-login-page/support/ee-plugin-support.php
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
There were no browser issues found
Optimizations
Plugin configuration 86% from 29 tests
readme.txt 94% 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 your attention:
- Tags: There were no tags found
protect-login-page/ee-protect-login-page.php 77% from 13 tests
Analyzing the main PHP file in "Protect Login Page" version 1.0.3
You should first fix the following items:
- Description: Keep the plugin description shorter than 140 characters (currently 168 characters long)
- Text Domain: The text domain must be the same as the plugin slug, although optional since WordPress version 4.6
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("protect-login-page.php" instead of "ee-protect-login-page.php")
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
Everything looks great! No dangerous files found in this plugin615 lines of code in 8 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 6 | 299 | 86 | 411 |
| CSS | 1 | 64 | 120 | 181 |
| JavaScript | 1 | 8 | 3 | 23 |
PHP code Passed 2 tests
This plugin's cyclomatic complexity and code structure detailed below
There are no cyclomatic complexity problems detected for this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.44 |
| 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 | 9 | |
| ▷ Named functions | 9 | 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
Often times overlooked, PNG files can occupy unnecessary space in your plugin
1 PNG file occupies 0.01MB with 0.01MB in potential savings
Potential savings
| Compression of 1 random PNG file using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| support/images/ee-show-support.png | 11.08KB | 5.79KB | ▼ 47.75% |