Benchmarks
Plugin footprint 58% from 16 tests
Installer 0% from 1 test
🔺 Critical test (weight: 50) | All plugins must install correctly, without throwing any errors, warnings, or notices
It is recommended to fix the following installer errors
- Install procedure had errors
- > Warning in wp-content/plugins/vimeo-video-autoplay-automute/vvaa.php+42
Use of undefined constant vvaa - assumed 'vvaa' (this will throw an Error in a future version of PHP)
Server metrics [RAM: ▼2.51MB] [CPU: ▼351.68ms] Passed 4 tests
Server-side resources used by Vimeo Video Autoplay Automute
No issues were detected with server-side resource usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 1.86 ▼1.65 | 4.33 ▼50.45 |
| Dashboard /wp-admin | 1.88 ▼1.53 | 3.61 ▼28.97 |
| Posts /wp-admin/edit.php | 1.88 ▼1.76 | 3.59 ▼35.05 |
| Add New Post /wp-admin/post-new.php | 1.88 ▼5.12 | 4.50 ▼1,292.26 |
| Media Library /wp-admin/upload.php | 1.88 ▼1.41 | 4.07 ▼23.51 |
Server storage [IO: ▲0.38MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
No storage issues were detected
Filesystem: 5 new files
Database: no new tables, no new options
Browser metrics Passed 4 tests
A check of browser resources used by Vimeo Video Autoplay Automute
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 3,922 ▲180 | 16.38 ▲0.66 | 9.99 ▲3.11 | 2.73 ▲0.09 |
| Dashboard /wp-admin | 2,903 ▲45 | 6.14 ▼0.01 | 125.00 ▼6.01 | 164.37 ▼1.20 |
| Posts /wp-admin/edit.php | 2,699 ▲29 | 3.26 ▲0.01 | 63.45 ▼0.56 | 140.89 ▼3.41 |
| Add New Post /wp-admin/post-new.php | 1,695 ▼15 | 21.05 ▲0.29 | 429.07 ▼7.68 | 159.53 ▲9.23 |
| Media Library /wp-admin/upload.php | 1,706 ▲8 | 5.93 ▲0.45 | 142.56 ▲2.45 | 188.00 ▼11.83 |
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
The following items require your attention
- The plugin did not uninstall gracefully
- > Warning in wp-content/plugins/vimeo-video-autoplay-automute/vvaa.php+42
Use of undefined constant vvaa - assumed 'vvaa' (this will throw an Error in a future version of PHP)
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
Even though no errors were found, this is by no means an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | It is important to ensure that your PHP files perform no action when accessed directly, respecting the single-responsibility principle
The following issues need your attention
- 1× PHP files trigger server errors when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_shortcode() in wp-content/plugins/vimeo-video-autoplay-automute/vvaa.php:37
- > 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 on the user side
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 88% from 16 tests
Often overlooked, readme.txt is one of the most important files in your plugin
Attributes that require attention:
- Screenshots: These screenshots have no corresponding images in /assets: #1 (Screenshot for how to write vimeo short code into post or page.), #2 (This is the second screen shot corresponding output.)
- Tags: There are too many tags (12 tag instead of maximum 10)
vimeo-video-autoplay-automute/vvaa.php 92% from 13 tests
The entry point to "Vimeo Video Autoplay Automute" version 1.0 is a PHP file that has certain tags in its header comment area
Please take the time to fix the following:
- Main file name: Name the main plugin file the same as the plugin slug ("vimeo-video-autoplay-automute.php" instead of "vvaa.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short review of files and their extensions; it is not recommended to include executable files
Good job! No executable or dangerous file extensions detected79 lines of code in 2 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 1 | 6 | 10 | 44 |
| JavaScript | 1 | 2 | 2 | 35 |
PHP code Passed 2 tests
This is a very shot review of cyclomatic complexity and code structure
All good! No complexity issues found
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.70 |
| Average class complexity | 7.00 |
| ▷ Minimum class complexity | 7.00 |
| ▷ Maximum class complexity | 7.00 |
| Average method complexity | 7.00 |
| ▷ Minimum method complexity | 7.00 |
| ▷ Maximum method complexity | 7.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 1 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 1 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 1 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 1 | 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
All PNG images should be compressed to minimize bandwidth usage for end users
2 PNG files occupy 0.37MB with 0.26MB in potential savings
Potential savings
| Compression of 2 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| screenshot-2.png | 236.15KB | 69.04KB | ▼ 70.76% |
| screenshot-1.png | 143.07KB | 41.45KB | ▼ 71.03% |