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.03MB] [CPU: ▼3.70ms] Passed 4 tests
Analyzing server-side resources used by Awesome Clock Widget
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.49 ▲0.03 | 35.03 ▼3.80 |
| Dashboard /wp-admin | 3.34 ▲0.03 | 44.57 ▼3.41 |
| Posts /wp-admin/edit.php | 3.39 ▲0.03 | 45.80 ▼1.49 |
| Add New Post /wp-admin/post-new.php | 5.92 ▲0.03 | 90.78 ▼6.11 |
| Media Library /wp-admin/upload.php | 3.26 ▲0.03 | 34.66 ▲0.68 |
Server storage [IO: ▲0.31MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
This plugin was installed successfully
Filesystem: 7 new files
Database: no new tables, 7 new options
| New WordPress options |
|---|
| widget_theysaidso_widget |
| db_upgraded |
| widget_worldclock_widget |
| widget_recent-posts |
| theysaidso_admin_options |
| can_compress_scripts |
| widget_recent-comments |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Awesome Clock Widget
Normal browser usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,800 ▲54 | 14.48 ▲0.05 | 1.64 ▼0.07 | 41.59 ▼1.44 |
| Dashboard /wp-admin | 2,203 ▲15 | 5.79 ▼0.09 | 97.16 ▼2.08 | 36.67 ▼7.00 |
| Posts /wp-admin/edit.php | 2,089 ▼3 | 1.99 ▼0.01 | 40.32 ▼0.98 | 34.24 ▼1.71 |
| Add New Post /wp-admin/post-new.php | 1,542 ▲9 | 18.49 ▼4.42 | 609.91 ▼31.65 | 46.63 ▼4.36 |
| Media Library /wp-admin/upload.php | 1,388 ▲3 | 4.20 ▼0.19 | 94.15 ▼4.65 | 42.66 ▼0.27 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
The following items require your attention
- The uninstall procedure has failed, leaving 7 options in the database
- widget_worldclock_widget
- db_upgraded
- theysaidso_admin_options
- widget_recent-comments
- can_compress_scripts
- widget_recent-posts
- 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 fix the following items
- 1× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Class 'WP_Widget' not found in wp-content/plugins/awesome-clock-widget/index.php:10
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
No browser issues were found
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 88% from 16 tests
Perhaps the most important file in your plugin readme.txt gets parsed in order to generate the public listing of your plugin
Attributes that require attention:
- Plugin Name: "Plugin Name" should be replaced with the name of your plugin on the first line (
=== awesome-clock-widget ===) - Screenshots: Add an image for screenshot #2 (This is the second screen shot)
awesome-clock-widget/index.php 92% from 13 tests
The entry point to "Awesome Clock Widget" version 2.0 is a PHP file that has certain tags in its header comment area
It is important to fix the following:
- Main file name: It is recommended to name the main PHP file as the plugin slug ("awesome-clock-widget.php" instead of "index.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short check of programming languages and file extensions; no executable files are allowed
No dangerous file extensions were detected3,135 lines of code in 6 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| JavaScript | 4 | 656 | 332 | 2,759 |
| CSS | 1 | 102 | 50 | 281 |
| PHP | 1 | 31 | 15 | 95 |
PHP code Passed 2 tests
Analyzing cyclomatic complexity and code structure
Although this was not an exhaustive test, there were no cyclomatic complexity issues detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.55 |
| Average class complexity | 15.00 |
| ▷ Minimum class complexity | 15.00 |
| ▷ Maximum class complexity | 15.00 |
| Average method complexity | 5.67 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 15.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 | 3 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 3 | 100.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
There were not PNG files found in your plugin