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.02MB] [CPU: ▼2.91ms] Passed 4 tests
An overview of server-side resources used by Display Blog Time
This plugin does not affect your website's performance
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.48 ▲0.02 | 42.32 ▼2.51 |
| Dashboard /wp-admin | 3.32 ▲0.02 | 50.00 ▼1.96 |
| Posts /wp-admin/edit.php | 3.37 ▲0.02 | 51.01 ▼0.24 |
| Add New Post /wp-admin/post-new.php | 5.90 ▲0.02 | 89.29 ▼6.93 |
| Media Library /wp-admin/upload.php | 3.25 ▲0.02 | 35.72 ▼0.19 |
Server storage [IO: ▲0.04MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
No storage issues were detected
Filesystem: 6 new files
Database: no new tables, 7 new options
| New WordPress options |
|---|
| widget_et_btime_widget |
| can_compress_scripts |
| db_upgraded |
| widget_recent-posts |
| widget_theysaidso_widget |
| widget_recent-comments |
| theysaidso_admin_options |
Browser metrics Passed 4 tests
Display Blog Time: an overview of browser usage
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,789 ▲3 | 14.28 ▼0.07 | 1.73 ▼0.33 | 42.81 ▼1.42 |
| Dashboard /wp-admin | 2,198 ▲24 | 5.63 ▲0.03 | 86.57 ▼14.69 | 43.76 ▲1.91 |
| Posts /wp-admin/edit.php | 2,100 ▼0 | 2.01 ▲0.04 | 33.91 ▼2.63 | 35.45 ▲1.89 |
| Add New Post /wp-admin/post-new.php | 1,526 ▼0 | 23.82 ▲0.23 | 674.11 ▼26.14 | 57.96 ▲2.60 |
| Media Library /wp-admin/upload.php | 1,397 ▼3 | 4.17 ▼0.03 | 100.46 ▼3.62 | 44.66 ▼6.98 |
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
The following items require your attention
- Zombie WordPress options detected upon uninstall: 7 options
- widget_theysaidso_widget
- db_upgraded
- widget_recent-comments
- widget_et_btime_widget
- widget_recent-posts
- can_compress_scripts
- theysaidso_admin_options
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)
The smoke test was a success, however most plugin functionality was not tested
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
Please take a closer look at the following
- 1× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Fatal error
Uncaught Error: Class 'WP_Widget' not found in wp-content/plugins/display-blog-time/btime.php:25
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
No browser errors were detected
Optimizations
Plugin configuration 83% from 29 tests
readme.txt 88% from 16 tests
You should put a lot of thought into formatting readme.txt as it is used by WordPress.org to prepare the public listing of your plugin
These attributes need your attention:
- Screenshots: Add a description for screenshot #2 in display-blog-time/assets to your readme.txt
- Screenshots: Add images for these screenshots: #5 (6.), #7 (8.)
display-blog-time/btime.php 77% from 13 tests
"Display Blog Time" version 0.9 BETA...'s main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
Please take the time to fix the following:
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("display-blog-time.php" instead of "btime.php")
- Version: Use periods and digits only for your plugin's version number (ex. "1.0.3" instead of "0.9 BETA...")
- Text Domain: You no longer need to specify the text domain since WordPress 4.6; it must be the same as the plugin slug
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
No dangerous file extensions were detected50 lines of code in 3 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 2 | 15 | 40 | 48 |
| Markdown | 1 | 0 | 0 | 2 |
PHP code Passed 2 tests
This is a short overview of cyclomatic complexity and code structure for this plugin
This plugin has no cyclomatic complexity issues
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.12 |
| Average class complexity | 4.00 |
| ▷ Minimum class complexity | 4.00 |
| ▷ Maximum class complexity | 4.00 |
| Average method complexity | 1.75 |
| ▷ 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
PNG files should be compressed to save space and minimize bandwidth usage
No PNG images were found in this plugin