Benchmarks
Plugin footprint 65% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
Install script ran successfully
Server metrics [RAM: ▲1.02MB] [CPU: ▲3.89ms] Passed 4 tests
This is a short check of server-side resources used by WP Mail Logging
Normal server usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 4.52 ▲1.06 | 46.33 ▲7.09 |
Dashboard /wp-admin | 4.35 ▲1.05 | 52.83 ▲4.36 |
Posts /wp-admin/edit.php | 4.40 ▲1.05 | 58.62 ▲4.93 |
Add New Post /wp-admin/post-new.php | 6.87 ▲0.98 | 88.49 ▼0.84 |
Media Library /wp-admin/upload.php | 4.21 ▲0.98 | 44.71 ▲9.26 |
SMTP /wp-admin/admin.php?page=wpml_plugin_log&tab=smtp | 4.22 | 41.56 |
Settings /wp-admin/admin.php?page=wpml_plugin_log&tab=settings | 4.21 | 41.48 |
Email Log /wp-admin/admin.php?page=wpml_plugin_log | 4.29 | 43.33 |
Server storage [IO: ▲1.32MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
The plugin installed successfully
Filesystem: 132 new files
Database: 1 new table, 9 new options
New tables |
---|
wp_wpml_mails |
New WordPress options |
---|
wp_mail_logging_activated_time |
widget_theysaidso_widget |
db_upgraded |
WPML_Plugin__version |
can_compress_scripts |
theysaidso_admin_options |
widget_recent-posts |
widget_recent-comments |
wp_mail_logging_user_feedback_notice |
Browser metrics Passed 4 tests
An overview of browser requirements for WP Mail Logging
Minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,848 ▲91 | 13.30 ▼1.00 | 4.47 ▲2.42 | 39.48 ▼2.93 |
Dashboard /wp-admin | 2,254 ▲63 | 4.87 ▼0.18 | 105.46 ▲1.85 | 39.97 ▼7.35 |
Posts /wp-admin/edit.php | 2,137 ▲48 | 2.03 ▲0.03 | 40.77 ▼0.60 | 34.65 ▼1.37 |
Add New Post /wp-admin/post-new.php | 1,563 ▲27 | 23.48 ▲0.11 | 663.36 ▼4.24 | 52.72 ▼2.14 |
Media Library /wp-admin/upload.php | 1,439 ▲51 | 4.21 ▼0.04 | 95.50 ▼5.06 | 42.49 ▼0.32 |
SMTP /wp-admin/admin.php?page=wpml_plugin_log&tab=smtp | 998 | 1.89 | 25.24 | 41.53 |
Settings /wp-admin/admin.php?page=wpml_plugin_log&tab=settings | 1,566 | 1.80 | 28.92 | 39.42 |
Email Log /wp-admin/admin.php?page=wpml_plugin_log | 1,330 | 1.77 | 27.69 | 37.54 |
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
Please fix the following items
- This plugin does not fully uninstall, leaving 1 table in the database
- wp_wpml_mails
- Zombie WordPress options were found after uninstall: 9 options
- can_compress_scripts
- widget_theysaidso_widget
- widget_recent-comments
- widget_recent-posts
- db_upgraded
- wp_mail_logging_activated_time
- theysaidso_admin_options
- wp_mail_logging_user_feedback_notice
- WPML_Plugin__version
Smoke tests 75% 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 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
Please take a closer look at the following
- 33× PHP files trigger server errors when accessed directly (only 10 are shown):
- > PHP Fatal error
require(): Failed opening required 'vendor/autoload.php' (include_path='.:/usr/share/php') in wp-content/plugins/wp-mail-logging/lib/vendor/brandonwamboldt/wp-orm/wp-orm.php on line 13
- > PHP Fatal error
Uncaught Error: Interface 'No3x\\WPML\\ORM\\ModelInterface' not found in wp-content/plugins/wp-mail-logging/lib/vendor/brandonwamboldt/wp-orm/src/BaseModel.php:10
- > PHP Fatal error
Uncaught Error: Class 'No3x\\WPML\\ORM\\BaseModel' not found in wp-content/plugins/wp-mail-logging/lib/vendor/brandonwamboldt/wp-orm/src/Model/Post.php:13
- > PHP Fatal error
Uncaught Error: Class 'No3x\\WPML\\Renderer\\Format\\HeadingsRenderer' not found in wp-content/plugins/wp-mail-logging/src/Renderer/Format/RawRenderer.php:11
- > PHP Fatal error
require_once(): Failed opening required 'ABSPATHwp-admin/includes/class-wp-upgrader-skin.php' (include_path='.:/usr/share/php') in wp-content/plugins/wp-mail-logging/src/inc/Helpers/PluginSilentUpgraderSkin.php on line 6
- > PHP Warning
require_once(ABSPATHwp-admin/includes/class-wp-upgrader.php): failed to open stream: No such file or directory in wp-content/plugins/wp-mail-logging/src/inc/Helpers/PluginSilentUpgrader.php on line 10
- > PHP Fatal error
Uncaught Error: Class 'No3x\\WPML\\ORM\\BaseModel' not found in wp-content/plugins/wp-mail-logging/lib/vendor/brandonwamboldt/wp-orm/src/Model/User.php:13
- > PHP Fatal error
Uncaught Error: Interface 'No3x\\WPML\\IHooks' not found in wp-content/plugins/wp-mail-logging/src/Renderer/WPML_MailRenderer_AJAX_Handler.php:11
- > PHP Fatal error
Uncaught Error: Class 'No3x\\WPML\\Renderer\\Column\\GenericColumn' not found in wp-content/plugins/wp-mail-logging/src/Renderer/Column/SubjectColumn.php:8
- > PHP Fatal error
Uncaught Error: Class 'No3x\\WPML\\Renderer\\Column\\GenericColumn' not found in wp-content/plugins/wp-mail-logging/src/Renderer/Column/TimestampColumn.php:6
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 97% from 29 tests
readme.txt 94% 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
Please fix the following attributes:
- Screenshots: A description for screenshot #4 is missing in wp-mail-logging/assets to your readme.txt
wp-mail-logging/wp-mail-logging.php Passed 13 tests
"WP Mail Logging" version 1.12.0's primary PHP file adds more information about the plugin and serves as the entry point for WordPress
34 characters long description:
Logs each email sent by WordPress.
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
Everything looks great! No dangerous files found in this plugin9,800 lines of code in 111 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 77 | 2,128 | 4,667 | 7,111 |
CSS | 10 | 22 | 17 | 1,847 |
JavaScript | 10 | 135 | 164 | 468 |
PO File | 2 | 169 | 211 | 362 |
SVG | 12 | 0 | 0 | 12 |
PHP code Passed 2 tests
A brief analysis of cyclomatic complexity and code structure for this plugin
No complexity issues detected
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.35 |
Average class complexity | 13.30 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 87.00 |
Average method complexity | 2.61 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 26.00 |
Code structure | ||
---|---|---|
Namespaces | 15 | |
Interfaces | 8 | |
Traits | 0 | |
Classes | 62 | |
▷ Abstract classes | 5 | 8.06% |
▷ Concrete classes | 57 | 91.94% |
▷ Final classes | 0 | 0.00% |
Methods | 550 | |
▷ Static methods | 60 | 10.91% |
▷ Public methods | 414 | 75.27% |
▷ Protected methods | 55 | 10.00% |
▷ Private methods | 81 | 14.73% |
Functions | 27 | |
▷ Named functions | 4 | 14.81% |
▷ Anonymous functions | 23 | 85.19% |
Constants | 80 | |
▷ Global constants | 3 | 3.75% |
▷ Class constants | 77 | 96.25% |
▷ Public constants | 77 | 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
15 compressed PNG files occupy 0.49MB
Potential savings
Compression of 5 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
assets/images/smtp/screenshot-full.png | 71.38KB | 72.60KB | 0.00% |
assets/images/smtp/wpmailsmtp-logo@2x.png | 13.65KB | 8.91KB | ▼ 34.72% |
assets/images/prod-edu/reports.png | 73.50KB | 75.92KB | 0.00% |
assets/images/plane-bg@2x.png | 3.49KB | 3.49KB | 0.00% |
assets/images/prod-edu/archive.png | 120.74KB | 126.80KB | 0.00% |