Benchmarks
Plugin footprint 82% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
Installer ran successfully
Server metrics [RAM: ▲0.04MB] [CPU: ▼3.27ms] Passed 4 tests
Server-side resources used by Custom Fields to Metaboxes
Normal server usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.51 ▲0.05 | 49.77 ▲4.45 |
Dashboard /wp-admin | 3.36 ▲0.01 | 54.77 ▼7.67 |
Posts /wp-admin/edit.php | 3.41 ▲0.05 | 51.58 ▲2.75 |
Add New Post /wp-admin/post-new.php | 5.94 ▲0.05 | 82.82 ▼11.97 |
Media Library /wp-admin/upload.php | 3.28 ▲0.05 | 40.08 ▲3.80 |
Cust. Fields to Meta /wp-admin/tools.php?page=custom-fields-to-metabox | 3.25 | 33.35 |
Server storage [IO: ▲0.02MB] [DB: ▲0.00MB] 67% from 3 tests
Filesystem and database footprint
These are issues you should consider
- The plugin illegally modified 1 file (4.00KB) outside of "wp-content/plugins/custom-fields-to-metaboxes/" and "wp-content/uploads/"
- (new file) wp-content/mgd_mirror/mgd_maximinodotpy-gitdown-test-repository
Filesystem: 4 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_recent-posts |
can_compress_scripts |
theysaidso_admin_options |
db_upgraded |
widget_theysaidso_widget |
widget_recent-comments |
Browser metrics Passed 4 tests
A check of browser resources used by Custom Fields to Metaboxes
Minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,819 ▲48 | 14.67 ▲0.29 | 1.91 ▼0.38 | 43.67 ▼5.56 |
Dashboard /wp-admin | 2,225 ▲22 | 5.83 ▲0.01 | 98.12 ▼21.91 | 41.13 ▼12.31 |
Posts /wp-admin/edit.php | 2,107 ▲7 | 1.98 ▼0.04 | 40.69 ▲5.47 | 32.83 ▼5.66 |
Add New Post /wp-admin/post-new.php | 1,534 ▲8 | 23.31 ▼0.18 | 684.44 ▲64.00 | 54.00 ▲4.03 |
Media Library /wp-admin/upload.php | 1,404 ▲4 | 4.22 ▲0.02 | 101.08 ▼6.80 | 45.71 ▼9.43 |
Cust. Fields to Meta /wp-admin/tools.php?page=custom-fields-to-metabox | 962 | 1.72 | 26.54 | 31.62 |
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: 6 options
- db_upgraded
- widget_recent-comments
- can_compress_scripts
- widget_theysaidso_widget
- theysaidso_admin_options
- widget_recent-posts
Smoke tests 50% from 4 tests
Server-side errors 0% from 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
Please fix the following server-side errors
- 2 occurences, only the last one shown
- > GET request to /wp-admin/tools.php?page=custom-fields-to-metabox
- > request to
- > Notice in wp-config.php+20
Undefined index: REQUEST_METHOD
SRP 50% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle applies for WordPress plugins as well - please make sure your PHP files perform no actions when accessed directly
Almost there! Just fix the following items
- 1× PHP files trigger server errors when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function get_option() in wp-content/plugins/custom-fields-to-metaboxes/custom-fields-to-metaboxes.php:565
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
Everything seems fine on the user side
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 94% from 16 tests
Perhaps the most important file in your plugin readme.txt gets parsed in order to generate the public listing of your plugin
These attributes need your attention:
- Donate link: Please fix this invalid url: "erikdmitchell@gmail.com"
custom-fields-to-metaboxes/custom-fields-to-metaboxes.php 85% from 13 tests
The primary PHP file in "Custom Fields to Metaboxes" version 0.1.1 is used by WordPress to initiate all plugin functionality
The following require your attention:
- Domain Path: The domain path folder was not found ("/languages")
- 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
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short review of files and their extensions; it is not recommended to include executable files
No dangerous file extensions were detected471 lines of code in 3 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 1 | 102 | 136 | 338 |
JavaScript | 1 | 25 | 9 | 82 |
CSS | 1 | 0 | 0 | 51 |
PHP code Passed 2 tests
An overview of cyclomatic complexity and code structure
There are no cyclomatic complexity problems detected for this plugin
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.35 |
Average class complexity | 55.00 |
▷ Minimum class complexity | 55.00 |
▷ Maximum class complexity | 55.00 |
Average method complexity | 4.18 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 9.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 | 17 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 14 | 82.35% |
▷ Protected methods | 3 | 17.65% |
▷ Private methods | 0 | 0.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
PNG files should be compressed to save space and minimize bandwidth usage
No PNG images were found in this plugin