Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
This plugin's installer ran successfully
Server metrics [RAM: ▲0.01MB] [CPU: ▲0.84ms] Passed 4 tests
This is a short check of server-side resources used by Login with Username or Email
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.47 ▲0.01 | 36.37 ▼5.47 |
| Dashboard /wp-admin | 3.31 ▲0.01 | 52.34 ▲5.03 |
| Posts /wp-admin/edit.php | 3.36 ▲0.01 | 49.36 ▼0.50 |
| Add New Post /wp-admin/post-new.php | 5.89 ▲0.01 | 98.33 ▲7.74 |
| Media Library /wp-admin/upload.php | 3.23 ▲0.01 | 36.22 ▲4.30 |
Server storage [IO: ▲0.06MB] [DB: ▲0.07MB] Passed 3 tests
Filesystem and database footprint
This plugin was installed successfully
Filesystem: 5 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_recent-posts |
| theysaidso_admin_options |
| widget_recent-comments |
| db_upgraded |
| can_compress_scripts |
| widget_theysaidso_widget |
Browser metrics Passed 4 tests
Login with Username or Email: an overview of browser usage
This plugin has a minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,812 ▲77 | 13.18 ▼1.20 | 1.58 ▼0.23 | 36.07 ▼9.09 |
| Dashboard /wp-admin | 2,228 ▲40 | 5.88 ▲0.01 | 108.52 ▲0.19 | 71.63 ▲29.05 |
| Posts /wp-admin/edit.php | 2,114 ▲22 | 2.11 ▲0.09 | 38.27 ▼2.35 | 33.83 ▼3.69 |
| Add New Post /wp-admin/post-new.php | 1,554 ▲37 | 18.39 ▲0.90 | 642.75 ▲59.64 | 66.25 ▲10.41 |
| Media Library /wp-admin/upload.php | 1,413 ▲25 | 4.26 ▲0.01 | 96.50 ▼1.19 | 81.09 ▲39.17 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.07MB] 75% from 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
It is recommended to fix the following
- Zombie WordPress options were found after uninstall: 6 options
- can_compress_scripts
- theysaidso_admin_options
- widget_recent-comments
- widget_recent-posts
- db_upgraded
- widget_theysaidso_widget
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
Even though no errors were found, this is by no means an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | SRP (Single-Responsibility Principle) - PHP files must act as libraries and never output text or perform any action when accessed directly in a browser
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_filter() in wp-content/plugins/login-with-username-or-email/email_login.php:14
- > 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 96% from 29 tests
readme.txt Passed 16 tests
The readme.txt file is important because it is parsed by WordPress.org for the public listing of your plugin
6 plugin tags: login with email or username, username, login with email address, logging in with email, login...
login-with-username-or-email/email_login.php 92% from 13 tests
The main file in "Login with Username or Email" v. 2.7 serves as a complement to information provided in readme.txt and as the entry point to the plugin
Please take the time to fix the following:
- Main file name: It is recommended to name the main PHP file as the plugin slug ("login-with-username-or-email.php" instead of "email_login.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are not allowed as they can serve as attack vectors
There were no executable files found in this plugin79 lines of code in 2 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 1 | 30 | 34 | 70 |
| HTML | 1 | 1 | 0 | 9 |
PHP code Passed 2 tests
An overview of cyclomatic complexity and code structure
Everything seems fine, there were no complexity issues found
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.48 |
| 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 | 7 | |
| ▷ Named functions | 7 | 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
Using a strong compression for your PNG files is a great way to speed-up your plugin
2 PNG files occupy 0.05MB with 0.04MB in potential savings
Potential savings
| Compression of 2 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/screenshot-1.png | 26.42KB | 6.38KB | ▼ 75.87% |
| assets/screenshot-2.png | 27.83KB | 7.48KB | ▼ 73.13% |