Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.01MB] [CPU: ▼3.75ms] Passed 4 tests
Analyzing server-side resources used by WP Mp3 Player
This plugin does not affect your website's performance
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.47 ▲0.02 | 40.01 ▼2.18 |
Dashboard /wp-admin | 3.31 ▲0.01 | 48.80 ▲0.64 |
Posts /wp-admin/edit.php | 3.37 ▲0.01 | 43.33 ▼4.35 |
Add New Post /wp-admin/post-new.php | 5.90 ▲0.01 | 86.66 ▼7.89 |
Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 35.32 ▼0.58 |
Server storage [IO: ▲0.25MB] [DB: ▲0.07MB] Passed 3 tests
Filesystem and database footprint
This plugin was installed successfully
Filesystem: 14 new files
Database: no new tables, 7 new options
New WordPress options |
---|
can_compress_scripts |
widget_recent-comments |
db_upgraded |
theysaidso_admin_options |
widget_recent-posts |
widget_wp_mp3_widget |
widget_theysaidso_widget |
Browser metrics Passed 4 tests
A check of browser resources used by WP Mp3 Player
There were no issues detected in relation to browser resource usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,912 ▲177 | 13.65 ▼0.76 | 13.55 ▲11.54 | 43.52 ▼3.42 |
Dashboard /wp-admin | 2,206 ▲15 | 5.91 ▲0.03 | 127.54 ▲27.54 | 41.91 ▼2.53 |
Posts /wp-admin/edit.php | 2,089 ▼0 | 1.97 ▼0.03 | 34.83 ▼0.59 | 35.21 ▼2.89 |
Add New Post /wp-admin/post-new.php | 1,535 ▲21 | 23.39 ▲5.88 | 676.23 ▼7.21 | 53.90 ▼3.41 |
Media Library /wp-admin/upload.php | 1,388 ▲3 | 4.18 ▼0.05 | 94.95 ▼11.17 | 39.43 ▼9.35 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.07MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
It is recommended to fix the following
- The uninstall procedure has failed, leaving 7 options in the database
- widget_recent-comments
- widget_wp_mp3_widget
- widget_recent-posts
- can_compress_scripts
- theysaidso_admin_options
- widget_theysaidso_widget
- db_upgraded
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
The smoke test was a success, however most plugin functionality was not tested
SRP 50% from 2 tests
🔹 Tests weight: 20 | A shallow check of the single-responsibility principle; PHP files should perform no action - including output of placeholder text - and trigger no errors when accessed directly
The following issues need your attention
- 1× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Fatal error
Uncaught Error: Class 'WP_Widget' not found in wp-content/plugins/wp-mp3-player/wp-mp3-plugin.php:12
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
Everything seems fine on the user side
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 88% from 16 tests
The readme.txt file describes your plugin functionality and requirements and it is parsed to prepare the your plugin's listing
These attributes need your attention:
- Screenshots: Add descriptions for screenshots #2, #3 in wp-mp3-player/assets to your readme.txt
- Plugin Name: "Plugin Name" should be replaced with the name of your plugin on the first line (
=== wp-mp3-player ===
)
wp-mp3-player/wp-mp3-plugin.php 92% from 13 tests
The main PHP file in "WP Mp3 Player" ver. 1.01 adds more information about the plugin and also serves as the entry point for this plugin
The following require your attention:
- Main file name: It is recommended to name the main PHP file as the plugin slug ("wp-mp3-player.php" instead of "wp-mp3-plugin.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short glimpse at programming languages used with this plugin and a check that no dangerous files are present
There were no executable files found in this plugin705 lines of code in 7 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
SVG | 1 | 0 | 0 | 288 |
CSS | 2 | 17 | 8 | 155 |
PHP | 1 | 27 | 26 | 154 |
JavaScript | 3 | 18 | 7 | 108 |
PHP code Passed 2 tests
A brief analysis of cyclomatic complexity and code structure for this plugin
No cyclomatic complexity issues were detected for this plugin
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.21 |
Average class complexity | 18.00 |
▷ Minimum class complexity | 18.00 |
▷ Maximum class complexity | 18.00 |
Average method complexity | 5.25 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 8.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 | 4 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 4 | 100.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 3 | |
▷ Named functions | 3 | 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
No PNG images were found in this plugin