Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
This plugin's installer ran successfully
Server metrics [RAM: ▲0.23MB] [CPU: ▲0.91ms] Passed 4 tests
A check of server-side resources used by Foxdell Folio Block Editor Customiser
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.68 ▲0.21 | 45.64 ▲6.39 |
| Dashboard /wp-admin | 3.58 ▲0.27 | 53.78 ▲9.41 |
| Posts /wp-admin/edit.php | 3.64 ▲0.28 | 55.32 ▲4.43 |
| Add New Post /wp-admin/post-new.php | 6.10 ▲0.21 | 89.66 ▼16.18 |
| Media Library /wp-admin/upload.php | 3.44 ▲0.21 | 43.07 ▲8.99 |
| Add Ons /wp-admin/admin.php?page=fofo_bec_plugin_page_addons | 3.44 | 38.77 |
| Themes /wp-admin/admin.php?page=fofo_bec_plugin_page_themes | 3.44 | 37.87 |
| Block Editor Customiser /wp-admin/admin.php?page=fofo_bec_plugin_page | 3.54 | 39.79 |
Server storage [IO: ▲0.13MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
No storage issues were detected
Filesystem: 19 new files
Database: no new tables, 10 new options
| New WordPress options |
|---|
| FOFO_BEC_CURRENT_THEME |
| widget_theysaidso_widget |
| FOFO_BEC_THEME_REGISTER |
| widget_recent-posts |
| FOFO_BEC_JS_KEY |
| widget_recent-comments |
| can_compress_scripts |
| theysaidso_admin_options |
| FOFO_BEC_ADDON_REGISTER |
| db_upgraded |
Browser metrics Passed 4 tests
Foxdell Folio Block Editor Customiser: an overview of browser usage
This plugin has a minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,973 ▲216 | 23.81 ▲9.07 | 1.87 ▼0.07 | 42.86 ▲2.36 |
| Dashboard /wp-admin | 2,377 ▲222 | 13.12 ▲7.47 | 313.73 ▲216.94 | 68.90 ▲28.93 |
| Posts /wp-admin/edit.php | 2,318 ▲226 | 11.70 ▲9.69 | 117.09 ▲72.82 | 33.94 ▼2.13 |
| Add New Post /wp-admin/post-new.php | 1,560 ▲41 | 23.04 ▼0.05 | 521.86 ▼145.16 | 38.44 ▼22.17 |
| Media Library /wp-admin/upload.php | 1,554 ▲166 | 14.36 ▲10.11 | 153.71 ▲43.95 | 45.21 ▼2.78 |
| Add Ons /wp-admin/admin.php?page=fofo_bec_plugin_page_addons | 1,029 | 13.35 | 104.98 | 26.92 |
| Themes /wp-admin/admin.php?page=fofo_bec_plugin_page_themes | 1,042 | 13.30 | 92.57 | 24.37 |
| Block Editor Customiser /wp-admin/admin.php?page=fofo_bec_plugin_page | 1,122 | 13.31 | 104.41 | 28.52 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
Please fix the following items
- The uninstall procedure has failed, leaving 10 options in the database
- FOFO_BEC_ADDON_REGISTER
- widget_recent-posts
- widget_theysaidso_widget
- widget_recent-comments
- db_upgraded
- can_compress_scripts
- FOFO_BEC_JS_KEY
- FOFO_BEC_CURRENT_THEME
- FOFO_BEC_THEME_REGISTER
- theysaidso_admin_options
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
Everything seems fine, however this is by no means an exhaustive test
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
- 1× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/foxdell-folio-block-editor-customiser/includes/fofo-bec-default-theme.php:15
- > 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
- 3 occurences, only the last one shown
- > GET request to /wp-admin/admin.php?page=fofo_bec_plugin_page
- > Javascript (severe) in unknown
/wp-content/plugins/foxdell-folio-block-editor-customiser/js/fofobec.js?ver=1.0.2 95:25 Uncaught ReferenceError: fofobec_function_dispatcher is not defined
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 94% from 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
Attributes that require attention:
- Screenshots: Screenshot #1 (The FoFo Block Customiser screen (1.png).) image required
foxdell-folio-block-editor-customiser/fofo-block-editor-customiser.php 85% from 13 tests
The main file in "Foxdell Folio Block Editor Customiser" v. 1.6.0 serves as a complement to information provided in readme.txt and as the entry point to the plugin
Please take the time to fix the following:
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("foxdell-folio-block-editor-customiser.php" instead of "fofo-block-editor-customiser.php")
- Text Domain: You no longer need to specify the text domain since WordPress 4.6; it must be the same as the plugin slug
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
No dangerous file extensions were detected1,068 lines of code in 16 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 15 | 420 | 1,177 | 1,003 |
| JavaScript | 1 | 26 | 19 | 65 |
PHP code Passed 2 tests
This plugin's cyclomatic complexity and code structure detailed below
Although this was not an exhaustive test, there were no cyclomatic complexity issues detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.24 |
| Average class complexity | 8.23 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 41.00 |
| Average method complexity | 1.98 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 11.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 1 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 13 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 13 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 99 | |
| ▷ Static methods | 10 | 10.10% |
| ▷ Public methods | 72 | 72.73% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 27 | 27.27% |
| Functions | 26 | |
| ▷ Named functions | 4 | 15.38% |
| ▷ Anonymous functions | 22 | 84.62% |
| Constants | 41 | |
| ▷ Global constants | 41 | 100.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.02MB with 0.01MB in potential savings
Potential savings
| Compression of 1 random PNG file using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/1.PNG | 21.18KB | 8.83KB | ▼ 58.29% |