Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | All plugins must install correctly, without throwing any errors, warnings, or notices
This plugin's installer ran successfully
Server metrics [RAM: ▼0.67MB] [CPU: ▼21.61ms] Passed 4 tests
Analyzing server-side resources used by WP-Player
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.49 ▲0.03 | 42.21 ▲2.54 |
Dashboard /wp-admin | 3.33 ▼0.01 | 49.26 ▼15.11 |
Posts /wp-admin/edit.php | 3.38 ▲0.03 | 46.48 ▼4.34 |
Add New Post /wp-admin/post-new.php | 3.18 ▼2.71 | 38.74 ▼67.91 |
Media Library /wp-admin/upload.php | 3.25 ▲0.03 | 39.03 ▲0.93 |
Server storage [IO: ▲0.16MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
There were no storage issued detected upon installing this plugin
Filesystem: 16 new files
Database: no new tables, 6 new options
New WordPress options |
---|
db_upgraded |
theysaidso_admin_options |
widget_recent-posts |
widget_theysaidso_widget |
can_compress_scripts |
widget_recent-comments |
Browser metrics Passed 4 tests
WP-Player: an overview of browser usage
Minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,799 ▲38 | 14.29 ▼0.06 | 8.54 ▲6.69 | 42.86 ▲0.30 |
Dashboard /wp-admin | 2,192 ▲15 | 5.56 ▼0.11 | 88.20 ▼3.84 | 45.87 ▲2.40 |
Posts /wp-admin/edit.php | 2,091 ▼9 | 2.31 ▲0.31 | 47.23 ▲7.48 | 40.79 ▲3.88 |
Add New Post /wp-admin/post-new.php | 6,371 ▲4,843 | 26.15 ▲3.20 | 931.28 ▲264.66 | 135.20 ▲75.19 |
Media Library /wp-admin/upload.php | 1,405 ▲2 | 4.36 ▲0.11 | 114.47 ▼4.66 | 52.57 ▲4.24 |
WP-Player 设置 /wp-admin/player.php | 26 | 0.42 | 0.16 | 17.92 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
The following items require your attention
- Zombie WordPress options detected upon uninstall: 6 options
- widget_theysaidso_widget
- can_compress_scripts
- db_upgraded
- widget_recent-posts
- widget_recent-comments
- theysaidso_admin_options
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
Good news, no errors were detected
SRP 50% from 2 tests
🔹 Tests weight: 20 | SRP (Single-Responsibility Principle) - PHP files must act as libraries and never output text or perform any action when accessed directly in a browser
The following issues need your attention
- 2× 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/wp-player/include/metaboxes.php:4
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/wp-player/include/metaboxes.php:4
- > PHP Fatal error
User-side errors 0% from 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
Please take a look at the following user-side issues
- > GET request to /wp-admin/player.php
- > Network (severe)
wp-admin/player.php - Failed to load resource: the server responded with a status of 404 (Not Found)
Optimizations
Plugin configuration 96% from 29 tests
readme.txt Passed 16 tests
It's important to format your readme.txt file correctly as it is parsed for the public listing of your plugin
5 plugin tags: player, qq, wp-player, mp3-player, mp3
wp-player/wp-player.php 92% from 13 tests
The principal PHP file in "WP-Player" v. 2.6.1 is loaded by WordPress automatically on each request
You should first fix the following items:
- Description: Keep the plugin description shorter than 140 characters (currently 179 characters long)
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is a short overview of programming languages used in this plugin, detecting executable files
No dangerous file extensions were detected1,500 lines of code in 9 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 4 | 93 | 123 | 1,495 |
JavaScript | 3 | 4 | 34 | 3 |
CSS | 2 | 0 | 19 | 2 |
PHP code Passed 2 tests
A brief analysis of cyclomatic complexity and code structure for this plugin
All good! No complexity issues found
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.35 |
Average class complexity | 65.50 |
▷ Minimum class complexity | 34.00 |
▷ Maximum class complexity | 97.00 |
Average method complexity | 3.69 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 14.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 2 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 2 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 48 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 22 | 45.83% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 26 | 54.17% |
Functions | 9 | |
▷ Named functions | 9 | 100.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
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
4 PNG files occupy 0.01MB with 0.01MB in potential savings
Potential savings
Compression of 4 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
assets/images/default.png | 1.76KB | 0.71KB | ▼ 59.77% |
assets/images/wp_player_bg.png | 2.29KB | 1.00KB | ▼ 56.49% |
assets/images/wp_player_bg_8.png | 2.26KB | 0.86KB | ▼ 61.78% |
assets/images/wp_player_bg2x.png | 3.80KB | 2.12KB | ▼ 44.28% |