Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices
Installer ran successfully
Server metrics [RAM: ▼0.01MB] [CPU: ▼6.43ms] Passed 4 tests
This is a short check of server-side resources used by Worpress Clock
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.47 ▲0.00 | 42.08 ▼1.63 |
| Dashboard /wp-admin | 3.31 ▼0.04 | 48.93 ▼14.31 |
| Posts /wp-admin/edit.php | 3.36 ▲0.00 | 46.63 ▼5.06 |
| Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 95.67 ▼4.72 |
| Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 37.66 ▲2.38 |
Server storage [IO: ▲0.01MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
This plugin installed successfully
Filesystem: 4 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| db_upgraded |
| theysaidso_admin_options |
| widget_theysaidso_widget |
| can_compress_scripts |
| widget_recent-comments |
| widget_recent-posts |
Browser metrics Passed 4 tests
Checking browser requirements for Worpress Clock
Normal browser usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,800 ▲54 | 13.72 ▼0.65 | 1.70 ▼0.27 | 40.92 ▼2.12 |
| Dashboard /wp-admin | 2,206 ▲15 | 4.83 ▼1.07 | 105.55 ▼1.52 | 40.05 ▲2.32 |
| Posts /wp-admin/edit.php | 2,089 ▼3 | 2.00 ▲0.03 | 39.29 ▲3.00 | 35.64 ▼0.95 |
| Add New Post /wp-admin/post-new.php | 1,533 ▲5 | 22.92 ▼0.15 | 599.32 ▼57.36 | 63.80 ▲10.29 |
| Media Library /wp-admin/upload.php | 1,385 ▼0 | 4.18 ▼0.06 | 102.27 ▼2.74 | 45.43 ▼0.32 |
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: 6 options
- db_upgraded
- widget_theysaidso_widget
- theysaidso_admin_options
- widget_recent-comments
- widget_recent-posts
- can_compress_scripts
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
Good news, no errors were detected
SRP 50% from 2 tests
🔹 Tests weight: 20 | SRP (Single-Responsibility Principle) - PHP files must act as libraries and never output text or perform any action when accessed directly in a browser
Almost there! Just fix the following items
- 1× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_shortcode() in wp-content/plugins/wordpress-clock/wp-clock.php:24
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file uses markdown syntax to describe your plugin to the world
Attributes that require attention:
- Screenshots: Add an image for screenshot #1 (Wordpress Clock on Display)
wordpress-clock/wp-clock.php 92% from 13 tests
The main PHP file in "Worpress Clock" ver. 1.1 adds more information about the plugin and also serves as the entry point for this plugin
The following require your attention:
- Main file name: The principal plugin file should be the same as the plugin slug ("wordpress-clock.php" instead of "wp-clock.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short review of files and their extensions; it is not recommended to include executable files
There were no executable files found in this plugin23 lines of code in 1 file:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 1 | 7 | 8 | 23 |
PHP code Passed 2 tests
A brief analysis of cyclomatic complexity and code structure for this plugin
Great job! No cyclomatic complexity issues were detected in this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.00 |
| 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
1 PNG file occupies 0.01MB with 0.00MB in potential savings
Potential savings
| Compression of 1 random PNG file using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| screenshot-1.png | 6.69KB | 3.79KB | ▼ 43.36% |