Benchmarks
Plugin footprint 58% from 16 tests
Installer 0% from 1 test
🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices
It is recommended to fix the following installer errors
- The plugin did not install without errors
- > Parse error in wp-content/plugins/recent-tracks-lastfm/lastfm-recenttracks.php+87
syntax error, unexpected end of file
Server metrics [RAM: ▲0.00MB] [CPU: ▼3.49ms] Passed 4 tests
Server-side resources used by Last.FM Recent Tracks - Wordpress Plugin
No issues were detected with server-side resource usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.46 ▲0.00 | 38.29 ▲2.26 |
| Dashboard /wp-admin | 3.31 ▲0.00 | 56.75 ▲6.56 |
| Posts /wp-admin/edit.php | 3.36 ▲0.00 | 40.13 ▼10.53 |
| Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 86.33 ▼12.24 |
| Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 43.95 ▲9.56 |
Server storage [IO: ▲0.07MB] [DB: ▲0.07MB] Passed 3 tests
Filesystem and database footprint
The plugin installed successfully
Filesystem: 5 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_recent-comments |
| db_upgraded |
| widget_theysaidso_widget |
| can_compress_scripts |
| widget_recent-posts |
| theysaidso_admin_options |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Last.FM Recent Tracks - Wordpress Plugin
This plugin renders optimally with no browser resource issues detected
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,825 ▲90 | 14.48 ▼0.15 | 2.20 ▲0.64 | 43.98 ▲5.16 |
| Dashboard /wp-admin | 2,206 ▲17 | 5.79 ▲0.86 | 95.69 ▼22.90 | 40.90 ▼0.94 |
| Posts /wp-admin/edit.php | 2,086 ▼3 | 2.05 ▲0.02 | 34.00 ▼7.49 | 34.20 ▼1.15 |
| Add New Post /wp-admin/post-new.php | 1,533 ▲4 | 23.47 ▲5.23 | 657.93 ▲34.68 | 62.07 ▲9.04 |
| Media Library /wp-admin/upload.php | 1,385 ▼0 | 4.24 ▼0.03 | 100.00 ▲1.32 | 44.24 ▲1.58 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.07MB] 75% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
It is recommended to fix the following
- Zombie WordPress options detected upon uninstall: 6 options
- db_upgraded
- can_compress_scripts
- theysaidso_admin_options
- widget_theysaidso_widget
- widget_recent-posts
- widget_recent-comments
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
Even though everything seems fine, this is not an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle: PHP files have to remain inert when accessed directly, throwing no errors and performing no actions
Please fix the following items
- 1× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Parse error
syntax error, unexpected end of file in wp-content/plugins/recent-tracks-lastfm/lastfm-recenttracks.php on line 87
- > PHP Parse error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
There were no browser issues found
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file uses markdown syntax to describe your plugin to the world
These attributes need to be fixed:
- Screenshots: These screenshots do not have images: #1 (The plugin on a post or page.), #2 (The options page for the plugin.)
recent-tracks-lastfm/lastfm-recenttracks.php 92% from 13 tests
The main PHP script in "Last.FM Recent Tracks - Wordpress Plugin" version 1.1 is automatically included on every request by WordPress
The following require your attention:
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("recent-tracks-lastfm.php" instead of "lastfm-recenttracks.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | An overview of files in this plugin; executable files are not allowed
Everything looks great! No dangerous files found in this plugin102 lines of code in 2 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 1 | 9 | 9 | 69 |
| CSS | 1 | 0 | 0 | 33 |
PHP code Passed 2 tests
This is a short overview of cyclomatic complexity and code structure for this plugin
This plugin has no cyclomatic complexity problems
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.15 |
| 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 | 6 | |
| ▷ Named functions | 0 | 0.00% |
| ▷ Anonymous functions | 6 | 100.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
Using a strong compression for your PNG files is a great way to speed-up your plugin
2 PNG files occupy 0.07MB with 0.05MB in potential savings
Potential savings
| Compression of 2 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| screenshot-1.png | 21.33KB | 4.39KB | ▼ 79.42% |
| screenshot-2.png | 46.58KB | 15.20KB | ▼ 67.37% |