Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
Install script ran successfully
Server metrics [RAM: ▲0.00MB] [CPU: ▼2.79ms] Passed 4 tests
This is a short check of server-side resources used by Post Type Select Field for Advanced Custom Fields
This plugin has minimal impact on server resources
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.47 ▲0.01 | 46.25 ▲6.95 |
| Dashboard /wp-admin | 3.31 ▲0.00 | 51.39 ▼15.48 |
| Posts /wp-admin/edit.php | 3.36 ▲0.00 | 49.08 ▼6.13 |
| Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 103.48 ▲13.73 |
| Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 38.25 ▲3.49 |
Server storage [IO: ▲0.01MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
This plugin installed successfully
Filesystem: 4 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_recent-comments |
| can_compress_scripts |
| widget_theysaidso_widget |
| widget_recent-posts |
| db_upgraded |
| theysaidso_admin_options |
Browser metrics Passed 4 tests
Post Type Select Field for Advanced Custom Fields: an overview of browser usage
This plugin has a minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,800 ▲11 | 13.24 ▼1.24 | 1.98 ▲0.20 | 45.15 ▲6.35 |
| Dashboard /wp-admin | 2,206 ▲12 | 4.86 ▲0.04 | 104.52 ▼14.10 | 37.12 ▼7.40 |
| Posts /wp-admin/edit.php | 2,089 ▲3 | 2.05 ▲0.03 | 37.80 ▲4.11 | 34.10 ▼5.43 |
| Add New Post /wp-admin/post-new.php | 1,524 ▼18 | 23.32 ▲5.05 | 718.87 ▲62.03 | 58.90 ▼6.56 |
| Media Library /wp-admin/upload.php | 1,382 ▼0 | 4.21 ▲0.01 | 98.30 ▼4.97 | 43.98 ▲0.25 |
Uninstaller [IO: ✅] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
You still need to fix the following
- Zombie WordPress options detected upon uninstall: 6 options
- widget_theysaidso_widget
- theysaidso_admin_options
- db_upgraded
- widget_recent-posts
- widget_recent-comments
- can_compress_scripts
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
Even though everything seems fine, this is not 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
- 3× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function load_plugin_textdomain() in wp-content/plugins/post-type-select-for-advanced-custom-fields/acf-posttype-select.php:15
- > PHP Fatal error
Uncaught Error: Class 'acf_field' not found in wp-content/plugins/post-type-select-for-advanced-custom-fields/acf-posttype-select-v4.php:2
- > PHP Fatal error
Uncaught Error: Class 'acf_field' not found in wp-content/plugins/post-type-select-for-advanced-custom-fields/acf-posttype-select-v5.php:2
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
No browser errors were detected
Optimizations
Plugin configuration 96% from 29 tests
readme.txt Passed 16 tests
Perhaps the most important file in your plugin readme.txt gets parsed in order to generate the public listing of your plugin
4 plugin tags: advanced custom fields, post type, select, acf
post-type-select-for-advanced-custom-fields/acf-posttype-select.php 92% from 13 tests
The principal PHP file in "Post Type Select Field for Advanced Custom Fields" v. 1.1.0 is loaded by WordPress automatically on each request
You should first fix the following items:
- Main file name: It is recommended to name the main PHP file as the plugin slug ("post-type-select-for-advanced-custom-fields.php" instead of "acf-posttype-select.php")
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 detected265 lines of code in 3 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 3 | 52 | 137 | 265 |
PHP code Passed 2 tests
This plugin's cyclomatic complexity and code structure detailed below
All good! No complexity issues found
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.25 |
| Average class complexity | 10.50 |
| ▷ Minimum class complexity | 8.00 |
| ▷ Maximum class complexity | 13.00 |
| Average method complexity | 3.38 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 12.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 2 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 2 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 8 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 6 | 75.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 2 | 25.00% |
| Functions | 2 | |
| ▷ Named functions | 2 | 100.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
There are no PNG files in this plugin