Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | All plugins must install correctly, without throwing any errors, warnings, or notices
Install script ran successfully
Server metrics [RAM: ▲0.04MB] [CPU: ▼4.90ms] Passed 4 tests
Server-side resources used by JKL Timezone Converter
Normal server usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.51 ▲0.04 | 35.78 ▼6.27 |
Dashboard /wp-admin | 3.34 ▲0.04 | 44.49 ▼3.67 |
Posts /wp-admin/edit.php | 3.45 ▲0.10 | 49.63 ▲1.95 |
Add New Post /wp-admin/post-new.php | 5.92 ▲0.04 | 89.96 ▼11.11 |
Media Library /wp-admin/upload.php | 3.26 ▲0.04 | 37.00 ▲1.45 |
Server storage [IO: ▲0.07MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
No storage issues were detected
Filesystem: 17 new files
Database: no new tables, 7 new options
New WordPress options |
---|
widget_jkl_timezones_widget |
widget_recent-posts |
widget_recent-comments |
widget_theysaidso_widget |
db_upgraded |
can_compress_scripts |
theysaidso_admin_options |
Browser metrics Passed 4 tests
An overview of browser requirements for JKL Timezone Converter
Minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,825 ▲79 | 13.63 ▼0.75 | 1.80 ▲0.07 | 41.61 ▼4.08 |
Dashboard /wp-admin | 2,203 ▲15 | 5.83 ▲0.94 | 98.78 ▼6.48 | 39.24 ▼3.72 |
Posts /wp-admin/edit.php | 2,089 ▼3 | 2.04 ▲0.05 | 39.79 ▼2.43 | 34.37 ▼0.44 |
Add New Post /wp-admin/post-new.php | 1,522 ▼6 | 23.27 ▲4.99 | 664.43 ▲62.22 | 57.34 ▲2.85 |
Media Library /wp-admin/upload.php | 1,388 ▼0 | 4.22 ▲0.01 | 97.44 ▲2.42 | 44.85 ▼0.54 |
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
Please fix the following items
- Zombie WordPress options detected upon uninstall: 7 options
- db_upgraded
- widget_recent-comments
- can_compress_scripts
- theysaidso_admin_options
- widget_jkl_timezones_widget
- widget_recent-posts
- widget_theysaidso_widget
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
The smoke test was a success, however most plugin functionality was not tested
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
Please fix the following
- 2× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Fatal error
Uncaught Error: Call to undefined function get_option() in wp-content/plugins/jkl-timezone-converter/inc/functions.php:19
- > PHP Fatal error
Uncaught Error: Call to undefined function get_option() in wp-content/plugins/jkl-timezone-converter/inc/functions.php:19
- > 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 90% 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: shortcode, custom, calculator, timezones, content...
jkl-timezone-converter/jkl-timezones.php 77% from 13 tests
"JKL Timezone Converter" version 1.0.3's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
Please make the necessary changes and fix the following:
- Main file name: The principal plugin file should be the same as the plugin slug ("jkl-timezone-converter.php" instead of "jkl-timezones.php")
- Text Domain: If you choose to specify the text domain, it must be the same as the plugin slug; optional since WordPress version 4.6
- Description: If Twitter did it, so should we! Keep the description under 140 characters (currently 145 characters long)
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short check of programming languages and file extensions; no executable files are allowed
Good job! No executable or dangerous file extensions detected646 lines of code in 11 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 8 | 161 | 540 | 322 |
CSS | 1 | 8 | 47 | 234 |
Markdown | 1 | 31 | 0 | 80 |
JavaScript | 1 | 5 | 11 | 10 |
PHP code Passed 2 tests
An overview of cyclomatic complexity and code structure
No cyclomatic complexity issues were detected for this plugin
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.32 |
Average class complexity | 4.33 |
▷ Minimum class complexity | 3.00 |
▷ Maximum class complexity | 5.00 |
Average method complexity | 1.83 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 3.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 3 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 3 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 13 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 8 | 61.54% |
▷ Protected methods | 5 | 38.46% |
▷ Private methods | 0 | 0.00% |
Functions | 12 | |
▷ Named functions | 9 | 75.00% |
▷ Anonymous functions | 3 | 25.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
1 compressed PNG file occupies 0.00MB
Potential savings
Compression of 1 random PNG file using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
img/up-down-arrow.png | 0.11KB | 0.11KB | ▼ 2.61% |