Benchmarks
Plugin footprint 65% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices
Installer ran successfully
Server metrics [RAM: ▼0.93MB] [CPU: ▼37.29ms] Passed 4 tests
Server-side resources used by TrueMail Email Validator
This plugin has minimal impact on server resources
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.47 ▲0.00 | 41.63 ▼4.17 |
| Dashboard /wp-admin | 3.03 ▼0.32 | 28.09 ▼36.00 |
| Posts /wp-admin/edit.php | 3.03 ▼0.33 | 25.50 ▼23.71 |
| Add New Post /wp-admin/post-new.php | 3.03 ▼2.86 | 26.26 ▼75.95 |
| Media Library /wp-admin/upload.php | 3.03 ▼0.20 | 22.91 ▼13.50 |
| TrueMail Email Validator /wp-admin/options-general.php?page=truemail-email-validator | 3.03 | 29.38 |
Server storage [IO: ▲0.04MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
This plugin was installed successfully
Filesystem: 4 new files
Database: no new tables, 7 new options
| New WordPress options |
|---|
| widget_theysaidso_widget |
| db_upgraded |
| widget_recent-posts |
| can_compress_scripts |
| TrueMail Api Key |
| theysaidso_admin_options |
| widget_recent-comments |
Browser metrics Passed 4 tests
An overview of browser requirements for TrueMail Email Validator
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,813 ▲52 | 14.64 ▲0.36 | 2.12 ▲0.09 | 43.41 ▼1.36 |
| Dashboard /wp-admin | 2,216 ▲36 | 5.55 ▼0.12 | 86.72 ▼3.26 | 36.61 ▼2.10 |
| Posts /wp-admin/edit.php | 2,130 ▲30 | 1.99 ▲0.00 | 36.18 ▼1.87 | 37.16 ▲3.80 |
| Add New Post /wp-admin/post-new.php | 1,393 ▼133 | 20.72 ▼2.52 | 597.52 ▼145.37 | 33.65 ▼20.60 |
| Media Library /wp-admin/upload.php | 1,427 ▲27 | 4.25 ▲0.10 | 102.72 ▼16.24 | 42.09 ▼6.43 |
| TrueMail Email Validator /wp-admin/options-general.php?page=truemail-email-validator | 877 | 2.16 | 27.82 | 29.48 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 50% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
The following items require your attention
- Uninstall procedure had uncaught errors
- > Notice in wp-content/plugins/truemail-email-validator/includes/tmp-functions.php+129
Trying to access array offset on value of type bool
- Zombie WordPress options detected upon uninstall: 7 options
- widget_recent-posts
- db_upgraded
- TrueMail Api Key
- widget_theysaidso_widget
- widget_recent-comments
- can_compress_scripts
- theysaidso_admin_options
Smoke tests 50% from 4 tests
Server-side errors 0% from 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
Almost there, just fix the following server-side errors
- > GET request to /wp-admin/options-general.php?page=truemail-email-validator
- > Notice in wp-content/plugins/truemail-email-validator/includes/tmp-functions.php+129
Trying to access array offset on value of type bool
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
- 2× PHP files trigger server errors when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/truemail-email-validator/includes/tmp-functions.php:8
- > PHP Fatal error
Uncaught Error: Call to undefined function plugin_dir_path() in wp-content/plugins/truemail-email-validator/truemail-plugin.php:17
- > 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 issues were found
Optimizations
Plugin configuration 93% from 29 tests
readme.txt Passed 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
7 plugin tags: email tester, email validation, email verify, email verifier, real-time form validation...
truemail-email-validator/truemail-plugin.php 85% from 13 tests
The entry point to "TrueMail Email Validator" version 1.0.0 is a PHP file that has certain tags in its header comment area
Please take the time to fix the following:
- Text Domain: The text domain must be the same as the plugin slug, although optional since WordPress version 4.6
- Main file name: It is recommended to name the main PHP file as the plugin slug ("truemail-email-validator.php" instead of "truemail-plugin.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short review of files and their extensions; it is not recommended to include executable files
Everything looks great! No dangerous files found in this plugin202 lines of code in 3 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 2 | 26 | 14 | 111 |
| Markdown | 1 | 44 | 0 | 91 |
PHP code Passed 2 tests
This is a short overview of cyclomatic complexity and code structure for this plugin
There are no cyclomatic complexity problems detected for this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.45 |
| 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 | 11 | |
| ▷ Named functions | 11 | 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
All PNG images should be compressed to minimize bandwidth usage for end users
No PNG files were detected