Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.13MB] [CPU: ▼8.12ms] Passed 4 tests
This is a short check of server-side resources used by Byteplant Email Validator
This plugin does not affect your website's performance
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.56 ▲0.10 | 40.33 ▼0.24 |
| Dashboard /wp-admin | 3.46 ▲0.11 | 48.84 ▼11.51 |
| Posts /wp-admin/edit.php | 3.57 ▲0.22 | 51.19 ▼0.73 |
| Add New Post /wp-admin/post-new.php | 6.04 ▲0.15 | 81.36 ▼20.01 |
| Media Library /wp-admin/upload.php | 3.38 ▲0.15 | 39.33 ▲2.71 |
| Byteplant Email Validator /wp-admin/options-general.php?page=byteplant_email_validator | 3.35 | 39.19 |
Server storage [IO: ▲0.21MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
No storage issues were detected
Filesystem: 36 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_theysaidso_widget |
| theysaidso_admin_options |
| db_upgraded |
| widget_recent-comments |
| can_compress_scripts |
| widget_recent-posts |
Browser metrics Passed 4 tests
An overview of browser requirements for Byteplant Email Validator
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,804 ▲58 | 13.70 ▼0.66 | 1.91 ▲0.05 | 43.38 ▲1.86 |
| Dashboard /wp-admin | 2,207 ▲25 | 5.88 ▼0.05 | 115.56 ▲11.21 | 42.87 ▼3.18 |
| Posts /wp-admin/edit.php | 2,093 ▲4 | 2.00 ▼0.01 | 39.61 ▼0.68 | 34.31 ▼1.38 |
| Add New Post /wp-admin/post-new.php | 1,522 ▲8 | 23.11 ▲5.60 | 600.43 ▼75.08 | 57.16 ▼2.25 |
| Media Library /wp-admin/upload.php | 1,395 ▲7 | 4.28 ▲0.06 | 95.80 ▼17.24 | 40.85 ▼7.33 |
| Byteplant Email Validator /wp-admin/options-general.php?page=byteplant_email_validator | 960 | 1.90 | 23.56 | 28.73 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
These items require your attention
- Zombie WordPress options were found after uninstall: 6 options
- db_upgraded
- can_compress_scripts
- widget_theysaidso_widget
- widget_recent-posts
- widget_recent-comments
- theysaidso_admin_options
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
Everything seems fine, however this is by no means an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle: PHP files have to remain inert when accessed directly, throwing no errors and performing no actions
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/email-validator-by-byteplant/plugin.php:20
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
No browser errors were detected
Optimizations
Plugin configuration 87% from 29 tests
readme.txt 88% from 16 tests
You should put a lot of thought into formatting readme.txt as it is used by WordPress.org to prepare the public listing of your plugin
Attributes that need to be fixed:
- Tags: Too many tags (16 tag instead of maximum 10); only the first 5 tags are used in your directory listing
- Screenshots: Screenshot #1 (Plugin page.) image required
email-validator-by-byteplant/plugin.php 85% from 13 tests
The primary PHP file in "Byteplant Email Validator" version 6.4 is used by WordPress to initiate all plugin functionality
It is important to fix the following:
- Main file name: It is recommended to name the main PHP file as the plugin slug ("email-validator-by-byteplant.php" instead of "plugin.php")
- Description: The description should be shorter than 140 characters (currently 149 characters long)
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
Success! There were no dangerous files found in this plugin1,792 lines of code in 27 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 17 | 341 | 878 | 971 |
| PO File | 4 | 199 | 220 | 626 |
| JavaScript | 4 | 24 | 0 | 177 |
| CSS | 2 | 3 | 0 | 18 |
PHP code Passed 2 tests
This is a short overview of cyclomatic complexity and code structure for this plugin
No cyclomatic complexity issues were detected for this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.19 |
| Average class complexity | 5.79 |
| ▷ Minimum class complexity | 2.00 |
| ▷ Maximum class complexity | 18.00 |
| Average method complexity | 1.63 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 12.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 14 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 14 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 106 | |
| ▷ Static methods | 2 | 1.89% |
| ▷ Public methods | 101 | 95.28% |
| ▷ Protected methods | 3 | 2.83% |
| ▷ Private methods | 2 | 1.89% |
| Functions | 2 | |
| ▷ Named functions | 2 | 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 Passed 2 tests
Image compression Passed 2 tests
All PNG images should be compressed to minimize bandwidth usage for end users
1 PNG file occupies 0.09MB with 0.05MB in potential savings
Potential savings
| Compression of 1 random PNG file using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| screenshot-1.png | 89.65KB | 37.99KB | ▼ 57.62% |