Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
This plugin's installer ran successfully
Server metrics [RAM: ▲0.01MB] [CPU: ▼7.56ms] Passed 4 tests
Analyzing server-side resources used by Awesome Progress Bar
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.48 ▲0.01 | 36.02 ▼5.15 |
| Dashboard /wp-admin | 3.32 ▲0.01 | 42.71 ▼2.50 |
| Posts /wp-admin/edit.php | 3.37 ▲0.01 | 45.90 ▼2.88 |
| Add New Post /wp-admin/post-new.php | 5.90 ▲0.01 | 78.57 ▼19.70 |
| Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 37.48 ▲3.61 |
Server storage [IO: ▲0.14MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
This plugin was installed successfully
Filesystem: 4 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| can_compress_scripts |
| widget_recent-posts |
| theysaidso_admin_options |
| widget_recent-comments |
| db_upgraded |
| widget_theysaidso_widget |
Browser metrics Passed 4 tests
Checking browser requirements for Awesome Progress Bar
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,910 ▲164 | 13.72 ▼0.59 | 4.97 ▲3.17 | 42.01 ▼0.88 |
| Dashboard /wp-admin | 2,205 ▲17 | 5.84 ▼0.03 | 100.48 ▼10.37 | 37.42 ▼4.12 |
| Posts /wp-admin/edit.php | 2,088 ▼4 | 2.00 ▼0.05 | 35.46 ▼1.54 | 32.34 ▼5.64 |
| Add New Post /wp-admin/post-new.php | 1,544 ▲2 | 18.18 ▼0.10 | 622.28 ▲0.70 | 65.73 ▲12.23 |
| Media Library /wp-admin/upload.php | 1,393 ▲5 | 4.21 ▲0.02 | 94.22 ▼16.99 | 44.66 ▼2.93 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
You still need to fix the following
- This plugin did not uninstall successfully, leaving 6 options in the database
- theysaidso_admin_options
- can_compress_scripts
- widget_theysaidso_widget
- widget_recent-comments
- db_upgraded
- widget_recent-posts
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)
Everything seems fine, however this is by no means an exhaustive test
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
The following issues need your attention
- 2× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Warning
Use of undefined constant WP_PLUGIN_URL - assumed 'WP_PLUGIN_URL' (this will throw an Error in a future version of PHP) in wp-content/plugins/awesome-progess-bar/main_progres.php on line 12
- > PHP Fatal error
Uncaught Error: Call to undefined function plugin_basename() in wp-content/plugins/awesome-progess-bar/main_progres.php:12
- > PHP Warning
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
No browser errors were detected
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 94% from 16 tests
Don't ignore readme.txt as it is the file that instructs WordPress.org on how to present your plugin to the world
Please fix the following attributes:
- Contributors: Contributors not specified
awesome-progess-bar/main_progres.php 85% from 13 tests
The main PHP script in "Awesome Progress Bar" version 1.0 is automatically included on every request by WordPress
Please take the time to fix the following:
- Main file name: It is recommended to name the main PHP file as the plugin slug ("awesome-progess-bar.php" instead of "main_progres.php")
- Description: Please keep the plugin description shorter than 140 characters (currently 145 characters long)
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | An overview of files in this plugin; executable files are not allowed
No dangerous file extensions were detected2 lines of code in 2 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| CSS | 1 | 0 | 6 | 1 |
| PHP | 1 | 0 | 0 | 1 |
PHP code Passed 2 tests
This plugin's cyclomatic complexity and code structure detailed below
Everything seems fine, there were no complexity issues found
| 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 | 5 | |
| ▷ Named functions | 5 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 1 | |
| ▷ Global constants | 1 | 100.00% |
| ▷ Class constants | 0 | 0.00% |
| ▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
PNG images were not found in this plugin