Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
Install script ran successfully
Server metrics [RAM: ▲0.06MB] [CPU: ▼7.56ms] Passed 4 tests
Analyzing server-side resources used by EVA - Email Validator
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.77 ▲0.04 | 46.03 ▼0.00 |
Dashboard /wp-admin | 3.70 ▲0.07 | 52.39 ▼19.88 |
Posts /wp-admin/edit.php | 3.75 ▲0.07 | 53.70 ▼0.02 |
Add New Post /wp-admin/post-new.php | 6.22 ▲0.07 | 87.67 ▼10.34 |
Media Library /wp-admin/upload.php | 3.56 ▲0.07 | 39.23 ▲0.41 |
EVA - Email Validator /wp-admin/options-general.php?page=eva_email_validator | 3.52 | 36.65 |
Server storage [IO: ▲0.36MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
There were no storage issued detected upon installing this plugin
Filesystem: 11 new files
Database: no new tables, 6 new options
New WordPress options |
---|
can_compress_scripts |
theysaidso_admin_options |
widget_recent-comments |
widget_recent-posts |
db_upgraded |
widget_theysaidso_widget |
Browser metrics Passed 4 tests
An overview of browser requirements for EVA - Email Validator
Normal browser usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,793 ▲47 | 14.40 ▲0.38 | 1.86 ▲0.06 | 38.14 ▼4.42 |
Dashboard /wp-admin | 2,202 ▲28 | 5.56 ▼0.04 | 86.32 ▼34.18 | 38.82 ▼3.71 |
Posts /wp-admin/edit.php | 2,104 ▲4 | 2.04 ▼0.00 | 39.94 ▼1.32 | 35.95 ▲0.81 |
Add New Post /wp-admin/post-new.php | 1,548 ▲19 | 23.08 ▲5.50 | 666.56 ▲49.68 | 56.31 ▲8.93 |
Media Library /wp-admin/upload.php | 1,398 ▼2 | 4.19 ▼0.05 | 98.73 ▼9.54 | 42.79 ▼1.55 |
EVA - Email Validator /wp-admin/options-general.php?page=eva_email_validator | 852 | 2.01 | 23.06 | 31.56 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
Please fix the following items
- This plugin does not fully uninstall, leaving 6 options in the database
- db_upgraded
- widget_recent-posts
- widget_theysaidso_widget
- can_compress_scripts
- widget_recent-comments
- theysaidso_admin_options
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a short smoke test looking for server-side errors
Even though no errors were found, this is by no means an exhaustive test
SRP 50% 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
Please take a closer look at the following
- 1× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/eva-email-validator/plugin.php:19
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the browser (console and network errors and warnings)
No browser errors were detected
Optimizations
Plugin configuration 86% from 29 tests
readme.txt 94% from 16 tests
Often overlooked, readme.txt is one of the most important files in your plugin
These attributes need your attention:
- Screenshots: Screenshot #1 (Configuration Page.) image required
eva-email-validator/plugin.php 77% from 13 tests
"EVA - Email Validator" version 1.1's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
The following require your attention:
- Text Domain: The text domain should only use lowercase characters and dashes
- Description: Keep the plugin description shorter than 140 characters (currently 240 characters long)
- Main file name: The principal plugin file should be the same as the plugin slug ("eva-email-validator.php" instead of "plugin.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is a short overview of programming languages used in this plugin, detecting executable files
No dangerous file extensions were detected464 lines of code in 9 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 9 | 141 | 323 | 464 |
PHP code Passed 2 tests
Analyzing logical lines of code, cyclomatic complexity, and other code metrics
All good! No complexity issues found
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.21 |
Average class complexity | 5.86 |
▷ Minimum class complexity | 2.00 |
▷ Maximum class complexity | 10.00 |
Average method complexity | 1.71 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 6.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 | 48 | |
▷ Static methods | 2 | 4.17% |
▷ Public methods | 47 | 97.92% |
▷ Protected methods | 1 | 2.08% |
▷ Private methods | 0 | 0.00% |
Functions | 1 | |
▷ Named functions | 1 | 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.34MB with 0.26MB in potential savings
Potential savings
Compression of 1 random PNG file using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
screenshot-1.png | 346.89KB | 78.46KB | ▼ 77.38% |