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.28MB] [CPU: ▲2.20ms] Passed 4 tests
A check of server-side resources used by Mail logging - WP Mail Catcher
This plugin has minimal impact on server resources
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.78 ▲0.32 | 39.86 ▲1.41 |
| Dashboard /wp-admin | 3.61 ▲0.30 | 46.49 ▲1.59 |
| Posts /wp-admin/edit.php | 3.66 ▲0.30 | 49.99 ▲6.17 |
| Add New Post /wp-admin/post-new.php | 6.15 ▲0.26 | 94.34 ▲0.17 |
| Media Library /wp-admin/upload.php | 3.47 ▲0.24 | 37.41 ▲5.62 |
| Settings /wp-admin/admin.php?page=wp-mail-catcher-settings | 3.47 | 34.50 |
| WP Mail Catcher /wp-admin/admin.php?page=wp-mail-catcher | 3.69 | 42.18 |
Server storage [IO: ▲0.26MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
This plugin was installed successfully
Filesystem: 47 new files
Database: 1 new table, 6 new options
| New tables |
|---|
| wp_mail_catcher_logs |
| New WordPress options |
|---|
| widget_theysaidso_widget |
| can_compress_scripts |
| widget_recent-posts |
| theysaidso_admin_options |
| db_upgraded |
| widget_recent-comments |
Browser metrics Passed 4 tests
Checking browser requirements for Mail logging - WP Mail Catcher
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,849 ▲87 | 14.34 ▼0.38 | 1.86 ▲0.34 | 40.08 ▲0.75 |
| Dashboard /wp-admin | 2,223 ▲42 | 5.62 ▼0.10 | 86.18 ▼26.73 | 40.41 ▼2.14 |
| Posts /wp-admin/edit.php | 2,134 ▲37 | 1.99 ▼0.09 | 40.49 ▼0.02 | 35.22 ▼0.59 |
| Add New Post /wp-admin/post-new.php | 1,555 ▲29 | 23.47 ▲0.29 | 619.93 ▼49.77 | 47.97 ▼0.97 |
| Media Library /wp-admin/upload.php | 1,437 ▲40 | 4.19 ▼0.01 | 95.29 ▼7.41 | 41.56 ▼3.77 |
| Settings /wp-admin/admin.php?page=wp-mail-catcher-settings | 1,601 | 1.69 | 32.19 | 29.94 |
| WP Mail Catcher /wp-admin/admin.php?page=wp-mail-catcher | 2,095 | 6.77 | 138.85 | 65.91 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
It is recommended to fix the following
- Zombie WordPress options detected upon uninstall: 6 options
- widget_recent-comments
- widget_theysaidso_widget
- theysaidso_admin_options
- can_compress_scripts
- widget_recent-posts
- db_upgraded
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
Even though everything seems fine, this is not an exhaustive test
SRP 0% from 2 tests
🔹 Tests weight: 20 | SRP (Single-Responsibility Principle) - PHP files must act as libraries and never output text or perform any action when accessed directly in a browser
Please take a closer look at the following
- 1× PHP files output text when accessed directly:
- > /wp-content/plugins/wp-mail-catcher/src/Views/TextMessage.php
- 9× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Fatal error
Trait 'WpMailCatcher\\Loggers\\LogHelper' not found in wp-content/plugins/wp-mail-catcher/src/Loggers/BuddyPress.php on line 7
- > PHP Fatal error
Uncaught Error: Class 'WpMailCatcher\\GeneralHelper' not found in wp-content/plugins/wp-mail-catcher/src/Views/HtmlMessage.php:5
- > PHP Fatal error
Uncaught Error: Class 'WpMailCatcher\\DatabaseUpgradeManager' not found in wp-content/plugins/wp-mail-catcher/src/Views/Log.php:7
- > PHP Fatal error
Uncaught Error: Class 'WpMailCatcher\\GeneralHelper' not found in wp-content/plugins/wp-mail-catcher/src/Views/NewMessageModal.php:9
- > PHP Fatal error
Uncaught Error: Class 'WP_List_Table' not found in wp-content/plugins/wp-mail-catcher/src/MailAdminTable.php:8
- > PHP Fatal error
Uncaught Error: Call to undefined function WpMailCatcher\\admin_url() in wp-content/plugins/wp-mail-catcher/src/GeneralHelper.php:46
- > PHP Fatal error
Uncaught Error: Class 'WpMailCatcher\\GeneralHelper' not found in wp-content/plugins/wp-mail-catcher/src/Views/Footer.php:8
- > PHP Fatal error
Uncaught Error: Class 'WpMailCatcher\\Models\\Settings' not found in wp-content/plugins/wp-mail-catcher/src/Views/Settings.php:7
- > PHP Fatal error
Trait 'WpMailCatcher\\Loggers\\LogHelper' not found in wp-content/plugins/wp-mail-catcher/src/Loggers/WpMail.php on line 7
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
No browser issues were found
Optimizations
Plugin configuration 90% from 29 tests
readme.txt Passed 16 tests
The readme.txt file uses markdown syntax to describe your plugin to the world
7 plugin tags: email logger, crm, logging, email logging, mail...
wp-mail-catcher/WpMailCatcher.php 77% from 13 tests
"Mail logging - WP Mail Catcher" version 2.1.6's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
Please make the necessary changes and fix the following:
- Description: The description should be shorter than 140 characters (currently 178 characters long)
- Text Domain: The text domain follows the same naming rules as the plugin slug: lowercase characters and dashes
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("wp-mail-catcher.php" instead of "WpMailCatcher.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is an overview of programming languages used in this plugin; dangerous file extensions are not allowed
There were no executable files found in this plugin2,892 lines of code in 41 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 36 | 547 | 527 | 2,680 |
| PO File | 1 | 63 | 64 | 176 |
| JSON | 2 | 0 | 0 | 34 |
| CSS | 1 | 0 | 0 | 1 |
| JavaScript | 1 | 0 | 0 | 1 |
PHP code Passed 2 tests
An overview of cyclomatic complexity and code structure
No complexity issues detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.40 |
| Average class complexity | 14.48 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 54.00 |
| Average method complexity | 2.94 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 47.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 5 | |
| Interfaces | 1 | |
| Traits | 1 | |
| Classes | 19 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 19 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 137 | |
| ▷ Static methods | 63 | 45.99% |
| ▷ Public methods | 122 | 89.05% |
| ▷ Protected methods | 3 | 2.19% |
| ▷ Private methods | 12 | 8.76% |
| Functions | 16 | |
| ▷ Named functions | 0 | 0.00% |
| ▷ Anonymous functions | 16 | 100.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
Using a strong compression for your PNG files is a great way to speed-up your plugin
1 PNG file occupies 0.00MB with 0.00MB in potential savings
Potential savings
| Compression of 1 random PNG file using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/file-icon.png | 1.15KB | 0.20KB | ▼ 82.45% |