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.01MB] [CPU: ▼5.30ms] Passed 4 tests
An overview of server-side resources used by Login alert by e-mail
Normal server usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.48 ▲0.02 | 38.28 ▼1.56 |
Dashboard /wp-admin | 3.32 ▲0.01 | 49.65 ▼3.63 |
Posts /wp-admin/edit.php | 3.37 ▲0.01 | 47.87 ▲0.59 |
Add New Post /wp-admin/post-new.php | 5.92 ▲0.03 | 90.42 ▼13.00 |
Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 32.07 ▼3.01 |
Server storage [IO: ▲1.23MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
No storage issues were detected
Filesystem: 26 new files
Database: no new tables, 6 new options
New WordPress options |
---|
db_upgraded |
theysaidso_admin_options |
widget_theysaidso_widget |
widget_recent-comments |
can_compress_scripts |
widget_recent-posts |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Login alert by e-mail
This plugin renders optimally with no browser resource issues detected
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,912 ▲166 | 13.59 ▼0.97 | 5.57 ▲3.89 | 42.65 ▲4.82 |
Dashboard /wp-admin | 2,207 ▲19 | 5.76 ▲0.89 | 98.01 ▼20.15 | 38.99 ▼7.35 |
Posts /wp-admin/edit.php | 2,093 ▲4 | 2.17 ▲0.17 | 39.39 ▲2.50 | 38.07 ▲3.57 |
Add New Post /wp-admin/post-new.php | 1,518 ▼15 | 23.28 ▼0.16 | 588.68 ▼2.76 | 47.20 ▼5.85 |
Media Library /wp-admin/upload.php | 1,389 ▲1 | 4.29 ▲0.11 | 94.97 ▼5.48 | 41.13 ▼2.11 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 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
- widget_theysaidso_widget
- theysaidso_admin_options
- widget_recent-posts
- widget_recent-comments
- db_upgraded
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
Even though no errors were found, this is by no means an exhaustive test
SRP 0% from 2 tests
🔹 Tests weight: 20 | It is important to ensure that your PHP files perform no action when accessed directly, respecting the single-responsibility principle
Almost there! Just fix the following items
- 2× PHP files output text when accessed directly:
- > /wp-content/plugins/login-alert-by-e-mail/admin/partials/ruicruz-login-alert-admin-display.php
- > /wp-content/plugins/login-alert-by-e-mail/public/partials/ruicruz-login-alert-public-display.php
- 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/login-alert-by-e-mail/includes/class-ruicruz-login-alert.php:269
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
No browser errors were detected
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 94% from 16 tests
Often overlooked, readme.txt is one of the most important files in your plugin
Attributes that need to be fixed:
- Screenshots: These screenshots have no corresponding images in /assets: #1 (Login with success for image loginok.png.), #2 (Login withbout success for image loginfailed.png)
login-alert-by-e-mail/ruicruz-login-alert.php 85% from 13 tests
The principal PHP file in "Login alert by e-mail" v. 1.0 is loaded by WordPress automatically on each request
It is important to fix the following:
- Main file name: Name the main plugin file the same as the plugin slug ("login-alert-by-e-mail.php" instead of "ruicruz-login-alert.php")
- Text Domain: If you choose to specify the text domain, it must be the same as the plugin slug; optional since WordPress version 4.6
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 plugin218 lines of code in 16 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 12 | 123 | 535 | 212 |
JavaScript | 2 | 4 | 54 | 6 |
CSS | 2 | 0 | 8 | 0 |
PHP code Passed 2 tests
A brief analysis of cyclomatic complexity and code structure for this plugin
There were no cyclomatic complexity issued detected
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.07 |
Average class complexity | 1.43 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 3.00 |
Average method complexity | 1.13 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 3.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 7 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 7 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 23 | |
▷ Static methods | 2 | 8.70% |
▷ Public methods | 18 | 78.26% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 5 | 21.74% |
Functions | 5 | |
▷ Named functions | 5 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 1 | |
▷ Global constants | 1 | 100.00% |
▷ Class constants | 0 | 0.00% |
▷ Public constants | 0 | 0.00% |
Plugin size 50% from 2 tests
Image compression 50% from 2 tests
PNG files should be compressed to save space and minimize bandwidth usage
4 PNG files occupy 1.18MB with 0.70MB in potential savings
Potential savings
Compression of 4 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
assets/loginfailed.png | 43.06KB | 17.61KB | ▼ 59.10% |
assets/banner.png | 926.64KB | 355.97KB | ▼ 61.59% |
assets/loginok.png | 41.75KB | 16.75KB | ▼ 59.87% |
assets/banner-772x250.png | 201.63KB | 88.59KB | ▼ 56.06% |