Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.00MB] [CPU: ▼5.92ms] Passed 4 tests
This is a short check of server-side resources used by Advanced Custom Fields: Widget
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.48 ▲0.02 | 37.87 ▼0.30 |
Dashboard /wp-admin | 3.32 ▼0.03 | 44.62 ▼17.53 |
Posts /wp-admin/edit.php | 3.37 ▲0.01 | 48.92 ▲1.23 |
Add New Post /wp-admin/post-new.php | 5.90 ▲0.01 | 90.17 ▼5.73 |
Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 33.91 ▼0.11 |
Server storage [IO: ▲0.18MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
This plugin was installed successfully
Filesystem: 12 new files
Database: no new tables, 7 new options
New WordPress options |
---|
widget_recent-comments |
widget_theysaidso_widget |
can_compress_scripts |
db_upgraded |
theysaidso_admin_options |
widget_recent-posts |
widget_acf_widget |
Browser metrics Passed 4 tests
Advanced Custom Fields: Widget: an overview of browser usage
Minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,800 ▲54 | 13.29 ▼1.09 | 1.81 ▲0.08 | 37.53 ▼7.23 |
Dashboard /wp-admin | 2,206 ▲18 | 4.85 ▼0.06 | 108.85 ▲0.73 | 39.86 ▲0.44 |
Posts /wp-admin/edit.php | 2,089 ▼0 | 1.99 ▼0.01 | 39.11 ▲0.82 | 36.75 ▲2.35 |
Add New Post /wp-admin/post-new.php | 1,537 ▲4 | 23.39 ▲0.49 | 674.05 ▲29.73 | 52.51 ▲1.51 |
Media Library /wp-admin/upload.php | 1,391 ▲3 | 4.21 ▲0.03 | 96.60 ▼4.20 | 42.21 ▼2.65 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
Please fix the following items
- This plugin did not uninstall successfully, leaving 7 options in the database
- db_upgraded
- widget_recent-comments
- widget_acf_widget
- can_compress_scripts
- widget_theysaidso_widget
- widget_recent-posts
- theysaidso_admin_options
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
The smoke test was a success, however most plugin functionality was not tested
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
The following issues need your attention
- 3× PHP files trigger server errors when accessed directly:
- > PHP Fatal error
Uncaught Error: Class 'WP_Widget' not found in wp-content/plugins/advanced-custom-fields-widget/includes/class-acf-widget.php:3
- > PHP Fatal error
Uncaught Error: Using $this when not in object context in wp-content/plugins/advanced-custom-fields-widget/partials/acf-widget-html.php:1
- > PHP Fatal error
Uncaught Error: Class 'WP_Widget' not found in wp-content/plugins/advanced-custom-fields-widget/includes/class-acf-widget.php:3
- > 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)
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 93% from 29 tests
readme.txt Passed 16 tests
Don't ignore readme.txt as it is the file that instructs WordPress.org on how to present your plugin to the world
4 plugin tags: advanced custom fields, widget, acf, widgets
advanced-custom-fields-widget/acf-widget.php 85% from 13 tests
The main PHP script in "Advanced Custom Fields: Widget" version 1.0.2 is automatically included on every request by WordPress
Please take the time to fix the following:
- Main file name: The principal plugin file should be the same as the plugin slug ("advanced-custom-fields-widget.php" instead of "acf-widget.php")
- Text Domain: Please use dashes and lowercase characters for text domains
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
Good job! No executable or dangerous file extensions detected269 lines of code in 6 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 5 | 169 | 44 | 264 |
JavaScript | 1 | 4 | 0 | 5 |
PHP code Passed 2 tests
Analyzing cyclomatic complexity and code structure
Great job! No cyclomatic complexity issues were detected in this plugin
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.27 |
Average class complexity | 7.67 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 19.00 |
Average method complexity | 2.25 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 6.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 3 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 3 | 100.00% |
▷ 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 | 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
PNG files should be compressed to save space and minimize bandwidth usage
4 PNG files occupy 0.16MB with 0.11MB in potential savings
Potential savings
Compression of 4 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
screenshot-4.png | 48.26KB | 14.56KB | ▼ 69.83% |
screenshot-1.png | 48.42KB | 15.27KB | ▼ 68.47% |
screenshot-3.png | 38.01KB | 12.16KB | ▼ 68.00% |
screenshot-2.png | 32.78KB | 10.25KB | ▼ 68.72% |