Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.12MB] [CPU: ▼3.63ms] Passed 4 tests
A check of server-side resources used by Pending Draft Alert
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.58 ▲0.11 | 41.25 ▼4.65 |
| Dashboard /wp-admin | 3.51 ▲0.16 | 53.30 ▼14.69 |
| Posts /wp-admin/edit.php | 3.56 ▲0.20 | 56.49 ▲7.33 |
| Add New Post /wp-admin/post-new.php | 6.00 ▲0.11 | 94.56 ▲3.16 |
| Media Library /wp-admin/upload.php | 3.34 ▲0.11 | 39.98 ▲1.65 |
| Pending Draft Alert /wp-admin/options-general.php?page=wppda_settings | 3.34 | 40.12 |
Server storage [IO: ▲0.04MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
No storage issues were detected
Filesystem: 7 new files
Database: no new tables, 7 new options
| New WordPress options |
|---|
| can_compress_scripts |
| widget_theysaidso_widget |
| widget_recent-comments |
| db_upgraded |
| wppda_setting_basic |
| theysaidso_admin_options |
| widget_recent-posts |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Pending Draft Alert
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,945 ▲199 | 14.54 ▲0.17 | 1.80 ▼0.04 | 40.26 ▼9.01 |
| Dashboard /wp-admin | 2,354 ▲174 | 6.32 ▲0.62 | 122.27 ▲18.66 | 38.41 ▼4.14 |
| Posts /wp-admin/edit.php | 2,276 ▲176 | 3.54 ▲1.52 | 54.71 ▲16.54 | 33.62 ▼14.64 |
| Add New Post /wp-admin/post-new.php | 1,548 ▲4 | 23.46 ▲0.47 | 647.66 ▼29.21 | 37.13 ▼34.01 |
| Media Library /wp-admin/upload.php | 1,422 ▲22 | 4.37 ▲0.19 | 82.69 ▼32.38 | 43.16 ▼3.23 |
| Pending Draft Alert /wp-admin/options-general.php?page=wppda_settings | 1,054 | 3.48 | 50.95 | 28.03 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
These items require your attention
- This plugin does not fully uninstall, leaving 7 options in the database
- widget_recent-comments
- widget_recent-posts
- db_upgraded
- widget_theysaidso_widget
- wppda_setting_basic
- theysaidso_admin_options
- can_compress_scripts
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
Good news, no errors were detected
SRP 50% 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
- 1× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Fatal error
Uncaught Error: Using $this when not in object context in wp-content/plugins/pending-draft-alert/email/email-view.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, but this is not an exhaustive test
Optimizations
Plugin configuration 93% 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
5 plugin tags: reminder, drafts, drafts post, email reminder, email
pending-draft-alert/wp-pending-draft-alert.php 85% from 13 tests
The main PHP file in "Pending Draft Alert" ver. 1.0 adds more information about the plugin and also serves as the entry point for this plugin
You should first fix the following items:
- Text Domain: The text domain follows the same naming rules as the plugin slug: lowercase characters and dashes
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("pending-draft-alert.php" instead of "wp-pending-draft-alert.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short review of files and their extensions; it is not recommended to include executable files
Everything looks great! No dangerous files found in this plugin623 lines of code in 6 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 6 | 168 | 264 | 623 |
PHP code Passed 2 tests
An overview of cyclomatic complexity and code structure
No complexity issues detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.34 |
| Average class complexity | 21.00 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 61.00 |
| Average method complexity | 2.16 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 7.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 3 | |
| ▷ Abstract classes | 1 | 33.33% |
| ▷ Concrete classes | 2 | 66.67% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 38 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 36 | 94.74% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 2 | 5.26% |
| Functions | 7 | |
| ▷ Named functions | 6 | 85.71% |
| ▷ Anonymous functions | 1 | 14.29% |
| 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
PNG files should be compressed to save space and minimize bandwidth usage
There are no PNG files in this plugin