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.02MB] [CPU: ▼2.95ms] Passed 4 tests
An overview of server-side resources used by Wavesurfer Audio Player block
No issues were detected with server-side resource usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.49 ▲0.03 | 38.26 ▼1.86 |
| Dashboard /wp-admin | 3.33 ▲0.03 | 43.18 ▼10.36 |
| Posts /wp-admin/edit.php | 3.38 ▲0.02 | 45.94 ▲0.47 |
| Add New Post /wp-admin/post-new.php | 5.91 ▲0.02 | 93.51 ▲1.70 |
| Media Library /wp-admin/upload.php | 3.25 ▲0.02 | 35.45 ▼0.04 |
Server storage [IO: ▲0.73MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
There were no storage issued detected upon installing this plugin
Filesystem: 63 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_recent-comments |
| widget_theysaidso_widget |
| theysaidso_admin_options |
| widget_recent-posts |
| can_compress_scripts |
| db_upgraded |
Browser metrics Passed 4 tests
A check of browser resources used by Wavesurfer Audio Player block
Normal browser usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,811 ▲76 | 13.71 ▼0.67 | 7.72 ▲5.79 | 39.73 ▼9.18 |
| Dashboard /wp-admin | 2,203 ▲15 | 5.83 ▼0.07 | 99.80 ▼11.47 | 38.64 ▼13.52 |
| Posts /wp-admin/edit.php | 2,089 ▲3 | 2.03 ▼0.07 | 37.18 ▼1.36 | 34.61 ▲1.01 |
| Add New Post /wp-admin/post-new.php | 6,424 ▲4,905 | 20.97 ▼2.11 | 898.71 ▲221.87 | 37.71 ▼10.44 |
| Media Library /wp-admin/upload.php | 1,388 ▲3 | 4.18 ▼0.04 | 96.59 ▼12.77 | 40.59 ▼7.10 |
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
These items require your attention
- This plugin does not fully uninstall, leaving 6 options in the database
- can_compress_scripts
- db_upgraded
- 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
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
Please fix the following items
- 2× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Fatal error
Uncaught Error: Call to undefined function WavesurferAudioPlayer\\add_action() in wp-content/plugins/wavesurfer-audio-player-block/lib/meta-boxes.php:5
- > PHP Fatal error
Uncaught Error: Call to undefined function WavesurferAudioPlayer\\add_action() in wp-content/plugins/wavesurfer-audio-player-block/lib/enqueue-scripts.php:5
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 93% 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
1 plugin tags: block
wavesurfer-audio-player-block/ws-audio-player.php 85% from 13 tests
The principal PHP file in "Wavesurfer Audio Player block" v. 1.0 is loaded by WordPress automatically on each request
You should first fix the following items:
- Text Domain: The text domain must be the same as the plugin slug, although optional since WordPress version 4.6
- Main file name: It is recommended to name the main PHP file as the plugin slug ("wavesurfer-audio-player-block.php" instead of "ws-audio-player.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
Good job! No executable or dangerous file extensions detected2,376 lines of code in 58 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| TypeScript | 5 | 111 | 169 | 1,054 |
| JavaScript | 39 | 52 | 185 | 799 |
| JSON | 3 | 0 | 0 | 142 |
| CSS | 3 | 5 | 2 | 117 |
| PHP | 4 | 26 | 59 | 108 |
| SVG | 1 | 0 | 1 | 76 |
| PO File | 1 | 5 | 5 | 36 |
| Markdown | 1 | 10 | 0 | 23 |
| Sass | 1 | 6 | 0 | 21 |
PHP code Passed 2 tests
An overview of cyclomatic complexity and code structure
This plugin has no cyclomatic complexity issues
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.13 |
| 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 | 1 | |
| 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 | 7 | |
| ▷ Named functions | 7 | 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 files were detected