Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
Installer ran successfully
Server metrics [RAM: ▲0.05MB] [CPU: ▼5.45ms] Passed 4 tests
Server-side resources used by PlayerJS
Normal server usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.50 ▲0.04 | 40.56 ▲0.57 |
Dashboard /wp-admin | 3.37 ▲0.02 | 47.21 ▼14.01 |
Posts /wp-admin/edit.php | 3.42 ▲0.06 | 48.76 ▲1.87 |
Add New Post /wp-admin/post-new.php | 5.95 ▲0.06 | 82.26 ▼10.23 |
Media Library /wp-admin/upload.php | 3.29 ▲0.06 | 36.25 ▲2.23 |
PlayerJS /wp-admin/options-general.php?page=playerjs_com_admin | 3.26 | 34.19 |
Server storage [IO: ▲0.64MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
This plugin was installed successfully
Filesystem: 8 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_recent-posts |
widget_theysaidso_widget |
theysaidso_admin_options |
db_upgraded |
can_compress_scripts |
widget_recent-comments |
Browser metrics Passed 4 tests
PlayerJS: an overview of browser usage
This plugin renders optimally with no browser resource issues detected
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,796 ▲46 | 16.50 ▲2.22 | 49.04 ▲47.29 | 39.69 ▼0.28 |
Dashboard /wp-admin | 2,199 ▲18 | 5.61 ▼0.10 | 89.27 ▼7.01 | 38.38 ▼5.12 |
Posts /wp-admin/edit.php | 2,104 ▲4 | 2.08 ▲0.07 | 39.33 ▲5.85 | 35.80 ▲0.40 |
Add New Post /wp-admin/post-new.php | 1,540 ▲14 | 18.22 ▼4.95 | 613.39 ▼83.38 | 70.46 ▲6.97 |
Media Library /wp-admin/upload.php | 1,398 ▼2 | 4.14 ▼0.04 | 93.04 ▼3.98 | 41.55 ▼6.01 |
PlayerJS /wp-admin/options-general.php?page=playerjs_com_admin | 874 | 1.99 | 24.49 | 38.97 |
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
It is recommended to fix the following
- The uninstall procedure has failed, leaving 6 options in the database
- can_compress_scripts
- widget_recent-comments
- db_upgraded
- widget_recent-posts
- theysaidso_admin_options
- widget_theysaidso_widget
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
Everything seems fine, however 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
Almost there! Just fix the following items
- 1× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/playerjs/admin/playerjs_com_admin.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)
There were no browser issues found
Optimizations
Plugin configuration Passed 29 tests
readme.txt Passed 16 tests
Perhaps the most important file in your plugin readme.txt gets parsed in order to generate the public listing of your plugin
8 plugin tags: vimeo player, video player, playerjs, hls player, youtube player...
playerjs/playerjs.php Passed 13 tests
The main PHP file in "PlayerJS" ver. 2.23 adds more information about the plugin and also serves as the entry point for this plugin
100 characters long description:
Embed your created player in PlayerJS Builder and play HTML5 Video, Audio, HLS, DASH, YouTube, Vimeo
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
Good job! No executable or dangerous file extensions detected428 lines of code in 5 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 2 | 69 | 18 | 251 |
JavaScript | 2 | 27 | 6 | 131 |
CSS | 1 | 3 | 0 | 46 |
PHP code Passed 2 tests
A brief analysis of cyclomatic complexity and code structure for this plugin
No complexity issues detected
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.55 |
Average class complexity | 3.00 |
▷ Minimum class complexity | 3.00 |
▷ Maximum class complexity | 3.00 |
Average method complexity | 1.67 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 3.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 | 3 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 3 | 100.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 13 | |
▷ Named functions | 13 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 1 | |
▷ Global constants | 1 | 100.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.01MB with 0.00MB in potential savings
Potential savings
Compression of 2 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
admin/playerjs.png | 7.19KB | 6.11KB | ▼ 14.99% |
admin/x.png | 1.23KB | 0.34KB | ▼ 72.45% |