Benchmarks
Plugin footprint 65% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | All plugins must install correctly, without throwing any errors, warnings, or notices
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.58MB] [CPU: ▲2.71ms] Passed 4 tests
An overview of server-side resources used by Custom Field Suite
No issues were detected with server-side resource usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 4.05 ▲0.59 | 45.98 ▲6.29 |
| Dashboard /wp-admin | 3.89 ▲0.58 | 46.50 ▼0.71 |
| Posts /wp-admin/edit.php | 3.94 ▲0.58 | 48.94 ▲2.52 |
| Add New Post /wp-admin/post-new.php | 6.47 ▲0.59 | 94.44 ▲13.42 |
| Media Library /wp-admin/upload.php | 3.81 ▲0.58 | 37.74 ▲2.75 |
| Custom Field Suite /wp-admin/edit.php?post_type=cfs | 3.85 | 36.91 |
| CFS Tools /wp-admin/tools.php?page=cfs-tools | 3.72 | 32.85 |
Server storage [IO: ▲0.75MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
This plugin installed successfully
Filesystem: 83 new files
Database: 2 new tables, 8 new options
| New tables |
|---|
| wp_cfs_values |
| wp_cfs_sessions |
| New WordPress options |
|---|
| widget_recent-comments |
| db_upgraded |
| theysaidso_admin_options |
| cfs_version |
| widget_theysaidso_widget |
| widget_recent-posts |
| can_compress_scripts |
| cfs_next_field_id |
Browser metrics Passed 4 tests
Custom Field Suite: an overview of browser usage
This plugin has a minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,817 ▲71 | 13.31 ▼0.98 | 4.72 ▲2.57 | 42.32 ▼3.95 |
| Dashboard /wp-admin | 2,220 ▲35 | 4.84 ▼0.00 | 98.58 ▼8.44 | 39.13 ▼5.52 |
| Posts /wp-admin/edit.php | 2,106 ▲17 | 2.04 ▼0.01 | 40.38 ▼0.72 | 35.12 ▼1.17 |
| Add New Post /wp-admin/post-new.php | 1,544 ▲11 | 23.21 ▼0.04 | 663.05 ▼16.21 | 58.97 ▼9.47 |
| Media Library /wp-admin/upload.php | 1,399 ▲17 | 4.18 ▼0.05 | 95.88 ▼5.40 | 39.35 ▼7.43 |
| Custom Field Suite /wp-admin/edit.php?post_type=cfs | 1,075 | 1.97 | 33.05 | 26.82 |
| CFS Tools /wp-admin/tools.php?page=cfs-tools | 862 | 1.76 | 25.70 | 37.87 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 50% from 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
It is recommended to fix the following
- The uninstall procedure failed, leaving 2 tables in the database
- wp_cfs_sessions
- wp_cfs_values
- Zombie WordPress options detected upon uninstall: 8 options
- widget_theysaidso_widget
- cfs_next_field_id
- db_upgraded
- widget_recent-comments
- cfs_version
- theysaidso_admin_options
- can_compress_scripts
- widget_recent-posts
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
Even though no errors were found, this is by no means an exhaustive test
SRP 0% 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
The following issues need your attention
- 1× PHP files output text when accessed directly:
- > /wp-content/plugins/custom-field-suite/templates/credits.php
- 32× GET requests to PHP files have triggered server-side errors or warnings (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Class 'cfs_field' not found in wp-content/plugins/custom-field-suite/includes/fields/term.php:3
- > PHP Fatal error
Uncaught Error: Class 'cfs_field' not found in wp-content/plugins/custom-field-suite/includes/fields/color/color.php:3
- > PHP Notice
Trying to get property 'post_type' of non-object in wp-content/plugins/custom-field-suite/templates/admin_head.php on line 9
- > PHP Fatal error
Uncaught Error: Class 'cfs_field' not found in wp-content/plugins/custom-field-suite/includes/fields/true_false.php:3
- > PHP Fatal error
Uncaught Error: Class 'cfs_field' not found in wp-content/plugins/custom-field-suite/includes/fields/wysiwyg.php:3
- > PHP Fatal error
Uncaught Error: Class 'cfs_field' not found in wp-content/plugins/custom-field-suite/includes/fields/text.php:3
- > PHP Fatal error
Uncaught Error: Class 'cfs_field' not found in wp-content/plugins/custom-field-suite/includes/fields/loop.php:3
- > PHP Notice
Undefined variable: screen in wp-content/plugins/custom-field-suite/templates/admin_head.php on line 9
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/custom-field-suite/includes/init.php:7
- > PHP Fatal error
Uncaught Error: Class 'cfs_field' not found in wp-content/plugins/custom-field-suite/includes/fields/relationship.php:3
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
There were no browser issues found
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
Attributes that need to be fixed:
- Screenshots: Add descriptions for screenshots #1, #2, #3, #4 in custom-field-suite/assets to your readme.txt
custom-field-suite/cfs.php 85% from 13 tests
The main PHP file in "Custom Field Suite" ver. 2.6.4 adds more information about the plugin and also serves as the entry point for this plugin
It is important to fix the following:
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("custom-field-suite.php" instead of "cfs.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
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is a short overview of programming languages used in this plugin, detecting executable files
Everything looks great! No dangerous files found in this plugin11,088 lines of code in 63 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 33 | 901 | 549 | 4,004 |
| PO File | 15 | 1,769 | 2,601 | 3,457 |
| CSS | 6 | 300 | 100 | 1,888 |
| JavaScript | 7 | 148 | 139 | 1,713 |
| JSON | 1 | 0 | 0 | 21 |
| Markdown | 1 | 2 | 0 | 5 |
PHP code Passed 2 tests
A brief analysis of cyclomatic complexity and code structure for this plugin
No cyclomatic complexity issues were detected for this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.34 |
| Average class complexity | 15.68 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 121.00 |
| Average method complexity | 3.32 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 36.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 25 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 25 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 158 | |
| ▷ Static methods | 1 | 0.63% |
| ▷ Public methods | 153 | 96.84% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 5 | 3.16% |
| Functions | 2 | |
| ▷ Named functions | 2 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 3 | |
| ▷ Global constants | 3 | 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
3 compressed PNG files occupy 0.00MB
Potential savings
| Compression of 3 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/js/select2/select2.png | 0.60KB | 0.99KB | 0.00% |
| assets/images/icon-calendar.png | 0.22KB | 0.17KB | ▼ 24.35% |
| assets/js/select2/select2x2.png | 0.83KB | 0.77KB | ▼ 6.15% |