Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.09MB] [CPU: ▼9.85ms] Passed 4 tests
A check of server-side resources used by Posts Auto Expire Control
This plugin does not affect your website's performance
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.56 ▲0.09 | 39.20 ▲2.72 |
Dashboard /wp-admin | 3.40 ▲0.06 | 49.87 ▼15.56 |
Posts /wp-admin/edit.php | 3.52 ▲0.16 | 49.65 ▲4.23 |
Add New Post /wp-admin/post-new.php | 5.98 ▲0.10 | 88.82 ▼30.80 |
Media Library /wp-admin/upload.php | 3.33 ▲0.10 | 41.16 ▲6.02 |
Posts Auto Expire Control /wp-admin/options-general.php?page=apext_setting | 3.34 | 33.84 |
Server storage [IO: ▲0.24MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
This plugin was installed successfully
Filesystem: 14 new files
Database: no new tables, 9 new options
New WordPress options |
---|
theysaidso_admin_options |
apextmail |
widget_theysaidso_widget |
apext |
db_upgraded |
apext_ver |
widget_recent-posts |
widget_recent-comments |
can_compress_scripts |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Posts Auto Expire Control
Minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,793 ▲22 | 14.34 ▼0.29 | 1.57 ▼0.25 | 41.39 ▼2.26 |
Dashboard /wp-admin | 2,196 ▲16 | 5.61 ▼0.04 | 85.17 ▼6.61 | 41.01 ▼2.43 |
Posts /wp-admin/edit.php | 2,107 ▲10 | 2.00 ▲0.02 | 34.53 ▼2.13 | 33.24 ▼3.94 |
Add New Post /wp-admin/post-new.php | 1,533 ▲7 | 23.17 ▼0.41 | 682.11 ▼1.69 | 53.90 ▼5.79 |
Media Library /wp-admin/upload.php | 1,398 ▼2 | 4.30 ▲0.10 | 96.31 ▼11.02 | 43.41 ▼4.48 |
Posts Auto Expire Control /wp-admin/options-general.php?page=apext_setting | 1,117 | 2.18 | 27.42 | 39.70 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
It is recommended to fix the following
- Zombie WordPress options detected upon uninstall: 9 options
- widget_theysaidso_widget
- theysaidso_admin_options
- widget_recent-comments
- apext_ver
- apextmail
- db_upgraded
- widget_recent-posts
- can_compress_scripts
- apext
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
The smoke test was a success, however most plugin functionality was not tested
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
- 10× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Fatal error
Uncaught Error: Call to undefined function get_post_types() in wp-content/plugins/post-auto-expire-control/html/render_output.php:3
- > PHP Notice
Undefined index: day in wp-content/plugins/post-auto-expire-control/html/add_rule_ajax.php on line 5
- > PHP Notice
Undefined index: counter in wp-content/plugins/post-auto-expire-control/html/add_rule_ajax.php on line 6
- > PHP Fatal error
Uncaught Error: Call to undefined function get_post_types() in wp-content/plugins/post-auto-expire-control/html/add_rule_ajax.php:8
- > PHP Notice
Undefined index: status in wp-content/plugins/post-auto-expire-control/html/add_rule_ajax.php on line 4
- > PHP Fatal error
Uncaught Error: Call to undefined function get_post_types() in wp-content/plugins/post-auto-expire-control/html/add_rule_form.php:3
- > PHP Fatal error
Uncaught Error: Call to undefined function get_option() in wp-content/plugins/post-auto-expire-control/html/mailsetting.php:2
- > PHP Notice
Undefined index: cpt in wp-content/plugins/post-auto-expire-control/html/add_rule_ajax.php on line 3
- > PHP Fatal error
Uncaught Error: Call to undefined function register_activation_hook() in wp-content/plugins/post-auto-expire-control/post-auto-expire-control.php:457
- > PHP Notice
Undefined index: role in wp-content/plugins/post-auto-expire-control/html/add_rule_ajax.php on line 2
- > PHP Fatal error
User-side errors 0% from 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the browser (console and network errors and warnings)
Please take a look at the following user-side issues
- > GET request to /wp-admin/options-general.php?page=apext_setting
- > Console-api (warning) in unknown
/wp-admin/load-scripts.php?c=0&load%5Bchunk_0%5D=jquery-core,jquery-migrate,utils&ver=6.3.1 1:28609 "jQuery.Deferred exception: $(...).live is not a function" "TypeError: $(...).live is not a function\n at HTMLDocument.\u003Canonymous> (/wp-content/plugins/post-auto-expire-control/js/jscontrol.js?ver=1.0:22:18)\n at e (/wp-admin/load-scripts.php?c=0&load%5Bchunk_0%5D=jquery-core,jquery-migrate,utils&ver=6.3.1:2:26990)\n at t (/wp-admin/load-scripts.php?c=0&load%5Bchunk_0%5D=jquery-core,jquery-migrate,utils&ver=6.3.1:2:27292)" undefined
- > GET request to /wp-admin/options-general.php?page=apext_setting
- > Javascript (severe) in unknown
/wp-admin/load-scripts.php?c=0&load%5Bchunk_0%5D=jquery-core,jquery-migrate,utils&ver=6.3.1 1:28721 Uncaught TypeError: $(...).live is not a function
Optimizations
Plugin configuration 97% from 29 tests
readme.txt 94% from 16 tests
It's important to format your readme.txt file correctly as it is parsed for the public listing of your plugin
These attributes need to be fixed:
- Screenshots: These screenshots have no corresponding images in /assets: #1 (Post expiration rules table), #2 (Auto post expiration email notification control panel)
post-auto-expire-control/post-auto-expire-control.php Passed 13 tests
The primary PHP file in "Posts Auto Expire Control" version 0.1.3 is used by WordPress to initiate all plugin functionality
94 characters long description:
this plugin helps you to set your author post expiration based on the user role and post type.
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are considered dangerous and should not be included with any WordPress plugin
Everything looks great! No dangerous files found in this plugin746 lines of code in 9 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 5 | 139 | 42 | 540 |
PO File | 1 | 45 | 71 | 101 |
JavaScript | 1 | 28 | 5 | 91 |
CSS | 2 | 0 | 0 | 14 |
PHP code Passed 2 tests
Analyzing cyclomatic complexity and code structure
This plugin has no cyclomatic complexity problems
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.24 |
Average class complexity | 44.00 |
▷ Minimum class complexity | 44.00 |
▷ Maximum class complexity | 44.00 |
Average method complexity | 2.39 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 7.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 1 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 1 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 31 | |
▷ Static methods | 2 | 6.45% |
▷ Public methods | 31 | 100.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 0 | |
▷ Named functions | 0 | 0.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 1 | |
▷ Global constants | 0 | 0.00% |
▷ Class constants | 1 | 100.00% |
▷ Public constants | 1 | 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