Benchmarks
Plugin footprint 65% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.09MB] [CPU: ▼9.67ms] Passed 4 tests
Server-side resources used by Wb Mail Logger
This plugin does not affect your website's performance
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.55 ▲0.09 | 37.27 ▼18.80 |
Dashboard /wp-admin | 3.39 ▲0.09 | 47.27 ▼11.56 |
Posts /wp-admin/edit.php | 3.51 ▲0.15 | 49.27 ▼2.66 |
Add New Post /wp-admin/post-new.php | 5.97 ▲0.09 | 99.02 ▼5.65 |
Media Library /wp-admin/upload.php | 3.31 ▲0.09 | 34.30 ▼0.76 |
Mail Log /wp-admin/tools.php?page=wb-mail-logger | 3.33 | 34.11 |
Server storage [IO: ▲0.12MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
This plugin was installed successfully
Filesystem: 19 new files
Database: 1 new table, 6 new options
New tables |
---|
wp_wb_mlr_data |
New WordPress options |
---|
widget_theysaidso_widget |
can_compress_scripts |
db_upgraded |
widget_recent-comments |
theysaidso_admin_options |
widget_recent-posts |
Browser metrics Passed 4 tests
A check of browser resources used by Wb Mail Logger
Normal browser usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,804 ▲58 | 13.56 ▼0.73 | 1.64 ▼0.62 | 38.71 ▼5.88 |
Dashboard /wp-admin | 2,210 ▲22 | 5.89 ▲0.03 | 105.66 ▼12.07 | 40.95 ▼2.03 |
Posts /wp-admin/edit.php | 2,093 ▲4 | 2.02 ▼0.03 | 40.00 ▲2.44 | 34.07 ▼1.10 |
Add New Post /wp-admin/post-new.php | 1,546 ▲12 | 18.24 ▼4.93 | 599.82 ▼45.97 | 49.42 ▼20.49 |
Media Library /wp-admin/upload.php | 1,395 ▲4 | 4.16 ▼0.03 | 96.88 ▼5.35 | 42.33 ▼0.85 |
Mail Log /wp-admin/tools.php?page=wb-mail-logger | 924 | 2.07 | 25.71 | 26.64 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 50% from 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
You still need to fix the following
- The plugin did not uninstall successfully, leaving 1 table in the database
- wp_wb_mlr_data
- Zombie WordPress options were found after uninstall: 6 options
- theysaidso_admin_options
- widget_recent-posts
- widget_recent-comments
- can_compress_scripts
- widget_theysaidso_widget
- db_upgraded
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
The smoke test was a success, however most plugin functionality was not tested
SRP 0% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle applies for WordPress plugins as well - please make sure your PHP files perform no actions when accessed directly
Almost there! Just fix the following items
- 1× PHP files perform the task of outputting text when accessed with GET requests:
- > /wp-content/plugins/wb-mail-logger/admin/partials/_detail-view.php
- 1× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Fatal error
Uncaught Error: Call to undefined function _e() in wp-content/plugins/wb-mail-logger/admin/partials/wb-mail-logger-admin-display.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 errors were detected
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file is important because it is parsed by WordPress.org for the public listing of your plugin
These attributes need your attention:
- Tags: Please delete some tags, you are using 15 tag instead of maximum 10
wb-mail-logger/wb-mail-logger.php 92% from 13 tests
The primary PHP file in "Wb Mail Logger" version 1.0.4 is used by WordPress to initiate all plugin functionality
It is important to fix the following:
- Description: The description should be shorter than 140 characters (currently 153 characters long)
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short check of programming languages and file extensions; no executable files are allowed
Everything looks great! No dangerous files found in this plugin682 lines of code in 13 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 11 | 149 | 454 | 590 |
JavaScript | 1 | 13 | 0 | 74 |
CSS | 1 | 0 | 0 | 18 |
PHP code Passed 2 tests
Analyzing cyclomatic complexity and code structure
This plugin has no cyclomatic complexity issues
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.26 |
Average class complexity | 8.83 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 42.00 |
Average method complexity | 2.21 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 7.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 6 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 6 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 39 | |
▷ Static methods | 4 | 10.26% |
▷ Public methods | 28 | 71.79% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 11 | 28.21% |
Functions | 3 | |
▷ Named functions | 3 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 6 | |
▷ Global constants | 6 | 100.00% |
▷ Class constants | 0 | 0.00% |
▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
No PNG files were detected