Benchmarks
Plugin footprint 83% 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.01MB] [CPU: ▼5.61ms] Passed 4 tests
Analyzing server-side resources used by Advanced Custom Fields: DB Field
This plugin has minimal impact on server resources
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.47 ▲0.01 | 37.82 ▼4.41 |
Dashboard /wp-admin | 3.31 ▲0.01 | 47.84 ▼4.57 |
Posts /wp-admin/edit.php | 3.36 ▲0.01 | 49.11 ▲0.39 |
Add New Post /wp-admin/post-new.php | 5.89 ▲0.01 | 88.16 ▼12.95 |
Media Library /wp-admin/upload.php | 3.23 ▲0.01 | 37.47 ▼0.51 |
Server storage [IO: ▲0.08MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
This plugin was installed successfully
Filesystem: 11 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_theysaidso_widget |
db_upgraded |
widget_recent-posts |
widget_recent-comments |
theysaidso_admin_options |
can_compress_scripts |
Browser metrics Passed 4 tests
Advanced Custom Fields: DB Field: 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 / | 2,800 ▲65 | 13.33 ▼1.05 | 1.64 ▼0.21 | 40.84 ▼2.74 |
Dashboard /wp-admin | 2,206 ▲15 | 4.88 ▼1.02 | 108.21 ▲8.27 | 38.18 ▼5.41 |
Posts /wp-admin/edit.php | 2,089 ▼0 | 1.97 ▲0.00 | 39.94 ▲3.48 | 34.04 ▲1.77 |
Add New Post /wp-admin/post-new.php | 1,535 ▲21 | 23.36 ▲5.70 | 650.44 ▼23.12 | 67.80 ▲18.16 |
Media Library /wp-admin/upload.php | 1,391 ▼0 | 4.27 ▲0.08 | 94.71 ▼1.74 | 41.96 ▼3.99 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
It is recommended to fix the following
- This plugin did not uninstall successfully, leaving 6 options in the database
- widget_recent-posts
- db_upgraded
- theysaidso_admin_options
- can_compress_scripts
- widget_theysaidso_widget
- widget_recent-comments
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
Even though everything seems fine, this is not an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | SRP (Single-Responsibility Principle) - PHP files must act as libraries and never output text or perform any action when accessed directly in a browser
Almost there! Just fix the following items
- 8× PHP files trigger errors when accessed directly with GET requests:
- > PHP Notice
Trying to access array offset on value of type null in wp-content/plugins/acf-db-field/views/parts-item-list.php on line 2
- > PHP Notice
Trying to access array offset on value of type null in wp-content/plugins/acf-db-field/views/parts-item-list.php on line 1
- > PHP Notice
Undefined variable: field in wp-content/plugins/acf-db-field/views/parts-item-list.php on line 2
- > PHP Fatal error
Uncaught Error: Class 'acf_db_common' not found in wp-content/plugins/acf-db-field/fields/acf-db.php:3
- > PHP Fatal error
Uncaught Error: Class 'acf_field' not found in wp-content/plugins/acf-db-field/fields/acf-db-common.php:2
- > PHP Warning
Invalid argument supplied for foreach() in wp-content/plugins/acf-db-field/views/parts-item-list.php on line 3
- > PHP Notice
Undefined variable: field in wp-content/plugins/acf-db-field/views/parts-item-list.php on line 1
- > PHP Notice
Undefined variable: posts in wp-content/plugins/acf-db-field/views/parts-item-list.php on line 3
- > PHP Notice
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
No browser issues were found
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 94% from 16 tests
It's important to format your readme.txt file correctly as it is parsed for the public listing of your plugin
Please fix the following attributes:
- Screenshots: Add images for these screenshots: #1 (DB Field Settings), #2 (Edit Post With DB Field)
acf-db-field/acf-db.php 85% from 13 tests
The primary PHP file in "Advanced Custom Fields: DB Field" version 1.0.1 is used by WordPress to initiate all plugin functionality
The following require your attention:
- Main file name: The principal plugin file should be the same as the plugin slug ("acf-db-field.php" instead of "acf-db.php")
- Text Domain: The text domain must be the same as the plugin slug, although optional since WordPress version 4.6
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are considered dangerous and should not be included with any WordPress plugin
Success! There were no dangerous files found in this plugin459 lines of code in 7 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 4 | 7 | 27 | 273 |
JavaScript | 1 | 0 | 0 | 163 |
Markdown | 1 | 7 | 0 | 14 |
CSS | 1 | 0 | 0 | 9 |
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.26 |
Average class complexity | 10.33 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 27.00 |
Average method complexity | 2.75 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 9.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 3 | |
▷ Abstract classes | 1 | 33.33% |
▷ Concrete classes | 2 | 66.67% |
▷ Final classes | 0 | 0.00% |
Methods | 16 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 16 | 100.00% |
▷ Protected methods | 0 | 0.00% |
▷ 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
Using a strong compression for your PNG files is a great way to speed-up your plugin
2 PNG files occupy 0.07MB with 0.03MB in potential savings
Potential savings
Compression of 2 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
screenshot-2.png | 26.78KB | 14.00KB | ▼ 47.74% |
screenshot-1.png | 40.92KB | 20.55KB | ▼ 49.76% |