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.07MB] [CPU: ▼301.81ms] Passed 4 tests
A check of server-side resources used by Advanced Term Fields
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.67 ▲0.16 | 52.06 ▲2.98 |
| Dashboard /wp-admin | 3.50 ▲0.09 | 33.12 ▲0.07 |
| Posts /wp-admin/edit.php | 3.73 ▲0.09 | 37.69 ▼0.45 |
| Add New Post /wp-admin/post-new.php | 6.99 ▼0.00 | 92.44 ▼1,209.04 |
| Media Library /wp-admin/upload.php | 3.38 ▲0.09 | 25.84 ▲2.18 |
Server storage [IO: ▲0.41MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
There were no storage issued detected upon installing this plugin
Filesystem: 16 new files
Database: no new tables, 1 new option
| New WordPress options |
|---|
| atf_core_version |
Browser metrics Passed 4 tests
Advanced Term Fields: an overview of browser usage
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 3,795 ▲53 | 16.29 ▲0.25 | 6.20 ▼0.23 | 2.79 ▲0.48 |
| Dashboard /wp-admin | 2,895 ▲34 | 6.14 ▼0.03 | 120.24 ▼17.50 | 157.51 ▼12.86 |
| Posts /wp-admin/edit.php | 2,694 ▲3 | 3.23 ▼0.01 | 63.62 ▲0.62 | 140.24 ▼3.86 |
| Add New Post /wp-admin/post-new.php | 1,752 ▼4 | 21.47 ▲4.26 | 422.18 ▲27.09 | 162.90 ▲11.23 |
| Media Library /wp-admin/upload.php | 1,701 ▲3 | 5.55 ▲0.03 | 141.36 ▲3.36 | 185.67 ▲0.07 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
Please fix the following items
- This plugin did not uninstall successfully, leaving 1 option in the database
- atf_core_version
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a short smoke test looking for 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 applies for WordPress plugins as well - please make sure your PHP files perform no actions when accessed directly
Please fix the following
- 4× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/advanced-term-fields/inc/functions.php:33
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_attr() in wp-content/plugins/advanced-term-fields/views/add-form-field.php:16
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_attr() in wp-content/plugins/advanced-term-fields/views/edit-form-field.php:16
- > PHP Fatal error
Uncaught Error: Using $this when not in object context in wp-content/plugins/advanced-term-fields/views/quick-form-field.php:16
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the browser (console and network errors and warnings)
There were no browser issues found
Optimizations
Plugin configuration 96% from 29 tests
readme.txt Passed 16 tests
The readme.txt file is undoubtedly the most important file in your plugin, preparing it for public listing on WordPress.org
6 plugin tags: term, metadata, termmeta, term_meta, taxonomy...
advanced-term-fields/advanced-term-fields.php 92% from 13 tests
The entry point to "Advanced Term Fields" version 0.1.2 is a PHP file that has certain tags in its header comment area
The following require your attention:
- Text Domain: Since WordPress version 4.6 the text domain is optional; if specified, it must be the same as the plugin slug
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | An overview of files in this plugin; executable files are not allowed
Everything looks great! No dangerous files found in this plugin497 lines of code in 8 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 7 | 235 | 991 | 469 |
| Markdown | 1 | 20 | 0 | 28 |
PHP code Passed 2 tests
Analyzing logical lines of code, cyclomatic complexity, and other code metrics
Although this was not an exhaustive test, there were no cyclomatic complexity issues detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.29 |
| Average class complexity | 24.00 |
| ▷ Minimum class complexity | 6.00 |
| ▷ Maximum class complexity | 42.00 |
| Average method complexity | 2.08 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 13.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 2 | |
| ▷ Abstract classes | 1 | 50.00% |
| ▷ Concrete classes | 1 | 50.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 42 | |
| ▷ Static methods | 7 | 16.67% |
| ▷ Public methods | 38 | 90.48% |
| ▷ Protected methods | 1 | 2.38% |
| ▷ Private methods | 3 | 7.14% |
| Functions | 4 | |
| ▷ Named functions | 1 | 25.00% |
| ▷ Anonymous functions | 3 | 75.00% |
| Constants | 2 | |
| ▷ Global constants | 2 | 100.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
1 PNG file occupies 0.03MB with 0.02MB in potential savings
Potential savings
| Compression of 1 random PNG file using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/screenshot.png | 29.72KB | 11.98KB | ▼ 59.68% |