Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
Installer ran successfully
Server metrics [RAM: ▲0.01MB] [CPU: ▲0.37ms] Passed 4 tests
Server-side resources used by Advanced Custom Fields: oEmbed Field
Normal server usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.47 ▲0.01 | 37.74 ▲0.95 |
Dashboard /wp-admin | 3.31 ▲0.01 | 46.13 ▼1.98 |
Posts /wp-admin/edit.php | 3.36 ▲0.01 | 47.74 ▲1.93 |
Add New Post /wp-admin/post-new.php | 5.89 ▲0.01 | 91.09 ▲5.99 |
Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 33.85 ▲0.57 |
Server storage [IO: ▲0.18MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
This plugin installed successfully
Filesystem: 12 new files
Database: no new tables, 6 new options
New WordPress options |
---|
theysaidso_admin_options |
widget_theysaidso_widget |
db_upgraded |
widget_recent-comments |
widget_recent-posts |
can_compress_scripts |
Browser metrics Passed 4 tests
Advanced Custom Fields: oEmbed Field: an overview of browser usage
Normal browser usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,800 ▲65 | 14.46 ▼0.17 | 1.68 ▲0.01 | 41.06 ▼1.09 |
Dashboard /wp-admin | 2,203 ▲15 | 5.83 ▲0.95 | 98.24 ▼9.37 | 42.29 ▲2.12 |
Posts /wp-admin/edit.php | 2,086 ▼3 | 1.97 ▼0.06 | 39.02 ▲0.78 | 35.58 ▲1.33 |
Add New Post /wp-admin/post-new.php | 1,514 ▼22 | 23.65 ▲0.60 | 657.72 ▲66.58 | 61.36 ▲4.61 |
Media Library /wp-admin/upload.php | 1,382 ▼6 | 4.25 ▲0.06 | 94.88 ▼3.76 | 41.19 ▼0.19 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
These items require your attention
- Zombie WordPress options detected upon uninstall: 6 options
- widget_theysaidso_widget
- widget_recent-comments
- theysaidso_admin_options
- db_upgraded
- can_compress_scripts
- widget_recent-posts
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check 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 | A shallow check of the single-responsibility principle; PHP files should perform no action - including output of placeholder text - and trigger no errors when accessed directly
The following issues need your attention
- 3× PHP files trigger server-side errors or warnings when accessed directly:
- > 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: Class 'acf_Field' not found in wp-content/plugins/advanced-custom-fields-oembed-field/oembed-v3.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 | 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 94% from 16 tests
You should put a lot of thought into formatting readme.txt as it is used by WordPress.org to prepare the public listing of your plugin
Please fix the following attributes:
- Screenshots: Please add images for these screenshots: #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
Analyzing the main PHP file in "Advanced Custom Fields: oEmbed Field" version 1.0.3
It is important to fix the following:
- Main file name: Even though not officially enforced, the main plugin file should be 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 | This is an overview of programming languages used in this plugin; dangerous file extensions 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
A brief analysis of cyclomatic complexity and code structure for this plugin
Although this was not an exhaustive test, there were no cyclomatic complexity issues detected
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
PNG files should be compressed to save space and 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% |