Benchmarks
Plugin footprint Passed 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.01MB] [CPU: ▼292.57ms] Passed 4 tests
Analyzing server-side resources used by Advanced Custom Fields: oEmbed Field
This plugin has minimal impact on server resources
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.57 ▲0.02 | 66.06 ▲14.89 |
| Dashboard /wp-admin | 3.45 ▲0.01 | 33.58 ▼0.27 |
| Posts /wp-admin/edit.php | 3.69 ▲0.01 | 36.47 ▼2.13 |
| Add New Post /wp-admin/post-new.php | 6.92 ▼0.08 | 92.73 ▼1,166.20 |
| Media Library /wp-admin/upload.php | 3.34 ▲0.01 | 24.47 ▼1.68 |
Server storage [IO: ▲0.18MB] [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: 12 new files
Database: no new tables, no new options
Browser metrics Passed 4 tests
This is an overview of browser requirements for Advanced Custom Fields: oEmbed Field
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 3,795 ▲41 | 15.88 ▲0.17 | 6.02 ▼0.27 | 3.07 ▲0.53 |
| Dashboard /wp-admin | 2,895 ▲37 | 6.11 ▼0.05 | 117.43 ▼21.42 | 154.62 ▼13.06 |
| Posts /wp-admin/edit.php | 2,688 ▼6 | 3.24 ▲0.00 | 64.30 ▼0.11 | 143.10 ▼1.96 |
| Add New Post /wp-admin/post-new.php | 1,781 ▲91 | 22.27 ▲1.29 | 414.17 ▼38.90 | 158.85 ▼0.74 |
| Media Library /wp-admin/upload.php | 1,698 ▲6 | 5.48 ▼0.01 | 144.07 ▲0.07 | 192.32 ▲7.03 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] Passed 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
Uninstaller ran successfully
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
Even though everything seems fine, this is not 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
Almost there! Just fix the following items
- 3× PHP files trigger server errors when accessed directly:
- > PHP Fatal error
Uncaught Error: Class 'acf_Field' not found in wp-content/plugins/advanced-custom-fields-oembed-field/oembed-v3.php:3
- > PHP Fatal error
Uncaught Error: Class 'acf_field' not found in wp-content/plugins/advanced-custom-fields-oembed-field/oembed-v4.php:3
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/advanced-custom-fields-oembed-field/acf-oembed.php:34
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
Everything seems fine on the user side
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file describes your plugin functionality and requirements and it is parsed to prepare the your plugin's listing
These attributes need your attention:
- Screenshots: These screenshots have no corresponding images in /assets: #1 (The Add Field interface.), #2 (The field in an Advanced Custom Field.)
advanced-custom-fields-oembed-field/acf-oembed.php 92% from 13 tests
The main file in "Advanced Custom Fields: oEmbed Field" v. 1.0.3 serves as a complement to information provided in readme.txt and as the entry point to the plugin
It is important to fix the following:
- Main file name: Name the main plugin file the same as the plugin slug ("advanced-custom-fields-oembed-field.php" instead of "acf-oembed.php")
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
Success! There were no dangerous files found in this plugin414 lines of code in 8 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 4 | 152 | 302 | 323 |
| JavaScript | 2 | 11 | 0 | 41 |
| CSS | 1 | 3 | 0 | 26 |
| Markdown | 1 | 18 | 0 | 24 |
PHP code Passed 2 tests
Cyclomatic complexity and code structure are the fingerprint of this plugin
There are no cyclomatic complexity problems detected for this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.20 |
| Average class complexity | 6.00 |
| ▷ Minimum class complexity | 2.00 |
| ▷ Maximum class complexity | 17.00 |
| Average method complexity | 1.87 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 9.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 4 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 4 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 23 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 23 | 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
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
2 PNG files occupy 0.15MB with 0.09MB in potential savings
Potential savings
| Compression of 2 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| screenshot-1.png | 78.88KB | 39.36KB | ▼ 50.10% |
| screenshot-2.png | 76.53KB | 28.93KB | ▼ 62.20% |