Benchmarks
Plugin footprint 65% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▼1.90MB] [CPU: ▼49.97ms] Passed 4 tests
A check of server-side resources used by Edisound Player
This plugin does not affect your website's performance
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.49 ▲0.03 | 41.68 ▲0.08 |
| Dashboard /wp-admin | 2.05 ▼1.26 | 6.78 ▼43.03 |
| Posts /wp-admin/edit.php | 2.05 ▼1.31 | 6.71 ▼42.80 |
| Add New Post /wp-admin/post-new.php | 2.05 ▼3.84 | 6.35 ▼89.79 |
| Media Library /wp-admin/upload.php | 2.05 ▼1.18 | 5.25 ▼24.25 |
Server storage [IO: ▲0.06MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
No storage issues were detected
Filesystem: 16 new files
Database: no new tables, 7 new options
| New WordPress options |
|---|
| theysaidso_admin_options |
| widget_recent-posts |
| widget_edisoud_widget |
| db_upgraded |
| widget_recent-comments |
| widget_theysaidso_widget |
| can_compress_scripts |
Browser metrics Passed 4 tests
An overview of browser requirements for Edisound Player
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,797 ▲36 | 14.75 ▲0.39 | 1.85 ▼0.07 | 43.30 ▼2.18 |
| Dashboard /wp-admin | 2,194 ▲23 | 5.52 ▲0.01 | 98.75 ▼5.26 | 43.70 ▼0.54 |
| Posts /wp-admin/edit.php | 2,108 ▲8 | 2.00 ▲0.04 | 35.94 ▼0.82 | 31.88 ▼2.99 |
| Add New Post /wp-admin/post-new.php | 6,370 ▲4,844 | 27.71 ▲4.60 | 916.19 ▲271.77 | 39.17 ▼9.89 |
| Media Library /wp-admin/upload.php | 1,402 ▲2 | 4.19 ▲0.04 | 102.61 ▲5.41 | 72.18 ▲29.66 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 50% from 4 tests
🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
These items require your attention
- This plugin did not uninstall without warnings or errors
- > User notice in wp-includes/functions.php+5905
Function wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the edisound-player-init handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- Zombie WordPress options detected upon uninstall: 7 options
- can_compress_scripts
- widget_recent-comments
- widget_recent-posts
- widget_edisoud_widget
- widget_theysaidso_widget
- db_upgraded
- theysaidso_admin_options
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the server (in the Apache logs)
Even though no errors were found, this is by no means 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
Almost there! Just fix the following items
- 1× PHP files perform the task of outputting text when accessed with GET requests:
- > /wp-content/plugins/edisound-player/edisound.php
- 3× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function Edisound\\PlayerPlugin\\Block\\add_action() in wp-content/plugins/edisound-player/includes/block.php:20
- > PHP Fatal error
Uncaught Error: Call to undefined function Edisound\\PlayerPlugin\\ShortCode\\add_shortcode() in wp-content/plugins/edisound-player/includes/shortcode.php:7
- > PHP Fatal error
Uncaught Error: Class 'WP_Widget' not found in wp-content/plugins/edisound-player/includes/widget.php:8
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 93% from 29 tests
readme.txt Passed 16 tests
The readme.txt file is undoubtedly the most important file in your plugin, preparing it for public listing on WordPress.org
2 plugin tags: player, edisound
edisound-player/edisound.php 85% from 13 tests
Analyzing the main PHP file in "Edisound Player" version 0.1.2
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
- Main file name: It is recommended to name the main PHP file as the plugin slug ("edisound-player.php" instead of "edisound.php")
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
Success! There were no dangerous files found in this plugin230 lines of code in 11 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 5 | 41 | 46 | 119 |
| JavaScript | 2 | 7 | 5 | 43 |
| PO File | 1 | 9 | 15 | 41 |
| JSON | 3 | 0 | 0 | 27 |
PHP code Passed 2 tests
An short overview of logical lines of code, cyclomatic complexity, and other code metrics
Great job! No cyclomatic complexity issues were detected in this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.15 |
| Average class complexity | 3.00 |
| ▷ Minimum class complexity | 3.00 |
| ▷ Maximum class complexity | 3.00 |
| Average method complexity | 1.50 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 2.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 4 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 1 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 1 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 4 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 4 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 9 | |
| ▷ Named functions | 6 | 66.67% |
| ▷ Anonymous functions | 3 | 33.33% |
| Constants | 4 | |
| ▷ Global constants | 0 | 0.00% |
| ▷ Class constants | 4 | 100.00% |
| ▷ Public constants | 4 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
PNG files should be compressed to save space and minimize bandwidth usage
1 PNG file occupies 0.00MB with 0.00MB in potential savings
Potential savings
| Compression of 1 random PNG file using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/js/img/edisound.png | 2.58KB | 1.22KB | ▼ 52.57% |