Benchmarks
Plugin footprint Passed 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | All plugins must install correctly, without throwing any errors, warnings, or notices
Installer ran successfully
Server metrics [RAM: ▲0.16MB] [CPU: ▼136.64ms] Passed 4 tests
This is a short check of server-side resources used by Post Date Time Change
No issues were detected with server-side resource usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 2.98 ▲0.15 | 38.85 ▲4.70 |
Dashboard /wp-admin | 3.20 ▲0.15 | 54.06 ▲10.28 |
Posts /wp-admin/edit.php | 3.32 ▲0.22 | 50.73 ▲10.56 |
Add New Post /wp-admin/post-new.php | 5.56 ▲0.13 | 87.86 ▼561.48 |
Media Library /wp-admin/upload.php | 3.25 ▲0.25 | 32.46 ▼0.07 |
Post Date Time Change /wp-admin/options-general.php?page=postdatetimechange | 3.12 | 27.99 |
Server storage [IO: ▲0.12MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
There were no storage issued detected upon installing this plugin
Filesystem: 13 new files
Database: no new tables, 1 new option
New WordPress options |
---|
postdatetimechange |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Post Date Time Change
Minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 3,717 ▲121 | 16.00 ▲0.54 | 7.50 ▼3.72 | 46.85 ▼3.64 |
Dashboard /wp-admin | 3,005 ▲74 | 5.91 ▼0.24 | 137.57 ▼4.88 | 109.57 ▼2.68 |
Posts /wp-admin/edit.php | 3,830 ▲1,091 | 3.60 ▲0.90 | 88.74 ▲22.56 | 86.65 ▼2.89 |
Add New Post /wp-admin/post-new.php | 1,675 ▼8 | 19.06 ▲0.31 | 372.69 ▼5.01 | 108.12 ▲2.46 |
Media Library /wp-admin/upload.php | 1,927 ▲117 | 5.46 ▲0.43 | 131.77 ▼19.47 | 121.97 ▼1.33 |
Post Date Time Change /wp-admin/options-general.php?page=postdatetimechange | 1,474 | 2.54 | 65.88 | 49.80 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] Passed 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
Uninstall script ran successfully
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
Good news, no errors were detected
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
Please take a closer look at the following
- 3× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function untrailingslashit() in wp-content/plugins/post-date-time-change/lib/class-postdatetimechange.php:59
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/post-date-time-change/lib/class-postdatetimechangeregist.php:37
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/post-date-time-change/lib/class-postdatetimechangeregist.php:37
- > 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)
No browser issues were found
Optimizations
Plugin configuration 96% from 29 tests
readme.txt Passed 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
7 plugin tags: edit, media, post, date, page...
post-date-time-change/postdatetimechange.php 92% from 13 tests
The main PHP script in "Post Date Time Change" version 5.08 is automatically included on every request by WordPress
Please make the necessary changes and fix the following:
- Main file name: The principal plugin file should be the same as the plugin slug ("post-date-time-change.php" instead of "postdatetimechange.php")
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
Good job! No executable or dangerous file extensions detected2,433 lines of code in 12 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
JavaScript | 5 | 192 | 106 | 1,307 |
PHP | 4 | 129 | 229 | 739 |
CSS | 3 | 25 | 2 | 387 |
PHP code Passed 2 tests
Analyzing cyclomatic complexity and code structure
No complexity issues detected
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.35 |
Average class complexity | 48.00 |
▷ Minimum class complexity | 10.00 |
▷ Maximum class complexity | 86.00 |
Average method complexity | 5.09 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 10.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 2 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 2 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 23 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 17 | 73.91% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 6 | 26.09% |
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
Often times overlooked, PNG files can occupy unnecessary space in your plugin
There were not PNG files found in your plugin