Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices
Installer ran successfully
Server metrics [RAM: ▲0.04MB] [CPU: ▼3.99ms] Passed 4 tests
A check of server-side resources used by EZPlayer
This plugin has minimal impact on server resources
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.51 ▲0.05 | 38.42 ▼7.67 |
Dashboard /wp-admin | 3.35 ▲0.01 | 46.60 ▼13.89 |
Posts /wp-admin/edit.php | 3.46 ▲0.11 | 47.75 ▲4.16 |
Add New Post /wp-admin/post-new.php | 5.95 ▲0.07 | 89.18 ▲7.38 |
Media Library /wp-admin/upload.php | 3.27 ▲0.05 | 33.99 ▲1.45 |
Server storage [IO: ▲0.06MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
This plugin installed successfully
Filesystem: 16 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_recent-comments |
db_upgraded |
widget_theysaidso_widget |
widget_recent-posts |
theysaidso_admin_options |
can_compress_scripts |
Browser metrics Passed 4 tests
A check of browser resources used by EZPlayer
This plugin has a minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,807 ▲36 | 13.27 ▼1.10 | 1.60 ▼0.40 | 40.86 ▼1.16 |
Dashboard /wp-admin | 2,210 ▲24 | 4.84 ▼0.09 | 99.93 ▼25.40 | 39.64 ▼8.00 |
Posts /wp-admin/edit.php | 2,096 ▲4 | 2.01 ▼0.02 | 42.96 ▲7.96 | 34.07 ▲2.69 |
Add New Post /wp-admin/post-new.php | 1,521 ▼12 | 17.61 ▼5.59 | 602.52 ▼78.05 | 57.05 ▲4.21 |
Media Library /wp-admin/upload.php | 1,398 ▲7 | 4.17 ▼0.04 | 96.64 ▲0.95 | 43.13 ▲0.58 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
You still need to fix the following
- Zombie WordPress options were found after uninstall: 6 options
- widget_recent-comments
- db_upgraded
- widget_theysaidso_widget
- theysaidso_admin_options
- widget_recent-posts
- can_compress_scripts
Smoke tests 50% 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 0% 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
Please take a closer look at the following
- 2× PHP files perform the action of outputting non-empty strings when accessed directly:
- > /wp-content/plugins/ezplayer/assets/frontend/views/js.php
- > /wp-content/plugins/ezplayer/assets/frontend/views/wrapper.php
- 4× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/ezplayer/ezplayer.php:14
- > PHP Fatal error
Uncaught Error: Class 'ET_Builder_Module' not found in wp-content/plugins/ezplayer/include/builders/divi.php:2
- > PHP Notice
Trying to access array offset on value of type null in wp-content/plugins/ezplayer/assets/frontend/views/wrapper.php on line 3
- > PHP Notice
Undefined variable: atts in wp-content/plugins/ezplayer/assets/frontend/views/wrapper.php on line 3
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
No browser errors were detected
Optimizations
Plugin configuration 96% from 29 tests
readme.txt Passed 16 tests
The readme.txt file is an important file in your plugin as it is parsed by WordPress.org to prepare the public listing of your plugin
3 plugin tags: video player, ezplayer, player
ezplayer/ezplayer.php 92% from 13 tests
"EZPlayer" version 1.0.10's primary PHP file adds more information about the plugin and serves as the entry point for WordPress
Please make the necessary changes and fix the following:
- Text Domain: You no longer need to specify the text domain since WordPress 4.6; it must be the same as the plugin slug
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
There were no executable files found in this plugin296 lines of code in 11 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 7 | 54 | 166 | 246 |
JavaScript | 1 | 2 | 0 | 26 |
PO File | 1 | 6 | 11 | 19 |
CSS | 1 | 0 | 0 | 3 |
Markdown | 1 | 2 | 0 | 2 |
PHP code Passed 2 tests
This plugin's cyclomatic complexity and code structure detailed below
All good! No complexity issues found
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.18 |
Average class complexity | 4.40 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 8.00 |
Average method complexity | 1.71 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 6.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 5 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 5 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 20 | |
▷ Static methods | 11 | 55.00% |
▷ Public methods | 14 | 70.00% |
▷ Protected methods | 1 | 5.00% |
▷ Private methods | 5 | 25.00% |
Functions | 4 | |
▷ Named functions | 0 | 0.00% |
▷ Anonymous functions | 4 | 100.00% |
Constants | 1 | |
▷ Global constants | 0 | 0.00% |
▷ Class constants | 1 | 100.00% |
▷ Public constants | 1 | 100.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.04MB with 0.04MB in potential savings
Potential savings
Compression of 2 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
assets/dashboard/images/vc.png | 21.49KB | 1.20KB | ▼ 94.43% |
assets/dashboard/images/tinymce.png | 21.85KB | 1.04KB | ▼ 95.23% |