Benchmarks
Plugin footprint 82% 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 gracefully, with no errors
Server metrics [RAM: ▲0.09MB] [CPU: ▼7.99ms] Passed 4 tests
Analyzing server-side resources used by Secure Messaging
This plugin has minimal impact on server resources
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.57 ▲0.11 | 35.63 ▼6.93 |
| Dashboard /wp-admin | 3.41 ▲0.06 | 44.68 ▼14.49 |
| Posts /wp-admin/edit.php | 3.52 ▲0.16 | 43.17 ▼2.91 |
| Add New Post /wp-admin/post-new.php | 5.99 ▲0.10 | 80.87 ▼7.63 |
| Media Library /wp-admin/upload.php | 3.33 ▲0.10 | 37.39 ▲6.56 |
Server storage [IO: ▲2.36MB] [DB: ▲0.00MB] 67% from 3 tests
Input-output and database impact of this plugin
It is recommended to fix the following issues
- You have illegally modified 4 files (7.56KB) outside of "wp-content/plugins/secure-messaging/" and "wp-content/uploads/"
- (new file) wp-content/.gpg/pubring.kbx~
- (new file) wp-content/.gpg/private-keys-v1.d/.empty
- (new file) wp-content/.gpg/random_seed
- (new file) wp-content/.gpg/pubring.kbx
Filesystem: 193 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_theysaidso_widget |
| theysaidso_admin_options |
| db_upgraded |
| widget_recent-posts |
| widget_recent-comments |
| can_compress_scripts |
Browser metrics Passed 4 tests
A check of browser resources used by Secure Messaging
This plugin renders optimally with no browser resource issues detected
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,800 ▲29 | 13.26 ▼1.12 | 1.77 ▼0.58 | 44.26 ▼0.31 |
| Dashboard /wp-admin | 2,209 ▲21 | 5.84 ▲0.94 | 97.33 ▼19.70 | 38.05 ▼8.77 |
| Posts /wp-admin/edit.php | 2,089 ▼0 | 2.06 ▲0.05 | 36.55 ▼0.63 | 33.00 ▼4.13 |
| Add New Post /wp-admin/post-new.php | 1,533 ▲19 | 23.38 ▲5.95 | 682.48 ▼20.00 | 57.43 ▲4.97 |
| Media Library /wp-admin/upload.php | 1,388 ▲9 | 4.24 ▲0.10 | 111.06 ▲6.07 | 47.24 ▼0.07 |
Uninstaller [IO: ▲0.01MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
Please fix the following items
- The uninstall procedure has failed, leaving 6 options in the database
- db_upgraded
- widget_theysaidso_widget
- widget_recent-posts
- can_compress_scripts
- widget_recent-comments
- theysaidso_admin_options
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)
Even though no errors were found, this is by no means an exhaustive test
SRP 0% 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
Almost there! Just fix the following items
- 3× PHP files perform the task of outputting text when accessed with GET requests:
- > /wp-content/plugins/secure-messaging/vendor/pear/console_commandline/tests/AllTests.php
- > /wp-content/plugins/secure-messaging/vendor/pear/crypt_gpg/tools/build-keyring.php
- > /wp-content/plugins/secure-messaging/vendor/pear/crypt_gpg/tools/dump-keyring.php
- 146× GET requests to PHP files have triggered server-side errors or warnings (only 10 are shown):
- > PHP Warning
require_once(Console/CommandLine/Action.php): failed to open stream: No such file or directory in wp-content/plugins/secure-messaging/vendor/pear/console_commandline/Console/CommandLine/Action/List.php on line 28
- > PHP Warning
require_once(Crypt/GPG.php): failed to open stream: No such file or directory in wp-content/plugins/secure-messaging/vendor/pear/crypt_gpg/tests/TestCase.php on line 40
- > PHP Fatal error
require_once(): Failed opening required 'Console/CommandLine.php' (include_path='.:/usr/share/php') in wp-content/plugins/secure-messaging/vendor/pear/console_commandline/docs/examples/ex3.php on line 27
- > PHP Warning
file_get_contents(/encrypted-data-missing-key.asc): failed to open stream: No such file or directory in wp-content/plugins/secure-messaging/vendor/pear/crypt_gpg/tools/build-keyring.php on line 101
- > PHP Warning
require_once(Crypt/GPGAbstract.php): failed to open stream: No such file or directory in wp-content/plugins/secure-messaging/vendor/pear/crypt_gpg/Crypt/GPG.php on line 60
- > PHP Fatal error
require_once(): Failed opening required 'Console/CommandLine.php' (include_path='.:/usr/share/php') in wp-content/plugins/secure-messaging/vendor/pear/console_commandline/docs/examples/ex4.php on line 28
- > PHP Fatal error
require_once(): Failed opening required 'Crypt/GPG.php' (include_path='.:/usr/share/php') in wp-content/plugins/secure-messaging/vendor/pear/crypt_gpg/tests/TestCase.php on line 40
- > PHP Warning
require_once(Console/CommandLine.php): failed to open stream: No such file or directory in wp-content/plugins/secure-messaging/vendor/pear/console_commandline/docs/examples/ex1.php on line 29
- > PHP Warning
require_once(Console/CommandLine/Action.php): failed to open stream: No such file or directory in wp-content/plugins/secure-messaging/vendor/pear/console_commandline/Console/CommandLine/Action/StoreTrue.php on line 28
- > PHP Fatal error
require_once(): Failed opening required 'Crypt/GPG.php' (include_path='.:/usr/share/php') in wp-content/plugins/secure-messaging/vendor/pear/crypt_gpg/tests/TestCase.php on line 40
- > PHP Warning
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
No browser issues were found
Optimizations
Plugin configuration 96% from 29 tests
readme.txt Passed 16 tests
Perhaps the most important file in your plugin readme.txt gets parsed in order to generate the public listing of your plugin
3 plugin tags: pgp, gpg, security
secure-messaging/secure-messaging.php 92% from 13 tests
The main PHP script in "Secure Messaging" version 0.4.1 is automatically included on every request by WordPress
You should first fix the following items:
- Text Domain: If you choose to specify the text domain, it must be the same as the plugin slug; optional since WordPress version 4.6
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short glimpse at programming languages used with this plugin and a check that no dangerous files are present
No dangerous file extensions were detected16,729 lines of code in 162 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 140 | 3,710 | 11,597 | 14,738 |
| XML | 10 | 38 | 20 | 1,310 |
| JSON | 4 | 0 | 0 | 312 |
| Bourne Shell | 1 | 40 | 44 | 197 |
| Markdown | 2 | 17 | 0 | 55 |
| PO File | 1 | 6 | 6 | 43 |
| reStructuredText | 1 | 13 | 0 | 42 |
| YAML | 3 | 0 | 0 | 32 |
PHP code Passed 2 tests
Analyzing logical lines of code, cyclomatic complexity, and other code metrics
No cyclomatic complexity issues were detected for this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.21 |
| Average class complexity | 13.23 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 148.00 |
| Average method complexity | 2.54 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 62.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 2 | |
| Interfaces | 4 | |
| Traits | 0 | |
| Classes | 77 | |
| ▷ Abstract classes | 4 | 5.19% |
| ▷ Concrete classes | 73 | 94.81% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 652 | |
| ▷ Static methods | 24 | 3.68% |
| ▷ Public methods | 566 | 86.81% |
| ▷ Protected methods | 58 | 8.90% |
| ▷ Private methods | 28 | 4.29% |
| Functions | 17 | |
| ▷ Named functions | 15 | 88.24% |
| ▷ Anonymous functions | 2 | 11.76% |
| Constants | 63 | |
| ▷ Global constants | 6 | 9.52% |
| ▷ Class constants | 57 | 90.48% |
| ▷ Public constants | 57 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
PNG files should be compressed to save space and minimize bandwidth usage
There are no PNG files in this plugin