Benchmarks
Plugin footprint 40% from 16 tests
Installer 0% from 1 test
🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices
The following installer errors require your attention
- Install procedure had errors
- > Deprecated in wp-content/plugins/plainmail/PlainmailInstall.php+3
Methods with the same name as their class will not be constructors in a future version of PHP; PlainmailInstall has a deprecated constructor
Server metrics [RAM: ▼1.84MB] [CPU: ▼51.19ms] Passed 4 tests
Analyzing server-side resources used by Wordpress Plain Mail
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 2.16 ▼1.30 | 5.68 ▼30.86 |
Dashboard /wp-admin | 2.18 ▼1.17 | 6.33 ▼54.11 |
Posts /wp-admin/edit.php | 2.18 ▼1.18 | 5.98 ▼38.57 |
Add New Post /wp-admin/post-new.php | 2.18 ▼3.71 | 6.16 ▼81.22 |
Media Library /wp-admin/upload.php | 2.18 ▼1.05 | 6.22 ▼29.79 |
Plainmail /wp-admin/options-general.php?page=plainmail | 2.18 | 6.07 |
Server storage [IO: ▲0.02MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
There were no storage issued detected upon installing this plugin
Filesystem: 8 new files
Database: 2 new tables, 7 new options
New tables |
---|
wp_plainmail_headers |
wp_plainmail_recipients |
New WordPress options |
---|
widget_recent-posts |
PLAINMAIL_INSTALLED |
widget_theysaidso_widget |
db_upgraded |
widget_recent-comments |
theysaidso_admin_options |
can_compress_scripts |
Browser metrics Passed 4 tests
Wordpress Plain Mail: an overview of browser usage
This plugin has a minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,799 ▲49 | 14.35 ▼0.00 | 1.90 ▲0.18 | 43.01 ▼3.37 |
Dashboard /wp-admin | 2,204 ▲24 | 5.63 ▲0.00 | 82.62 ▼9.00 | 38.79 ▼7.00 |
Posts /wp-admin/edit.php | 2,103 ▲3 | 2.01 ▲0.01 | 33.42 ▼5.12 | 34.12 ▲1.22 |
Add New Post /wp-admin/post-new.php | 1,541 ▲15 | 24.29 ▲0.56 | 650.47 ▼57.60 | 67.58 ▲14.74 |
Media Library /wp-admin/upload.php | 1,406 ▲6 | 4.17 ▼0.00 | 105.20 ▲2.30 | 45.82 ▲0.97 |
Plainmail /wp-admin/options-general.php?page=plainmail | 796 | 2.03 | 26.53 | 34.01 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 50% from 4 tests
🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
It is recommended to fix the following
- Uninstall procedure validation failed for this plugin
- > User notice in wp-includes/functions.php+5905
Function wp_register_style was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the css_plainmail handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- The uninstall procedure has failed, leaving 6 options in the database
- db_upgraded
- widget_recent-posts
- widget_recent-comments
- can_compress_scripts
- widget_theysaidso_widget
- theysaidso_admin_options
Smoke tests 50% from 4 tests
Server-side errors 0% from 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
Smoke test failed, please fix the following
- > GET request to /wp-admin/options-general.php?page=plainmail
- > User notice in wp-includes/functions.php+5905
Function wp_register_style was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the css_plainmail handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- > GET request to /wp-admin/options-general.php?page=plainmail
- > User notice in wp-includes/functions.php+5905
Function wp_enqueue_style was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the css_plainmail handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- > GET request to /wp-admin/options-general.php?page=plainmail
- > User deprecated in wp-includes/functions.php+5463
Function screen_icon is deprecated since version 3.8.0 with no alternative available.
- > GET request to /wp-admin/options-general.php?page=plainmail
- > User deprecated in wp-includes/functions.php+5463
Function get_screen_icon is deprecated since version 3.8.0 with no alternative available.
SRP 50% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle: PHP files have to remain inert when accessed directly, throwing no errors and performing no actions
Almost there! Just fix the following items
- 3× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Warning
require_once(ABSPATHwp-includes/pluggable.php): failed to open stream: No such file or directory in wp-content/plugins/plainmail/plainmail.php on line 14
- > PHP Warning
Use of undefined constant ABSPATH - assumed 'ABSPATH' (this will throw an Error in a future version of PHP) in wp-content/plugins/plainmail/plainmail.php on line 14
- > PHP Fatal error
require_once(): Failed opening required 'ABSPATHwp-includes/pluggable.php' (include_path='.:/usr/share/php') in wp-content/plugins/plainmail/plainmail.php on line 14
- > PHP Warning
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, but this is not an exhaustive test
Optimizations
Plugin configuration Passed 29 tests
readme.txt Passed 16 tests
Don't ignore readme.txt as it is the file that instructs WordPress.org on how to present your plugin to the world
1 plugin tags: email
plainmail/plainmail.php Passed 13 tests
The main file in "Wordpress Plain Mail" v. 1.2 serves as a complement to information provided in readme.txt and as the entry point to the plugin
34 characters long description:
Plaintext email form for Wordpress
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | An overview of files in this plugin; executable files are not allowed
No dangerous file extensions were detected582 lines of code in 7 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 6 | 202 | 63 | 560 |
CSS | 1 | 5 | 0 | 22 |
PHP code Passed 2 tests
A short review of cyclomatic complexity and code structure
There were no cyclomatic complexity issued detected
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.45 |
Average class complexity | 14.00 |
▷ Minimum class complexity | 3.00 |
▷ Maximum class complexity | 41.00 |
Average method complexity | 4.00 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 19.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 | 26 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 25 | 96.15% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 1 | 3.85% |
Functions | 0 | |
▷ Named functions | 0 | 0.00% |
▷ Anonymous functions | 0 | 0.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
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
There were not PNG files found in your plugin