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
This plugin's installer ran successfully
Server metrics [RAM: ▲0.01MB] [CPU: ▼3.37ms] Passed 4 tests
An overview of server-side resources used by GNTT Timezone Clock
No issues were detected with server-side resource usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.47 ▲0.01 | 39.37 ▼3.88 |
| Dashboard /wp-admin | 3.31 ▲0.01 | 50.14 ▼1.47 |
| Posts /wp-admin/edit.php | 3.36 ▲0.01 | 47.92 ▲6.07 |
| Add New Post /wp-admin/post-new.php | 5.89 ▲0.01 | 95.49 ▼8.80 |
| Media Library /wp-admin/upload.php | 3.23 ▲0.01 | 34.89 ▲0.69 |
Server storage [IO: ▲1.39MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
This plugin installed successfully
Filesystem: 10 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_theysaidso_widget |
| db_upgraded |
| widget_recent-posts |
| theysaidso_admin_options |
| can_compress_scripts |
| widget_recent-comments |
Browser metrics Passed 4 tests
Checking browser requirements for GNTT Timezone Clock
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,885 ▲128 | 13.60 ▼1.05 | 9.09 ▲7.07 | 42.44 ▼7.62 |
| Dashboard /wp-admin | 2,208 ▲17 | 5.85 ▲1.00 | 99.12 ▼11.03 | 43.25 ▼1.00 |
| Posts /wp-admin/edit.php | 2,091 ▼1 | 2.03 ▲0.02 | 40.90 ▲0.91 | 35.33 ▼0.70 |
| Add New Post /wp-admin/post-new.php | 1,530 ▼14 | 23.47 ▲5.27 | 652.21 ▲40.72 | 61.13 ▲12.20 |
| Media Library /wp-admin/upload.php | 1,390 ▼1 | 4.18 ▼0.04 | 96.56 ▲3.75 | 40.29 ▼1.84 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
Please fix the following items
- Zombie WordPress options detected upon uninstall: 6 options
- can_compress_scripts
- db_upgraded
- widget_recent-comments
- widget_recent-posts
- theysaidso_admin_options
- widget_theysaidso_widget
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
Everything seems fine, however this is by no means an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle applies for WordPress plugins as well - please make sure your PHP files perform no actions when accessed directly
Please take a closer look at the following
- 1× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/gntt-timezone-clock/gntt-time-zone-clock.php:16
- > 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
6 plugin tags: timezone clock, gntt, clock, timezone, gntt clock...
gntt-timezone-clock/gntt-time-zone-clock.php 92% from 13 tests
"GNTT Timezone Clock" version 1.0's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
It is important to fix the following:
- Main file name: Name the main plugin file the same as the plugin slug ("gntt-timezone-clock.php" instead of "gntt-time-zone-clock.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are considered dangerous and should not be included with any WordPress plugin
Everything looks great! No dangerous files found in this plugin84 lines of code in 3 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| CSS | 1 | 5 | 0 | 40 |
| PHP | 1 | 1 | 14 | 23 |
| JavaScript | 1 | 13 | 0 | 21 |
PHP code Passed 2 tests
Analyzing 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.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 | 4 | |
| ▷ Named functions | 4 | 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
5 PNG files occupy 0.03MB with 0.02MB in potential savings
Potential savings
| Compression of 5 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| images/minhand2.png | 1.10KB | 0.22KB | ▼ 80.34% |
| images/screenshot.png | 17.83KB | 8.81KB | ▼ 50.61% |
| images/clockface2.png | 13.19KB | 6.10KB | ▼ 53.72% |
| images/hourhand2.png | 1.12KB | 0.25KB | ▼ 78.19% |
| images/sechand2.png | 1.59KB | 0.93KB | ▼ 41.40% |