Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.03MB] [CPU: ▼3.27ms] Passed 4 tests
A check of server-side resources used by JF Simple Coming Soon
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.49 ▲0.02 | 45.87 ▲0.34 |
| Dashboard /wp-admin | 3.34 ▲0.04 | 55.86 ▼0.24 |
| Posts /wp-admin/edit.php | 3.40 ▲0.04 | 54.21 ▼11.05 |
| Add New Post /wp-admin/post-new.php | 5.93 ▲0.04 | 133.77 ▲26.15 |
| Media Library /wp-admin/upload.php | 3.27 ▲0.04 | 38.93 ▼2.14 |
| Simple Coming Soon /wp-admin/options-general.php?page=jf-simple-coming-soon | 3.26 | 34.10 |
Server storage [IO: ▲0.46MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
The plugin installed successfully
Filesystem: 19 new files
Database: no new tables, 15 new options
| New WordPress options |
|---|
| widget_recent-posts |
| jf_scs_topmargin_field |
| jf_scs_bgcolor_field |
| widget_recent-comments |
| widget_theysaidso_widget |
| jf_scs_enable |
| db_upgraded |
| can_compress_scripts |
| theysaidso_admin_options |
| jf_scs_use_custom_css |
| ... |
Browser metrics Passed 4 tests
Checking browser requirements for JF Simple Coming Soon
Normal browser usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,793 ▲47 | 14.28 ▼0.31 | 2.06 ▲0.09 | 49.08 ▲1.58 |
| Dashboard /wp-admin | 2,196 ▲16 | 5.57 ▼0.09 | 93.69 ▼21.80 | 40.99 ▼12.39 |
| Posts /wp-admin/edit.php | 2,107 ▲7 | 1.98 ▼0.05 | 41.33 ▼7.80 | 37.72 ▼7.92 |
| Add New Post /wp-admin/post-new.php | 1,529 ▲1 | 23.18 ▼0.03 | 704.63 ▼18.97 | 58.51 ▼18.76 |
| Media Library /wp-admin/upload.php | 1,404 ▲7 | 4.20 ▼0.01 | 117.79 ▲3.60 | 59.04 ▼2.59 |
| Simple Coming Soon /wp-admin/options-general.php?page=jf-simple-coming-soon | 1,836 | 8.14 | 191.53 | 72.79 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
These items require your attention
- Zombie WordPress options detected upon uninstall: 15 options
- jf_scs_use_custom_css
- jf_scs_delete_options
- theysaidso_admin_options
- jf_scs_title_field
- jf_scs_topmargin_field
- jf_scs_enable
- can_compress_scripts
- jf_scs_custom_css_field
- jf_scs_bgcolor_field
- jf_scs_textcolor_field
- ...
Smoke tests 25% from 4 tests
Server-side errors 0% from 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the server (in the Apache logs)
Smoke test failed, please fix the following
- > GET request to /wp-admin/options-general.php?page=jf-simple-coming-soon
- > User deprecated in wp-includes/functions.php+5463
Function screen_icon is deprecated since version 3.8.0 with no alternative available.
- > GET request to /wp-admin/options-general.php?page=jf-simple-coming-soon
- > User deprecated in wp-includes/functions.php+5463
Function get_screen_icon is deprecated since version 3.8.0 with no alternative available.
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
- 2× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Fatal error
Uncaught Error: Call to undefined function bloginfo() in wp-content/plugins/jf-simple-coming-soon/views/replacement-template.php:15
- > PHP Fatal error
Uncaught Error: Call to undefined function screen_icon() in wp-content/plugins/jf-simple-coming-soon/views/admin.php:14
- > PHP Fatal error
User-side errors 0% from 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
There are user-side issues you should fix
- > GET request to /wp-admin/options-general.php?page=jf-simple-coming-soon
- > Console-api (warning) in unknown
/wp-admin/load-scripts.php?c=0&load%5Bchunk_0%5D=jquery-core,jquery-migrate,utils,wp-polyfill-inert,regenerator-runtime,wp-polyfill,wp-hooks&ver=6.3.1 1:28609 "jQuery.Deferred exception: Cannot read properties of undefined (reading 'msie')" "TypeError: Cannot read properties of undefined (reading 'msie')\n at HTMLDocument.\u003Canonymous> (/wp-content/plugins/jf-simple-coming-soon/js/admin.js?ver=1.0.0:25:18)\n at e (/wp-admin/load-scripts.php?c=0&load%5Bchunk_0%5D=jquery-core,jquery-migrate,utils,wp-polyfill-inert,regenerator-runtime,wp-polyfill,wp-hooks&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,wp-polyfill-inert,regenerator-runtime,wp-polyfill,wp-hooks&ver=6.3.1:2:27292)" undefined
- > GET request to /wp-admin/options-general.php?page=jf-simple-coming-soon
- > Javascript (severe) in unknown
/wp-admin/load-scripts.php?c=0&load%5Bchunk_0%5D=jquery-core,jquery-migrate,utils,wp-polyfill-inert,regenerator-runtime,wp-polyfill,wp-hooks&ver=6.3.1 1:28721 Uncaught TypeError: Cannot read properties of undefined (reading 'msie')
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file is undoubtedly the most important file in your plugin, preparing it for public listing on WordPress.org
These attributes need your attention:
- Screenshots: Screenshot #1 (Options page) image missing
jf-simple-coming-soon/jf-simple-coming-soon.php 85% from 13 tests
The entry point to "JF Simple Coming Soon" version 1.0.0 is a PHP file that has certain tags in its header comment area
You should first fix the following items:
- Text Domain: The text domain must be the same as the plugin slug, although optional since WordPress version 4.6
- Description: The description should be shorter than 140 characters (currently 187 characters long)
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | There should be no dangerous file extensions present in any WordPress plugin
Success! There were no dangerous files found in this plugin324 lines of code in 11 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 6 | 71 | 223 | 274 |
| JavaScript | 4 | 6 | 2 | 40 |
| CSS | 1 | 1 | 1 | 10 |
PHP code Passed 2 tests
An short overview of logical lines of code, cyclomatic complexity, and other code metrics
This plugin has no cyclomatic complexity problems
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.29 |
| Average class complexity | 28.00 |
| ▷ Minimum class complexity | 28.00 |
| ▷ Maximum class complexity | 28.00 |
| Average method complexity | 2.35 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 8.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 | 20 | |
| ▷ Static methods | 5 | 25.00% |
| ▷ Public methods | 18 | 90.00% |
| ▷ Protected methods | 1 | 5.00% |
| ▷ Private methods | 1 | 5.00% |
| 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
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
1 PNG file occupies 0.03MB with 0.01MB in potential savings
Potential savings
| Compression of 1 random PNG file using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| screenshot-1.png | 29.43KB | 15.04KB | ▼ 48.91% |