Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
This plugin's installer ran successfully
Server metrics [RAM: ▲0.01MB] [CPU: ▼6.66ms] Passed 4 tests
An overview of server-side resources used by UVC digital clock
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.47 ▲0.01 | 38.18 ▼4.72 |
| Dashboard /wp-admin | 3.31 ▲0.01 | 43.26 ▼9.80 |
| Posts /wp-admin/edit.php | 3.37 ▲0.01 | 47.00 ▲1.29 |
| Add New Post /wp-admin/post-new.php | 5.90 ▲0.01 | 85.48 ▼13.40 |
| Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 33.64 ▲1.98 |
Server storage [IO: ▲0.04MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
The plugin installed successfully
Filesystem: 7 new files
Database: no new tables, 7 new options
| New WordPress options |
|---|
| db_upgraded |
| widget_recent-posts |
| widget_uvcd_clock |
| widget_theysaidso_widget |
| widget_recent-comments |
| theysaidso_admin_options |
| can_compress_scripts |
Browser metrics Passed 4 tests
Checking browser requirements for UVC digital clock
Normal browser usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,800 ▲43 | 13.22 ▼1.58 | 1.86 ▼0.11 | 44.09 ▼2.14 |
| Dashboard /wp-admin | 2,206 ▲18 | 4.86 ▼1.02 | 111.32 ▼11.78 | 43.00 ▼4.82 |
| Posts /wp-admin/edit.php | 2,089 ▼0 | 1.99 ▼0.00 | 39.04 ▲2.46 | 33.03 ▼0.91 |
| Add New Post /wp-admin/post-new.php | 1,533 ▲14 | 23.46 ▲0.40 | 647.59 ▼37.47 | 47.03 ▼11.16 |
| Media Library /wp-admin/upload.php | 1,391 ▲3 | 4.26 ▲0.06 | 95.89 ▼13.02 | 40.13 ▼7.89 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
Please fix the following items
- Zombie WordPress options were found after uninstall: 7 options
- db_upgraded
- widget_recent-posts
- widget_theysaidso_widget
- widget_recent-comments
- widget_uvcd_clock
- theysaidso_admin_options
- can_compress_scripts
Smoke tests 75% from 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)
Good news, no errors were detected
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
Please fix the following items
- 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/uvc-digital-clock/dclock.php:9
- > PHP Fatal error
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 86% from 29 tests
readme.txt 81% 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: A description for screenshot #1 is required in uvc-digital-clock/assets to your readme.txt
- Contributors: No tags were detected
- Contributors: Plugin contributors not specified
uvc-digital-clock/dclock.php 92% from 13 tests
The main PHP script in "UVC digital clock" version 1.0 is automatically included on every request by WordPress
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 ("uvc-digital-clock.php" instead of "dclock.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
There were no executable files found in this plugin86 lines of code in 1 file:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 1 | 54 | 16 | 86 |
PHP code Passed 2 tests
An short overview of logical lines of code, cyclomatic complexity, and other code metrics
Although this was not an exhaustive test, there were no cyclomatic complexity issues detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.08 |
| Average class complexity | 2.00 |
| ▷ Minimum class complexity | 2.00 |
| ▷ Maximum class complexity | 2.00 |
| Average method complexity | 1.25 |
| ▷ 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 | 4 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 4 | 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
All PNG images should be compressed to minimize bandwidth usage for end users
4 PNG files occupy 0.01MB with 0.00MB in potential savings
Potential savings
| Compression of 4 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| 003.png | 3.15KB | 2.15KB | ▼ 31.83% |
| 001.png | 3.10KB | 2.08KB | ▼ 32.90% |
| 004.png | 3.40KB | 2.26KB | ▼ 33.60% |
| 002.png | 3.51KB | 2.31KB | ▼ 34.04% |