Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
This plugin's installer ran successfully
Server metrics [RAM: ▲0.44MB] [CPU: ▼9.19ms] Passed 4 tests
This is a short check of server-side resources used by Search for Spotify
This plugin does not affect your website's performance
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.91 ▲0.45 | 40.88 ▼2.44 |
| Dashboard /wp-admin | 3.75 ▲0.41 | 52.17 ▼14.82 |
| Posts /wp-admin/edit.php | 3.87 ▲0.51 | 47.84 ▼8.51 |
| Add New Post /wp-admin/post-new.php | 6.33 ▲0.45 | 87.64 ▼11.00 |
| Media Library /wp-admin/upload.php | 3.68 ▲0.45 | 41.86 ▲5.80 |
| Spotify Search /wp-admin/options-general.php?page=kirilkirkov-spotify-search-settings | 3.74 | 34.30 |
Server storage [IO: ▲1.88MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
This plugin installed successfully
Filesystem: 196 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| can_compress_scripts |
| widget_recent-posts |
| theysaidso_admin_options |
| widget_theysaidso_widget |
| widget_recent-comments |
| db_upgraded |
Browser metrics Passed 4 tests
Search for Spotify: 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,879 ▲133 | 13.80 ▼0.53 | 8.99 ▲7.27 | 40.33 ▼2.16 |
| Dashboard /wp-admin | 2,202 ▲25 | 5.61 ▲0.09 | 89.80 ▼16.98 | 39.26 ▼4.36 |
| Posts /wp-admin/edit.php | 2,101 ▲1 | 2.02 ▲0.06 | 35.16 ▼5.36 | 33.66 ▼2.60 |
| Add New Post /wp-admin/post-new.php | 1,538 ▲1 | 18.34 ▲0.39 | 633.41 ▲16.13 | 69.21 ▼6.19 |
| Media Library /wp-admin/upload.php | 1,407 ▲4 | 4.20 ▼0.03 | 96.77 ▼0.99 | 42.58 ▼5.40 |
| Spotify Search /wp-admin/options-general.php?page=kirilkirkov-spotify-search-settings | 980 | 2.03 | 25.69 | 40.36 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
Please fix the following items
- The uninstall procedure has failed, leaving 6 options in the database
- widget_recent-comments
- can_compress_scripts
- widget_theysaidso_widget
- theysaidso_admin_options
- widget_recent-posts
- 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 | 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
Almost there! Just fix the following items
- 49× PHP files trigger server-side errors or warnings when accessed directly (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_html_e() in wp-content/plugins/kirilkirkov-spotify-search/Includes/Admin/SettingsForm.php:10
- > PHP Fatal error
Uncaught Error: Interface 'Psr\\Http\\Message\\UploadedFileInterface' not found in wp-content/plugins/kirilkirkov-spotify-search/vendor/guzzlehttp/psr7/src/UploadedFile.php:10
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_attr_e() in wp-content/plugins/kirilkirkov-spotify-search/Includes/Public/PublicSearchForm.php:4
- > PHP Parse error
syntax error, unexpected '|', expecting '{' in wp-content/plugins/kirilkirkov-spotify-search/vendor/symfony/polyfill-intl-normalizer/bootstrap80.php on line 18
- > PHP Fatal error
Uncaught Error: Interface 'GuzzleHttp\\Cookie\\CookieJarInterface' not found in wp-content/plugins/kirilkirkov-spotify-search/vendor/guzzlehttp/guzzle/src/Cookie/CookieJar.php:10
- > PHP Fatal error
Uncaught Error: Class 'GuzzleHttp\\Cookie\\CookieJar' not found in wp-content/plugins/kirilkirkov-spotify-search/vendor/guzzlehttp/guzzle/src/Cookie/FileCookieJar.php:7
- > PHP Fatal error
Uncaught Error: Interface 'Psr\\Http\\Message\\MessageInterface' not found in wp-content/plugins/kirilkirkov-spotify-search/vendor/psr/http-message/src/ResponseInterface.php:20
- > PHP Fatal error
Uncaught Error: Interface 'Psr\\Http\\Message\\StreamInterface' not found in wp-content/plugins/kirilkirkov-spotify-search/vendor/guzzlehttp/psr7/src/LimitStream.php:12
- > PHP Fatal error
Uncaught Error: Interface 'Psr\\Http\\Message\\StreamInterface' not found in wp-content/plugins/kirilkirkov-spotify-search/vendor/guzzlehttp/psr7/src/BufferStream.php:17
- > PHP Fatal error
Uncaught Error: Interface 'Psr\\Http\\Message\\RequestInterface' not found in wp-content/plugins/kirilkirkov-spotify-search/vendor/guzzlehttp/psr7/src/Request.php:13
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
Everything seems fine on the user side
Optimizations
Plugin configuration 96% from 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
4 plugin tags: spotify, spotify shortcode, spotify search, spotify widget
kirilkirkov-spotify-search/KirilKirkovSpotifySearch.php 92% from 13 tests
Analyzing the main PHP file in "Search for Spotify" version 1.3
Please make the necessary changes and fix the following:
- Main file name: The principal plugin file should be the same as the plugin slug ("kirilkirkov-spotify-search.php" instead of "KirilKirkovSpotifySearch.php")
Code Analysis 97% from 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 plugin33,924 lines of code in 181 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 147 | 2,480 | 6,483 | 28,610 |
| Markdown | 13 | 1,127 | 0 | 3,408 |
| JSON | 9 | 0 | 0 | 959 |
| CSS | 3 | 85 | 14 | 490 |
| JavaScript | 2 | 29 | 24 | 347 |
| YAML | 5 | 22 | 3 | 91 |
| Dockerfile | 1 | 8 | 0 | 10 |
| make | 1 | 4 | 0 | 9 |
PHP code 50% from 2 tests
This plugin's cyclomatic complexity and code structure detailed below
It is recommended to fix the following
- Please reduce cyclomatic complexity of methods to less than 100 (currently 179)
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.47 |
| Average class complexity | 15.42 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 179.00 |
| Average method complexity | 2.98 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 179.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 16 | |
| Interfaces | 15 | |
| Traits | 2 | |
| Classes | 99 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 99 | 100.00% |
| ▷ Final classes | 23 | 23.23% |
| Methods | 875 | |
| ▷ Static methods | 230 | 26.29% |
| ▷ Public methods | 709 | 81.03% |
| ▷ Protected methods | 4 | 0.46% |
| ▷ Private methods | 162 | 18.51% |
| Functions | 164 | |
| ▷ Named functions | 74 | 45.12% |
| ▷ Anonymous functions | 90 | 54.88% |
| Constants | 258 | |
| ▷ Global constants | 76 | 29.46% |
| ▷ Class constants | 182 | 70.54% |
| ▷ Public constants | 182 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
Often times overlooked, PNG files can occupy unnecessary space in your plugin
2 PNG files occupy 0.05MB with 0.03MB in potential savings
Potential savings
| Compression of 2 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| Includes/Admin/Assets/Img/274x300.png | 50.52KB | 15.76KB | ▼ 68.80% |
| Includes/Admin/GitHub-Mark-64px.png | 2.56KB | 1.51KB | ▼ 41.07% |