Benchmarks
Plugin footprint Passed 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
This plugin's installer ran successfully
Server metrics [RAM: ▲0.02MB] [CPU: ▼173.49ms] Passed 4 tests
Analyzing server-side resources used by Ninja Mail
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 2.86 ▲0.02 | 32.40 ▼1.87 |
| Dashboard /wp-admin | 3.08 ▲0.03 | 44.72 ▼1.99 |
| Posts /wp-admin/edit.php | 3.13 ▲0.03 | 42.46 ▼1.46 |
| Add New Post /wp-admin/post-new.php | 5.44 ▲0.01 | 89.01 ▼688.63 |
| Media Library /wp-admin/upload.php | 3.03 ▲0.02 | 33.79 ▲0.29 |
| Ninja Mail /wp-admin/admin.php?page=ninja-mail | 3.04 | 27.98 |
Server storage [IO: ▲0.03MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
The plugin installed successfully
Filesystem: 17 new files
Database: no new tables, no new options
Browser metrics Passed 4 tests
This is an overview of browser requirements for Ninja Mail
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 3,691 ▲95 | 15.88 ▼0.19 | 10.22 ▼0.72 | 47.82 ▼0.76 |
| Dashboard /wp-admin | 2,980 ▲46 | 5.91 ▼0.08 | 133.35 ▼13.12 | 101.63 ▼9.54 |
| Posts /wp-admin/edit.php | 2,752 ▲13 | 2.85 ▲0.13 | 67.45 ▲6.10 | 85.85 ▼2.84 |
| Add New Post /wp-admin/post-new.php | 1,624 ▲126 | 21.76 ▲2.89 | 272.18 ▼104.28 | 102.03 ▼5.94 |
| Media Library /wp-admin/upload.php | 1,820 ▲10 | 5.03 ▼0.01 | 161.36 ▲10.61 | 123.93 ▲9.66 |
| Ninja Mail /wp-admin/admin.php?page=ninja-mail | 1,113 | 2.09 | 59.60 | 72.49 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] Passed 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
Uninstall script ran successfully
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the server (in the Apache logs)
Everything seems fine, however this is by no means 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
Almost there! Just fix the following items
- 1× PHP files perform the action of outputting non-empty strings when accessed directly:
- > /wp-content/plugins/ninja-mail/includes/resources/views/admin-mail-log.html.php
- 12× GET requests to PHP files have triggered server-side errors or warnings (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/ninja-mail/ninja-mail.php:25
- > PHP Fatal error
Uncaught Error: Call to undefined function __() in wp-content/plugins/ninja-mail/includes/resources/views/admin-settings.html.php:16
- > PHP Fatal error
Uncaught Error: Class 'NinjaMail\\WordPress\\Plugin' not found in wp-content/plugins/ninja-mail/includes/plugin.php:8
- > PHP Fatal error
Uncaught Error: Call to undefined function add_filter() in wp-content/plugins/ninja-mail/includes/tests.php:3
- > PHP Fatal error
Uncaught Error: Call to undefined function plugin_dir_path() in wp-content/plugins/ninja-mail/bootstrap.php:6
- > PHP Fatal error
Uncaught Error: Call to undefined function __() in wp-content/plugins/ninja-mail/includes/resources/views/admin-menu.html.php:3
- > PHP Notice
Undefined variable: logs in wp-content/plugins/ninja-mail/includes/resources/views/admin-mail-log.html.php on line 46
- > PHP Notice
Undefined variable: enabled in wp-content/plugins/ninja-mail/includes/resources/views/admin-mail-log.html.php on line 25
- > PHP Warning
Invalid argument supplied for foreach() in wp-content/plugins/ninja-mail/includes/resources/views/admin-mail-log.html.php on line 46
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/ninja-mail/includes/admin.php:6
- > 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)
Everything seems fine on the user side
Optimizations
Plugin configuration Passed 29 tests
readme.txt Passed 16 tests
Often overlooked, readme.txt is one of the most important files in your plugin
3 plugin tags: forms, transactional, email
ninja-mail/ninja-mail.php Passed 13 tests
The main PHP file in "Ninja Mail" ver. 1.0.6 adds more information about the plugin and also serves as the entry point for this plugin
46 characters long description:
A transactional email service for Ninja Forms.
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
There were no executable files found in this plugin625 lines of code in 16 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 14 | 133 | 95 | 611 |
| Markdown | 2 | 9 | 0 | 14 |
PHP code Passed 2 tests
Analyzing cyclomatic complexity and code structure
Everything seems fine, there were no complexity issues found
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.24 |
| Average class complexity | 4.50 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 7.00 |
| Average method complexity | 1.66 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 6.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 2 | |
| Interfaces | 1 | |
| Traits | 0 | |
| Classes | 5 | |
| ▷ Abstract classes | 1 | 20.00% |
| ▷ Concrete classes | 4 | 80.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 35 | |
| ▷ Static methods | 13 | 37.14% |
| ▷ Public methods | 28 | 80.00% |
| ▷ Protected methods | 4 | 11.43% |
| ▷ Private methods | 3 | 8.57% |
| Functions | 20 | |
| ▷ Named functions | 4 | 20.00% |
| ▷ Anonymous functions | 16 | 80.00% |
| Constants | 3 | |
| ▷ Global constants | 1 | 33.33% |
| ▷ Class constants | 2 | 66.67% |
| ▷ Public constants | 2 | 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
There were not PNG files found in your plugin