Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
This plugin's installer ran successfully
Server metrics [RAM: ▲0.05MB] [CPU: ▼7.75ms] Passed 4 tests
This is a short check of server-side resources used by CWidget Countdown
This plugin does not affect your website's performance
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.51 ▲0.05 | 39.29 ▼4.39 |
Dashboard /wp-admin | 3.35 ▲0.05 | 46.31 ▼2.29 |
Posts /wp-admin/edit.php | 3.40 ▲0.05 | 43.83 ▼7.61 |
Add New Post /wp-admin/post-new.php | 5.93 ▲0.05 | 83.15 ▼16.69 |
Media Library /wp-admin/upload.php | 3.28 ▲0.05 | 36.25 ▲2.63 |
Server storage [IO: ▲0.08MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
There were no storage issued detected upon installing this plugin
Filesystem: 65 new files
Database: no new tables, 7 new options
New WordPress options |
---|
can_compress_scripts |
widget_theysaidso_widget |
theysaidso_admin_options |
widget_recent-posts |
widget_cwidget_countdown |
db_upgraded |
widget_recent-comments |
Browser metrics Passed 4 tests
An overview of browser requirements for CWidget Countdown
There were no issues detected in relation to browser resource usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,908 ▲173 | 13.77 ▼0.41 | 6.93 ▲4.84 | 42.28 ▼6.90 |
Dashboard /wp-admin | 2,209 ▲21 | 4.85 ▼0.07 | 112.56 ▲7.18 | 41.98 ▼2.75 |
Posts /wp-admin/edit.php | 2,089 ▼0 | 2.05 ▲0.03 | 33.87 ▼7.45 | 34.56 ▼0.59 |
Add New Post /wp-admin/post-new.php | 1,533 ▲19 | 23.58 ▲6.05 | 675.97 ▲2.29 | 61.54 ▲9.40 |
Media Library /wp-admin/upload.php | 1,391 ▲3 | 4.20 ▲0.01 | 98.15 ▼8.56 | 43.24 ▲0.04 |
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
Please fix the following items
- Zombie WordPress options detected upon uninstall: 7 options
- theysaidso_admin_options
- widget_recent-comments
- widget_recent-posts
- widget_theysaidso_widget
- can_compress_scripts
- db_upgraded
- widget_cwidget_countdown
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
Everything seems fine, however this is by no means an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | It is important to ensure that your PHP files perform no action when accessed directly, respecting the single-responsibility principle
The following issues need your attention
- 1× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Fatal error
Uncaught Error: Class 'WP_Widget' not found in wp-content/plugins/cwidget-countdown/cwidget.php:14
- > 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 93% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file is important because it is parsed by WordPress.org for the public listing of your plugin
Attributes that require attention:
- Screenshots: Add images for these screenshots: #1 (The Widget), #2 (The Countdown!)
cwidget-countdown/cwidget.php 92% from 13 tests
Analyzing the main PHP file in "CWidget Countdown" version 2.0
Please take the time to fix the following:
- Main file name: It is recommended to name the main PHP file as the plugin slug ("cwidget-countdown.php" instead of "cwidget.php")
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
Success! There were no dangerous files found in this plugin857 lines of code in 56 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
JavaScript | 50 | 0 | 152 | 517 |
PHP | 1 | 18 | 23 | 166 |
PO File | 4 | 44 | 44 | 149 |
CSS | 1 | 4 | 1 | 25 |
PHP code Passed 2 tests
A short review of cyclomatic complexity and code structure
Everything seems fine, there were no complexity issues found
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.17 |
Average class complexity | 16.00 |
▷ Minimum class complexity | 16.00 |
▷ Maximum class complexity | 16.00 |
Average method complexity | 3.50 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 12.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 | 6 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 6 | 100.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 1 | |
▷ Named functions | 1 | 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
Often times overlooked, PNG files can occupy unnecessary space in your plugin
2 PNG files occupy 0.01MB with 0.01MB in potential savings
Potential savings
Compression of 2 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
screenshot-1.png | 12.38KB | 5.87KB | ▼ 52.56% |
screenshot-2.png | 2.26KB | 1.20KB | ▼ 47.15% |