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
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.33MB] [CPU: ▼3.51ms] Passed 4 tests
An overview of server-side resources used by Emails Catch All
This plugin has minimal impact on server resources
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.81 ▲0.34 | 41.43 ▲3.22 |
Dashboard /wp-admin | 3.65 ▲0.31 | 50.81 ▼11.36 |
Posts /wp-admin/edit.php | 3.76 ▲0.41 | 57.68 ▲9.22 |
Add New Post /wp-admin/post-new.php | 6.23 ▲0.35 | 81.83 ▼10.42 |
Media Library /wp-admin/upload.php | 3.57 ▲0.34 | 42.76 ▲4.53 |
Emails Catch All /wp-admin/options-general.php?page=emails-catch-all-settings | 3.55 | 36.50 |
Server storage [IO: ▲0.30MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
The plugin installed successfully
Filesystem: 12 new files
Database: 1 new table, 8 new options
New tables |
---|
emails_catch_all |
New WordPress options |
---|
can_compress_scripts |
widget_recent-comments |
secas_plugin_notice_db_ver |
widget_theysaidso_widget |
emails_catch_all_settings_db_ver |
widget_recent-posts |
db_upgraded |
theysaidso_admin_options |
Browser metrics Passed 4 tests
An overview of browser requirements for Emails Catch All
Normal browser usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,864 ▲117 | 14.67 ▲0.35 | 1.69 ▲0.08 | 43.30 ▼0.28 |
Dashboard /wp-admin | 2,272 ▲94 | 5.56 ▼0.14 | 83.05 ▼32.89 | 78.11 ▲32.05 |
Posts /wp-admin/edit.php | 2,181 ▲81 | 2.07 ▲0.07 | 39.85 ▲3.71 | 37.77 ▲1.29 |
Add New Post /wp-admin/post-new.php | 1,747 ▲221 | 22.45 ▼1.01 | 722.96 ▲16.33 | 43.74 ▼17.59 |
Media Library /wp-admin/upload.php | 1,477 ▲74 | 4.08 ▼0.12 | 99.88 ▼3.41 | 82.39 ▲36.31 |
Emails Catch All /wp-admin/options-general.php?page=emails-catch-all-settings | 1,139 | 2.18 | 26.57 | 49.38 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 50% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
Please fix the following items
- The uninstall procedure failed, leaving 1 table in the database
- emails_catch_all
- Zombie WordPress options were found after uninstall: 8 options
- widget_recent-posts
- can_compress_scripts
- widget_theysaidso_widget
- theysaidso_admin_options
- emails_catch_all_settings_db_ver
- secas_plugin_notice_db_ver
- widget_recent-comments
- db_upgraded
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 | A shallow check of the single-responsibility principle; PHP files should perform no action - including output of placeholder text - and trigger no errors when accessed directly
The following issues need your attention
- 1× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Fatal error
Uncaught Error: Call to undefined function plugin_dir_path() in wp-content/plugins/emails-catch-all/emails-catch-all.php:39
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
No browser issues were found
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file describes your plugin functionality and requirements and it is parsed to prepare the your plugin's listing
Attributes that need to be fixed:
- Requires at least: Version not formatted correctly
emails-catch-all/emails-catch-all.php 85% from 13 tests
"Emails Catch All" version 3.4.3's primary PHP file adds more information about the plugin and serves as the entry point for WordPress
Please make the necessary changes and fix the following:
- Description: The description should be shorter than 140 characters (currently 420 characters long)
- Text Domain: The text domain is optional since WordPress version 4.6; if you do specify it, it must be the same as the plugin slug
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
No dangerous file extensions were detected2,110 lines of code in 6 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 2 | 207 | 448 | 1,850 |
PO File | 1 | 119 | 129 | 257 |
CSS | 2 | 0 | 0 | 2 |
JavaScript | 1 | 0 | 0 | 1 |
PHP code Passed 2 tests
A short review of cyclomatic complexity and code structure
Great job! No cyclomatic complexity issues were detected in this plugin
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.32 |
Average class complexity | 253.00 |
▷ Minimum class complexity | 253.00 |
▷ Maximum class complexity | 253.00 |
Average method complexity | 5.27 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 49.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 1 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 1 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 59 | |
▷ Static methods | 57 | 96.61% |
▷ Public methods | 58 | 98.31% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 1 | 1.69% |
Functions | 0 | |
▷ Named functions | 0 | 0.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 10 | |
▷ Global constants | 7 | 70.00% |
▷ Class constants | 3 | 30.00% |
▷ Public constants | 3 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
All PNG images should be compressed to minimize bandwidth usage for end users
2 PNG files occupy 0.04MB with 0.03MB in potential savings
Potential savings
Compression of 2 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
assets/images/icon-128x128.png | 26.02KB | 13.23KB | ▼ 49.14% |
assets/images/buy-me-a-coffee.png | 19.75KB | 7.15KB | ▼ 63.78% |