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.00MB] [CPU: ▼8.79ms] Passed 4 tests
Analyzing server-side resources used by Countdown Timer for WordPress Block Editor
This plugin does not affect your website's performance
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.48 ▲0.02 | 41.25 ▼3.92 |
Dashboard /wp-admin | 3.31 ▼0.04 | 47.20 ▼17.13 |
Posts /wp-admin/edit.php | 3.36 ▲0.00 | 46.66 ▼5.36 |
Add New Post /wp-admin/post-new.php | 5.91 ▲0.03 | 87.21 ▼8.76 |
Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 39.99 ▲2.01 |
Server storage [IO: ▲0.08MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
This plugin was installed successfully
Filesystem: 16 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_theysaidso_widget |
widget_recent-posts |
widget_recent-comments |
can_compress_scripts |
theysaidso_admin_options |
db_upgraded |
Browser metrics Passed 4 tests
A check of browser resources used by Countdown Timer for WordPress Block Editor
Normal browser usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,909 ▲148 | 13.61 ▼0.77 | 10.73 ▲9.02 | 42.23 ▲0.14 |
Dashboard /wp-admin | 2,189 ▲9 | 5.58 ▼0.10 | 84.80 ▼7.44 | 38.31 ▼0.86 |
Posts /wp-admin/edit.php | 2,100 ▼0 | 1.99 ▲0.02 | 37.28 ▼5.73 | 30.00 ▼13.19 |
Add New Post /wp-admin/post-new.php | 6,375 ▲4,849 | 28.39 ▲10.69 | 862.42 ▲177.69 | 38.61 ▼19.65 |
Media Library /wp-admin/upload.php | 1,400 ▼3 | 4.24 ▲0.01 | 103.83 ▲4.97 | 45.67 ▲1.52 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
Please fix the following items
- This plugin did not uninstall successfully, leaving 6 options in the database
- theysaidso_admin_options
- widget_theysaidso_widget
- can_compress_scripts
- widget_recent-comments
- widget_recent-posts
- db_upgraded
Smoke tests Passed 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
Even though no errors were found, this is by no means an exhaustive test
SRP Passed 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
Congratulations! This plugin passed the SRP test
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
No browser errors were detected
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 94% from 16 tests
Perhaps the most important file in your plugin readme.txt gets parsed in order to generate the public listing of your plugin
Please fix the following attributes:
- Screenshots: These screenshots lack descriptions #3, #4 in countdown-timer-block/assets to your readme.txt
countdown-timer-block/countdown-timer-for-gutenberg.php 85% from 13 tests
The main PHP file in "Countdown Timer for WordPress Block Editor" ver. 1.0.5 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 ("countdown-timer-block.php" instead of "countdown-timer-for-gutenberg.php")
- Text Domain: You no longer need to specify the text domain since WordPress 4.6; it must be the same as the plugin slug
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
Everything looks great! No dangerous files found in this plugin1,504 lines of code in 12 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
JavaScript | 4 | 465 | 711 | 1,033 |
CSS | 3 | 91 | 7 | 391 |
PHP | 3 | 8 | 27 | 55 |
PO File | 1 | 0 | 0 | 14 |
Sass | 1 | 1 | 1 | 11 |
PHP code Passed 2 tests
This plugin's cyclomatic complexity and code structure detailed below
No cyclomatic complexity issues were detected for this plugin
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.10 |
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 | 3 | |
▷ Named functions | 3 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 4 | |
▷ Global constants | 4 | 100.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
1 PNG file occupies 0.01MB with 0.00MB in potential savings
Potential savings
Compression of 1 random PNG file using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
build/assets/img/clock4.png | 5.83KB | 2.86KB | ▼ 50.95% |