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.04MB] [CPU: ▼7.62ms] Passed 4 tests
Server-side resources used by Sp*tify Play Button for WordPress
This plugin does not affect your website's performance
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.51 ▲0.04 | 37.46 ▲1.62 |
| Dashboard /wp-admin | 3.35 ▲0.04 | 43.76 ▼5.07 |
| Posts /wp-admin/edit.php | 3.40 ▲0.04 | 46.87 ▼1.22 |
| Add New Post /wp-admin/post-new.php | 5.93 ▲0.04 | 79.27 ▼22.23 |
| Media Library /wp-admin/upload.php | 3.27 ▲0.04 | 33.94 ▼1.95 |
| Sp*tify Play Button settings /wp-admin/options-general.php?page=spotifyplaybutton_settings | 3.24 | 31.75 |
Server storage [IO: ▲0.02MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
This plugin installed successfully
Filesystem: 6 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_theysaidso_widget |
| widget_recent-posts |
| db_upgraded |
| widget_recent-comments |
| theysaidso_admin_options |
| can_compress_scripts |
Browser metrics Passed 4 tests
A check of browser resources used by Sp*tify Play Button for WordPress
Normal browser usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,834 ▲73 | 14.36 ▲0.09 | 1.70 ▼0.17 | 43.65 ▲3.75 |
| Dashboard /wp-admin | 2,240 ▲63 | 5.64 ▲0.05 | 84.09 ▼2.87 | 35.91 ▼8.88 |
| Posts /wp-admin/edit.php | 2,145 ▲45 | 2.00 ▼0.02 | 38.30 ▲3.52 | 37.03 ▼0.35 |
| Add New Post /wp-admin/post-new.php | 6,240 ▲4,714 | 19.03 ▼4.33 | 864.58 ▲248.77 | 36.41 ▼12.29 |
| Media Library /wp-admin/upload.php | 1,445 ▲45 | 4.23 ▲0.03 | 95.86 ▼0.26 | 41.84 ▼3.46 |
| Sp*tify Play Button settings /wp-admin/options-general.php?page=spotifyplaybutton_settings | 904 | 2.02 | 25.23 | 28.62 |
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
- This plugin does not fully uninstall, leaving 6 options in the database
- widget_recent-comments
- widget_theysaidso_widget
- widget_recent-posts
- can_compress_scripts
- theysaidso_admin_options
- db_upgraded
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 | The single-responsibility principle applies for WordPress plugins as well - please make sure your PHP files perform no actions when accessed directly
Please fix the following
- 1× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Fatal error
Uncaught Error: Call to undefined function plugin_dir_url() in wp-content/plugins/spotify-play-button-for-wordpress/sptify-play-button-for-wordpress.php:13
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
No browser issues were found
Optimizations
Plugin configuration 90% 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
6 plugin tags: spotify play button, spotify, embed, playlist, spotify play button for wordpress...
spotify-play-button-for-wordpress/sptify-play-button-for-wordpress.php 77% from 13 tests
The principal PHP file in "Sp*tify Play Button for WordPress" v. 2.10 is loaded by WordPress automatically on each request
The following require your attention:
- Description: The description should be shorter than 140 characters (currently 182 characters long)
- Text Domain: The text domain follows the same naming rules as the plugin slug: lowercase characters and dashes
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("spotify-play-button-for-wordpress.php" instead of "sptify-play-button-for-wordpress.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are not allowed as they can serve as attack vectors
Good job! No executable or dangerous file extensions detected400 lines of code in 3 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 1 | 19 | 10 | 210 |
| JavaScript | 1 | 5 | 0 | 165 |
| CSS | 1 | 0 | 0 | 25 |
PHP code Passed 2 tests
An overview of cyclomatic complexity and code structure
This plugin has no cyclomatic complexity problems
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.30 |
| Average class complexity | 0.00 |
| ▷ Minimum class complexity | 0.00 |
| ▷ Maximum class complexity | 0.00 |
| Average method complexity | 0.00 |
| ▷ Minimum method complexity | 0.00 |
| ▷ Maximum method complexity | 0.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 0 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 0 | 0.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 0 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 0 | 0.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 10 | |
| ▷ Named functions | 10 | 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
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 |
| sptify-play-button-for-wordpress-icon.png | 3.56KB | 1.17KB | ▼ 67.28% |