Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | All plugins must install correctly, without throwing any errors, warnings, or notices
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.04MB] [CPU: ▼3.52ms] Passed 4 tests
A check of server-side resources used by Countdown Timer block - Display the event's date into a timer.
This plugin does not affect your website's performance
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.51 ▲0.05 | 39.74 ▼2.16 |
| Dashboard /wp-admin | 3.34 ▲0.04 | 47.03 ▼9.59 |
| Posts /wp-admin/edit.php | 3.39 ▲0.04 | 49.48 ▲2.17 |
| Add New Post /wp-admin/post-new.php | 5.93 ▲0.04 | 89.78 ▼3.18 |
| Media Library /wp-admin/upload.php | 3.27 ▲0.03 | 36.32 ▲0.84 |
Server storage [IO: ▲0.61MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
This plugin installed successfully
Filesystem: 18 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_theysaidso_widget |
| widget_recent-comments |
| can_compress_scripts |
| theysaidso_admin_options |
| db_upgraded |
| widget_recent-posts |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Countdown Timer block - Display the event's date into a timer.
This plugin renders optimally with no browser resource issues detected
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,814 ▲28 | 14.20 ▼0.37 | 2.06 ▲0.29 | 41.54 ▼2.43 |
| Dashboard /wp-admin | 2,198 ▲18 | 5.64 ▼0.01 | 86.04 ▼13.84 | 38.44 ▼5.54 |
| Posts /wp-admin/edit.php | 2,100 ▼0 | 2.03 ▲0.01 | 35.84 ▲1.09 | 34.34 ▼1.38 |
| Add New Post /wp-admin/post-new.php | 6,369 ▲4,843 | 28.04 ▲5.07 | 891.88 ▲209.09 | 53.84 ▲2.35 |
| Media Library /wp-admin/upload.php | 1,394 ▼6 | 4.19 ▼0.04 | 97.35 ▼19.18 | 43.07 ▼6.18 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
It is recommended to fix the following
- Zombie WordPress options detected upon uninstall: 6 options
- theysaidso_admin_options
- db_upgraded
- widget_recent-comments
- widget_theysaidso_widget
- widget_recent-posts
- can_compress_scripts
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a short smoke test looking for server-side errors
Good news, no errors were detected
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 items
- 2× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Warning
Use of undefined constant CTB_PLUGIN_VERSION - assumed 'CTB_PLUGIN_VERSION' (this will throw an Error in a future version of PHP) in wp-content/plugins/countdown-time/dist/editor.asset.php on line 4
- > PHP Warning
Use of undefined constant CTB_PLUGIN_VERSION - assumed 'CTB_PLUGIN_VERSION' (this will throw an Error in a future version of PHP) in wp-content/plugins/countdown-time/dist/script.asset.php on line 4
- > PHP Warning
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
Everything seems fine on the user side
Optimizations
Plugin configuration 93% 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
Attributes that need to be fixed:
- Requires at least: Invalid plugin version format
countdown-time/plugin.php 92% from 13 tests
The primary PHP file in "Countdown Timer block - Display the event's date into a timer." version 1.1.7 is used by WordPress to initiate all plugin functionality
Please take the time to fix the following:
- Main file name: It is recommended to name the main PHP file as the plugin slug ("countdown-time.php" instead of "plugin.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | There should be no dangerous file extensions present in any WordPress plugin
No dangerous file extensions were detected464 lines of code in 11 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PO File | 1 | 95 | 194 | 208 |
| JSON | 2 | 0 | 0 | 196 |
| PHP | 4 | 17 | 15 | 56 |
| CSS | 2 | 0 | 2 | 2 |
| JavaScript | 2 | 0 | 2 | 2 |
PHP code Passed 2 tests
This is a very shot review of cyclomatic complexity and code structure
Although this was not an exhaustive test, there were no cyclomatic complexity issues detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.19 |
| Average class complexity | 3.00 |
| ▷ Minimum class complexity | 3.00 |
| ▷ Maximum class complexity | 3.00 |
| Average method complexity | 1.40 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 2.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 1 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 1 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 5 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 5 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 0 | |
| ▷ Named functions | 0 | 0.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 2 | |
| ▷ Global constants | 2 | 100.00% |
| ▷ Class constants | 0 | 0.00% |
| ▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
All PNG images should be compressed to minimize bandwidth usage for end users
No PNG files were detected