Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
This plugin's installer ran successfully
Server metrics [RAM: ▲0.17MB] [CPU: ▼8.62ms] Passed 4 tests
Analyzing server-side resources used by Primail
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.63 ▲0.17 | 40.19 ▼2.92 |
Dashboard /wp-admin | 3.49 ▲0.14 | 53.50 ▼15.78 |
Posts /wp-admin/edit.php | 3.60 ▲0.24 | 50.79 ▼1.12 |
Add New Post /wp-admin/post-new.php | 6.07 ▲0.18 | 88.06 ▼14.65 |
Media Library /wp-admin/upload.php | 3.41 ▲0.18 | 40.95 ▲3.10 |
Primail /wp-admin/options-general.php?page=primail-settings | 3.38 | 33.78 |
Server storage [IO: ▲0.04MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
This plugin was installed successfully
Filesystem: 8 new files
Database: no new tables, 11 new options
New WordPress options |
---|
primail_default_from_email |
can_compress_scripts |
primail_api_debug_enabled |
primail_default_from_name |
widget_recent-posts |
theysaidso_admin_options |
primail_api_test_key |
widget_theysaidso_widget |
db_upgraded |
widget_recent-comments |
... |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Primail
This plugin has a minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,804 ▲43 | 14.18 ▼0.17 | 1.82 ▲0.12 | 44.76 ▼0.77 |
Dashboard /wp-admin | 2,210 ▲30 | 5.64 ▼0.04 | 86.83 ▼5.06 | 39.80 ▼3.42 |
Posts /wp-admin/edit.php | 2,118 ▲21 | 2.04 ▲0.10 | 38.89 ▲2.84 | 39.46 ▲0.51 |
Add New Post /wp-admin/post-new.php | 1,535 ▲7 | 23.61 ▲0.28 | 642.19 ▼2.49 | 52.08 ▼8.70 |
Media Library /wp-admin/upload.php | 1,415 ▲15 | 4.17 ▲0.02 | 103.17 ▼1.18 | 43.74 ▼4.36 |
Primail /wp-admin/options-general.php?page=primail-settings | 970 | 2.16 | 23.22 | 28.09 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
It is recommended to fix the following
- This plugin does not fully uninstall, leaving 11 options in the database
- db_upgraded
- can_compress_scripts
- widget_theysaidso_widget
- primail_default_from_email
- widget_recent-comments
- theysaidso_admin_options
- widget_recent-posts
- primail_default_from_name
- primail_api_test_key
- primail_api_key
- ...
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a short smoke test looking for server-side errors
Even though no errors were found, this is by no means an exhaustive test
SRP 50% 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
Please take a closer look at the following
- 3× PHP files trigger server errors when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function Primail_Options\\add_filter() in wp-content/plugins/primail/core/options.php:5
- > PHP Fatal error
Uncaught Error: Call to undefined function Primail_Settings\\add_action() in wp-content/plugins/primail/core/settings.php:5
- > PHP Fatal error
Uncaught Error: Call to undefined function plugin_dir_path() in wp-content/plugins/primail/primail.php:17
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
There were no browser issues found
Optimizations
Plugin configuration 93% 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
Attributes that require attention:
- Contributors: Plugin contributors not specified
primail/primail.php 92% from 13 tests
The main PHP file in "Primail" ver. 1.0.1 adds more information about the plugin and also serves as the entry point for this plugin
You should first fix the following items:
- Requires at least: Required version must match the one declared in readme.txt ("5.6" instead of "5.5.1")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is an overview of programming languages used in this plugin; dangerous file extensions are not allowed
There were no executable files found in this plugin858 lines of code in 6 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 5 | 169 | 257 | 821 |
CSS | 1 | 8 | 0 | 37 |
PHP code Passed 2 tests
Cyclomatic complexity and code structure are the fingerprint of this plugin
Everything seems fine, there were no complexity issues found
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.25 |
Average class complexity | 40.00 |
▷ Minimum class complexity | 40.00 |
▷ Maximum class complexity | 40.00 |
Average method complexity | 4.00 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 10.00 |
Code structure | ||
---|---|---|
Namespaces | 3 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 1 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 1 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 13 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 4 | 30.77% |
▷ Protected methods | 1 | 7.69% |
▷ Private methods | 8 | 61.54% |
Functions | 32 | |
▷ Named functions | 31 | 96.88% |
▷ Anonymous functions | 1 | 3.12% |
Constants | 2 | |
▷ Global constants | 2 | 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
PNG images were not found in this plugin