Benchmarks
Plugin footprint 65% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices
This plugin's installer ran successfully
Server metrics [RAM: ▼0.96MB] [CPU: ▲2,869.54ms] 75% from 4 tests
Analyzing server-side resources used by Corona Update
The following require your attention
- Extra CPU: The extra CPU usage must be under 200.00ms (currently 2,869.54ms on /wp-admin/upload.php)
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.02 ▼0.44 | 2,870.47 ▲2,829.84 |
Dashboard /wp-admin | 3.06 ▼0.28 | 5,938.85 ▲5,872.93 |
Posts /wp-admin/edit.php | 3.06 ▼0.29 | 2,893.89 ▲2,842.84 |
Add New Post /wp-admin/post-new.php | 3.06 ▼2.83 | 2,920.52 ▲2,812.90 |
Media Library /wp-admin/upload.php | 3.06 ▼0.17 | 3,025.89 ▲2,992.59 |
Server storage [IO: ▲0.16MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
There were no storage issued detected upon installing this plugin
Filesystem: 32 new files
Database: no new tables, 7 new options
New WordPress options |
---|
widget_corona_update_widget |
widget_recent-comments |
db_upgraded |
theysaidso_admin_options |
widget_theysaidso_widget |
can_compress_scripts |
widget_recent-posts |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Corona Update
Normal browser usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 3,070 ▲324 | 15.53 ▲0.97 | 4.82 ▲3.10 | 36.85 ▼1.80 |
Dashboard /wp-admin | 2,378 ▲190 | 6.63 ▲1.76 | 122.18 ▲12.79 | 43.02 ▼1.51 |
Posts /wp-admin/edit.php | 2,287 ▲195 | 3.61 ▲1.59 | 48.23 ▲9.24 | 32.36 ▼4.39 |
Add New Post /wp-admin/post-new.php | 1,700 ▲167 | 19.97 ▼3.07 | 573.22 ▼119.12 | 31.07 ▼35.86 |
Media Library /wp-admin/upload.php | 1,423 ▲41 | 4.31 ▼0.01 | 80.59 ▼25.12 | 46.40 ▼0.69 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 50% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
You still need to fix the following
- Uninstall procedure validation failed for this plugin
- > Warning in wp-content/plugins/corona-update/inc/class-get-api-data.php+26
file_get_contents(https://corona.lmao.ninja/v2/all): failed to open stream: Redirection limit reached, aborting
- This plugin does not fully uninstall, leaving 7 options in the database
- widget_recent-comments
- db_upgraded
- widget_recent-posts
- widget_corona_update_widget
- widget_theysaidso_widget
- can_compress_scripts
- theysaidso_admin_options
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
Even though no errors were found, 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
Almost there! Just fix the following items
- 4× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Fatal error
Uncaught Error: Call to undefined function trailingslashit() in wp-content/plugins/corona-update/corona-update.php:28
- > PHP Fatal error
Uncaught Error: Class 'WP_Widget' not found in wp-content/plugins/corona-update/inc/statistic-widget.php:18
- > PHP Fatal error
Uncaught Error: Call to undefined function CoronaUpdate\\add_shortcode() in wp-content/plugins/corona-update/inc/statistic-shortcode.php:20
- > PHP Fatal error
Uncaught Error: Call to undefined function CoronaUpdate\\get_option() in wp-content/plugins/corona-update/inc/awareness-popup.php:22
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
No browser issues were found
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 88% from 16 tests
The readme.txt file is an important file in your plugin as it is parsed by WordPress.org to prepare the public listing of your plugin
Attributes that require attention:
- Screenshots: Please add an image for screenshot #4 (/assets/screenshot-4.png)
- Screenshots: These screenshots lack descriptions #10, #9 in corona-update/assets to your readme.txt
corona-update/corona-update.php 92% from 13 tests
The main file in "Corona Update" v. 1.6.0 serves as a complement to information provided in readme.txt and as the entry point to the plugin
It is important to fix the following:
- Description: The description should be shorter than 140 characters (currently 233 characters long)
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
No dangerous file extensions were detected1,898 lines of code in 29 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 24 | 557 | 291 | 1,260 |
CSS | 3 | 26 | 10 | 495 |
JavaScript | 2 | 87 | 9 | 143 |
PHP code Passed 2 tests
Cyclomatic complexity and code structure are the fingerprint of this plugin
There were no cyclomatic complexity issued detected
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.29 |
Average class complexity | 6.71 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 19.00 |
Average method complexity | 2.45 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 18.00 |
Code structure | ||
---|---|---|
Namespaces | 3 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 21 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 21 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 83 | |
▷ Static methods | 2 | 2.41% |
▷ Public methods | 50 | 60.24% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 33 | 39.76% |
Functions | 18 | |
▷ Named functions | 18 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 6 | |
▷ Global constants | 6 | 100.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
There were not PNG files found in your plugin