Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.01MB] [CPU: ▲2.38ms] Passed 4 tests
Analyzing server-side resources used by Doomsday Clock
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.48 ▲0.02 | 40.54 ▲2.49 |
| Dashboard /wp-admin | 3.32 ▲0.01 | 48.20 ▲1.74 |
| Posts /wp-admin/edit.php | 3.43 ▲0.08 | 46.80 ▲2.53 |
| Add New Post /wp-admin/post-new.php | 5.90 ▲0.01 | 85.51 ▲2.75 |
| Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 38.20 ▲3.51 |
Server storage [IO: ▲0.15MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
There were no storage issued detected upon installing this plugin
Filesystem: 86 new files
Database: no new tables, 7 new options
| New WordPress options |
|---|
| widget_wpb_widget |
| widget_recent-posts |
| widget_theysaidso_widget |
| can_compress_scripts |
| widget_recent-comments |
| theysaidso_admin_options |
| db_upgraded |
Browser metrics Passed 4 tests
Checking browser requirements for Doomsday Clock
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,828 ▲17 | 13.32 ▲0.15 | 5.59 ▲3.72 | 45.86 ▼7.49 |
| Dashboard /wp-admin | 2,209 ▼0 | 5.87 ▲0.03 | 98.01 ▼3.69 | 39.80 ▼2.53 |
| Posts /wp-admin/edit.php | 2,086 ▼0 | 2.00 ▼0.05 | 37.42 ▲1.07 | 34.95 ▲2.09 |
| Add New Post /wp-admin/post-new.php | 1,514 ▼0 | 17.60 ▲0.07 | 662.87 ▼3.12 | 66.11 ▲14.29 |
| Media Library /wp-admin/upload.php | 1,388 ▼3 | 4.23 ▲0.02 | 107.81 ▲1.23 | 49.07 ▲1.51 |
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
- The uninstall procedure has failed, leaving 7 options in the database
- widget_wpb_widget
- widget_recent-posts
- db_upgraded
- widget_recent-comments
- can_compress_scripts
- theysaidso_admin_options
- widget_theysaidso_widget
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
Even though no errors were found, this is by no means 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
- 2× PHP files trigger server errors when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/doomsday-clock/widget.php:6
- > PHP Fatal error
Uncaught Error: Call to undefined function plugin_dir_path() in wp-content/plugins/doomsday-clock/index.php:14
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
There were no browser issues found
Optimizations
Plugin configuration 96% from 29 tests
readme.txt Passed 16 tests
The readme.txt file uses markdown syntax to describe your plugin to the world
3 plugin tags: doomsday clock, doomsday, clock
doomsday-clock/index.php 92% from 13 tests
The entry point to "Doomsday Clock" version 1.0.0 is a PHP file that has certain tags in its header comment area
Please take the time to fix the following:
- Main file name: Name the main plugin file the same as the plugin slug ("doomsday-clock.php" instead of "index.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is a short overview of programming languages used in this plugin, detecting executable files
Good job! No executable or dangerous file extensions detected2,567 lines of code in 85 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 3 | 437 | 952 | 2,485 |
| SVG | 82 | 0 | 0 | 82 |
PHP code Passed 2 tests
This is a very shot review of cyclomatic complexity and code structure
This plugin has no cyclomatic complexity problems
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.53 |
| Average class complexity | 122.67 |
| ▷ Minimum class complexity | 16.00 |
| ▷ Maximum class complexity | 223.00 |
| Average method complexity | 5.15 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 62.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 3 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 3 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 88 | |
| ▷ Static methods | 1 | 1.14% |
| ▷ Public methods | 73 | 82.95% |
| ▷ Protected methods | 15 | 17.05% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 9 | |
| ▷ Named functions | 9 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 22 | |
| ▷ Global constants | 22 | 100.00% |
| ▷ Class constants | 0 | 0.00% |
| ▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
PNG files should be compressed to save space and minimize bandwidth usage
No PNG files were detected