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
This plugin's installer ran successfully
Server metrics [RAM: ▲0.01MB] [CPU: ▼4.98ms] Passed 4 tests
Server-side resources used by Digital Clock Block
Normal server usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.47 ▲0.01 | 39.53 ▼4.44 |
Dashboard /wp-admin | 3.31 ▲0.01 | 47.69 ▼6.99 |
Posts /wp-admin/edit.php | 3.37 ▲0.01 | 48.74 ▼2.90 |
Add New Post /wp-admin/post-new.php | 5.91 ▲0.03 | 90.11 ▼5.57 |
Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 35.75 ▲3.21 |
Server storage [IO: ▲0.03MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
The plugin installed successfully
Filesystem: 16 new files
Database: no new tables, 6 new options
New WordPress options |
---|
theysaidso_admin_options |
widget_recent-posts |
db_upgraded |
widget_recent-comments |
can_compress_scripts |
widget_theysaidso_widget |
Browser metrics Passed 4 tests
An overview of browser requirements for Digital Clock Block
This plugin renders optimally with no browser resource issues detected
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,907 ▲146 | 13.38 ▼0.97 | 8.61 ▲6.71 | 41.74 ▼4.73 |
Dashboard /wp-admin | 2,198 ▲21 | 5.63 ▼0.04 | 87.25 ▼17.03 | 40.55 ▼2.94 |
Posts /wp-admin/edit.php | 2,103 ▲3 | 1.96 ▲0.00 | 36.56 ▼0.71 | 33.20 ▼3.52 |
Add New Post /wp-admin/post-new.php | 6,370 ▲4,842 | 27.66 ▲4.60 | 935.32 ▲245.67 | 39.93 ▼13.47 |
Media Library /wp-admin/upload.php | 1,400 ▼0 | 4.18 ▼0.05 | 98.55 ▼17.27 | 45.28 ▼4.05 |
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
- Zombie WordPress options were found after uninstall: 6 options
- widget_recent-posts
- can_compress_scripts
- theysaidso_admin_options
- db_upgraded
- widget_theysaidso_widget
- widget_recent-comments
Smoke tests Passed 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the server (in the Apache logs)
The smoke test was a success, however most plugin functionality was not tested
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
Everything seems fine, however this is by no means an exhaustive test
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
Perhaps the most important file in your plugin readme.txt gets parsed in order to generate the public listing of your plugin
These attributes need your attention:
- Screenshots: Add images for these screenshots: #1 (This is the first option), #2 (This is the second option), #3 (This is the third option), #4 (This is the fourth option), #5 (This is the Output)
digital-clock-block/plugin.php 92% from 13 tests
The primary PHP file in "Digital Clock Block" version 1.0.0 is used by WordPress to initiate all plugin functionality
It is important to fix the following:
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("digital-clock-block.php" instead of "plugin.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is an overview of file extensions present in this plugin and a short test that no dangerous files are bundled with this plugin
Success! There were no dangerous files found in this plugin432 lines of code in 14 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
JavaScript | 6 | 30 | 135 | 210 |
Sass | 4 | 6 | 1 | 117 |
CSS | 2 | 15 | 29 | 68 |
PHP | 2 | 13 | 49 | 37 |
PHP code Passed 2 tests
Analyzing logical lines of code, cyclomatic complexity, and other code metrics
This plugin has no cyclomatic complexity issues
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.20 |
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 | 2 | |
▷ Named functions | 2 | 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
Using a strong compression for your PNG files is a great way to speed-up your plugin
There were not PNG files found in your plugin